>>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...
>
>
>True, but I don't need exclusive use of the table. I try to avoid that...

Yes, but since this table is on the user's hard drive, EXCL is fine unless you allow more than one instance of your app. Also, I should mention another argument for the 1-row many-column table: there's no need to go LOCATE or SEEK a row, since you're always on row 1. There's no right/wrong on this issue, I'm only presenting some points why this method can be better for some situations :)