My mind is always open even when it is made up :) I have used a two field table in the past but never thought of using the Data Type to tell me what type it is. This solves the problem that I had in the past using a table.

It seems to me that a program might be used under one or more of the following conditions:
1 Single user on a single couputer not networked.
2 Single user on a single computer networked.
3 Single user on multiple computers networked.
4 Multiple users of one copy of the program on a single computer not networked.
5 Multiple users of one copy of the program on a single computer networked.
6 Multiple users of many copies of the program on multiple computers networked.

In my case this program is expected to be used under 1 or 2 but most likly 1 as the program will be used at a job site rather than an office.

Seems to me now that perhaps a combination of the two might be the best depending on what the data is.... Things like installation data for the program would be natural for the registry... gotta think some more... need more coffee...

>Even though you seem to have made up your mind, here some more to consider.
>
>Using the registry for user profiles forces the user to use the same PC when they log in. If the information were stored in a table on a network drive, this would not be the case.
>
>Also, configuration data stored in a sufficiently flexible table can store anything without changing the structure. You can store anything (basically) in a table with three character fields.
>
>Variable Name
>Data type
>Data value converted to character format
>
>Just add a program to convert from character to specified datatype and back and presto, you have a system you don't need to modify the structure.
>
>Just my $0.02.
>
>>Sounds like you are pro-registry to me... :) I like the idea that you don't have to change the structure to store more info... going once, going twice, sold on registry....
>>
>>Thanks for the help
>>
>>>>Are there any pros or cons to using the Registry to store program information like user settings vs using a table?
>>>
>>>If the settings are system wide, and should not vary from user to user, you have little choice but to use a table (or some other file) on a network drive. The registry offers the advantage of being a standard, and the recommended method of storing application data, and of allows differing sets of settings for different user profiles. Also, with the registry, you don't have to modify the structure when you decide to store more information. Can you tell which way I am voting here?