>>>>I have used .ini files to hold values in VFP, but it's just as simple and more controllable to use a .dbf parameter table (uh oh, now I'm going to hear from the API gurus).
>>>
>>>ha ha ha I know the feeling!
>>>
>>>>
>>>>If you want to use an .ini, there is pretty good description of the process in the Programmer's Guide.
>>>>
>>>
>>>I'll do some thinking about this and decide wether I'll go with the table or take the .ini file approach. On the meantime I'll sit down and wait for the day when technology allows us to control executables at run time, then I'll have a toast and think of all the cool stuff that could be done with it.
>>>
>>>
>>>Cheers and Merry Christmas,
>>>
>>The same,
>>
>>regards,
>
>Happy holidays to all.
>
>The Win95+ version of an .ini file is the registry. It's not to hard to store a value or two in the registry.
>
Hi Cheryl,

In fact is very easy. But what is the point _unless_ you are going to share the information with another, non VFP application? VFP provides a neat, compact, easy to use build-in means of storing and retrieving information in its native tables. We do not have to use methods necessary for languages (VB comes to mind) that are not so blessed.

Happy NY

regards,