>>Of course, I have user list in all my applications, but preferences users might have/want to have when running the application get far too many in the long run, which makes it easier to use their Windows Registry to control, than to modify the database each time I have to implement new user-preference based feature. For example, it usualy starts with users wanting to start my .app and getting exactly where they left off, next thing you know, they want last-used customer_id (accompanied by the name etc.) to pop up when they register new order, and so on...it just gets too clumsy to keep all that in your database when you already have something so nice as the Registry. It is, after all, only a primary key you need to store there, rest is handled by the views...
>>Daniel
>>Tip. See my demo at "Files\Classes - VCX\RegistryControl"
>
>Doing that way, however, forces them to always work at the same machine, whereas, if you did it in a free table, it wouldn't matter where they connect to the network from.

Well, of course, I assumed people would understand that it is the local machine values are stored on, so taking that into account it is up to individuals to evaluate wheather or not that's the way to do it.