LiveCode Forums.

Yes, part of the group, but out of sight (beyond the bounds of the group).

No idea about memory usage.

You could do a couple of things:

1. a chart/graph - I do something similar where the chart is a set width and I provide buttons to scroll the dates. When the user advances the date I query the data again (a db backend), and redraw the graph with new start and end dates.

2. a group that has locked ...

What RunRev needs to do is license the encryption extension. Real Software did it for Real Studio/Real BASIC so licensing for an IDE, and its users, by the developer of the IDE is not unprecedented.

http://www.hwaci.com/sw/sqlite/see.html

I'm not clear on your table structure.

Not sure how things could be worse than no mention at all in the release notes.

select character 5 to 10 of field 1

I want to see how well it really is and if you finally fixed the long standing major issue of lacking versioning support / versioning usability with LiveCode 5 or if its still an closed little world on its own not meant for 2+ developers at all

At least according to the Release Notes nothing has ...

My mistake. revDatabaseColumnNames returns a comma-delimited string not a return-delimited one so put the following after your revDatabaseColumnNames call...
That will make it work with the repeat loop you've already constructed.

put "INSERT INTO Mood (" into sqlQuery
put empty into tFieldNames
--add this bit
put empty into tFieldValues
put revDatabaseColumnNames(conID, "control") into pptext

repeat for each line linColumn in pptext
put tFieldNames & linColumn & "," into tFieldNames
--put "'"& tFieldNames ...

Off the top of my head....

put "INSERT INTO Mood (" into sqlQuery
put empty into tFieldNames
put revDatabaseColumnNames(conID, "control") into pptext

repeat for each line linColumn in pptext
put tFieldNames & linColumn & "," into tFieldNames
end repeat

repeat while the last character of ...

revDatabaseColumnNames will give you the names of the columns in a recordset.

Also, it can be a bit confusing because the menu names don't change much, but if you go to the 'LiveCode' menu it will be populated with GLX2 stuff instead.

Of particular note will be the GLX2 preferences.

If you hover the cursor over it, there's probably a message like "Using LiveCode Script Editor..."

There should also be a "GLX2" all the way to the right. Hover over that, and there should be a "Click to start using..." message.

Click the GLX2 'button' and it will be the script editor when you ...

I'm using, but so far the documentation is small.

It will grow, of course, but I fully expect the tags, statuses, and manuals to keep it organized enough to keep me no more insane than I currently am.

The usual metaphor, although it is extremely dated, is one of a rolodex/card file, where the stack is the rolodex/card holder, and each card is an individual...well, card. I suppose one of a website as the stack with cards as pages might work as well, and be more current. Hadn't thought of it that ...