>>>>>I've got some information that I'd like to store for my app, and I'm trying to decide how best to do it.
>>>>>
>>>>>I was thinking of making a table, but the table would only be one record with a lot of fields. That seems kind of silly.
>>>>>
>>>>>A lot of apps use .ini files to store configuration information. Is there anything special about them, or are they just text files? How would you know where in the file to change something? I don't know anything about manipulating text files with VFP.
>>>>>
>>>>>Or is there another option?
>>>>>
>>>>>Thanks,
>>>>>
>>>>>-Michelle
>>>>
>>>>INI files are supported for backward compatability. The registry is the proper place to store this information.
>>>
>>>For the system info, I think a 2 field table would work good. For user preferences, the registry wouldn't work, so I may use .ini's for that.
>>>
>>>Thanks,
>>>
>>>-Michelle
>>
>>
>>Whoa...that's exactly one thing the registry is used for. I save user preferences there all the time. INI files are no longer recommended.
>
>Ok, I'm confused. I thought the registry was local to the computer? If I put user settings there, how do I access it from a different computer? Do I put it in the registry on the server?

Sort of. With roaming profiles installed, certain portions, or hives, of the registry can follow the userid in an NT domain, with selected branches of the registry loaded from a hive file on the PDC. You can also create application hives - registry branches, essentially, that are loaded during application startup using some of the WIn32 API registry functions. The use of hives provides a mechanism for customization and control of registries cross system.

>
>-Michelle