>>>>At first, maybe...but it's extremely functional for storing session startup info like last form, last page, last grid cell, last sort, last record, various preferences, that type of thing. It's flexible, too, you open it EXCL from user dir, then can Alter Table to add/delete fields later as needed in main prg...
>>>
>>>I like the idea someone had of having two fields in the table. One is the attribute, the other is the value. Then I don't have to modify the structure to add or delete things.
>>
>>I use that method with cursors in grid/report "tables," but there's one thing to bear in mind - you may have to do some type conversions on your value field, it can get a little messy. And you still have to do an equivalent of Alter Table to add/delete rows to the table...
>
>The only thing I can think of at the moment to store is paths, company name, and serial number, which are all strings. So far I'm safe. I don't understand why I'd need an alter table to add or delete rows? What's wrong with INSERT and DELETE?

Nothing wrong :) Just that you need to check existence and adjust rows using Insert/Delete in the same manner you'd check columns and use Alter Table to "insert/delete" columns if you want to make changes on updated app versions...