What about saving the Registry to something like Gary.reg and then modifying, running it? I do something like this to avoid some corporate "restrictions" sometimes.

>In many of my older applications I stored Config information, licence details etc in my own .INI files (or files with the same layout but diferent names) and I was able to use the Windows API calls to read, list, edit & append entries and section to those files.
>
>In the new era or the Registry, can I have my own registry file? and use the API to access it? I've looked around but can not find anything along these lines.
>
>I have a number of applications whose data is stored on a network drive and which need to know details about each other and also share some data. I need a simple config file for them to share and the registry layout seems idea, but since this is network data I need all workstations to see the same file, hence the idea of my own registry.
>
>I know I could create tables & fields but the hierarchical nature and flexibility of the registry would be ideal (and the access functions already exist!)
>
>Anyone got any ideas on this?
>
>
>Gary.