Thanks Ed

The registry will be global but I still plan to store individual user settings in it as well as other application specific data.

The foxuser idea is intresting but I keep a seperate resource file for each user.

Ideally I am looking for something like Drew's GetAppInfo routines in his public domain framework.


Mark


>>I am looking for a simple set of functions to manage my application registry (not the windows registry).
>>
>>I couldn't find any in the files section that are not part of the free frameworks and I don't have time to re-invent the wheel or to try and hack them out.
>>
>
>These application settings, are they global to the app, to the workstation, to the user - IOW do the settings in the SYSTEM.DBF pertain to the app run anywhere, anytime, to one particular workstation, to each user, to each user at each station? You might want to look into adding your own entries to the RESOURCE file (FOXUSER.DBF) as appropriate; VFP can be asked "where do you think the Resource fie is supposed to be?) and it's a table; make your system entries have their own 'type' field value. You can pull the data by:
>
>SELECT * FROM (SET('RESOURCE',1)) INTO CURSOR MySettings WHERE type='MyApp'
>
>You can use the ID field to identify which settings are available, and there are two memo fields, Name and Data, somewhere to checksum the record using SYS(2007), a ReadOnly flag, and a datestamp available...
>
>May as well use it for something useful if you don't currently disable the resource file...
>
>>Previously I have been using a plain old system.dbf to store my application settings.
>>
>>This will be a big time saver for me.
>>
>>Thanks