Jane

>As I've written elsewhere, John, I'm not thrilled with locating common
>(shared) data Microsoft's way for various reasons on single workstations or
>in a workgroup.

Thanks for all you have writtien here and on ClarionMag.


>In a client/server situation, things get more complicated.
>Active Directory settings in a domain environment can remap users documents
>(or My Documents) folders transparently to some server location.

Dang! I did not want to know that! <G>

>Is your TPS settings file common or individual? Do ordinary users need to
>write to it?
>In some server-based apps I use TPS files which contain SQL connection
>information.

Yes, that is exactly what I am storing there.- the SQL connection settings and a
license key. They should be avail to all users for reading, and I would like for them
also to be able to change the settings. I may need to review the need for all users to
be able to change a connection setting. I could add a small SB6 based app to get over
that hurdle.

>I put these files in the same folder with the app, and have
>the app open them read-only (unless being run in setup mode by an
>administrator). Haven't tried this live with Server 2008, but in a Server
>2003 Active Directory domain comprising two WAN-connected sites it works
>fine because if users have permissions to run the app they have permissions
>to open the settings file read-only.

That makes sense too! Might try that next time.

Thanks

John Griffiths