Tim Young [Elevate Software] wrote:

> Malcolm,
>
> << But that is under <pf> so is a problem for shared access >>
>
> In the case of Vista or shared, make the configuration/app path be
> a shared folder or a folder in the local Application Data folder.
> But, the principle of having the database paths be under the
> configuration path is still suggested.

Noted, and I can do this for the stand-alone applets.

>
> << That I understand and already do under commonappdata .. my
> question was about the config file, which, if it is to be shared by
> p2p 'clients', will most likely have to be in the database folder.
> >>
>
> Not necessarily.  Again, I usually recommend that you keep the
> configuration file/log out of any database directories.  It's
> simply just too easy to think that you're blowing away the contents
> of a single database with an:
>
> erase *.*
> or
> move *.* \someotherdir
>
> and end up killing/messing up the entire configuration in the
> process also.

Yep, that is my concern.
I will reflect upon the dilemma - I am not keen to create another,
albeit read-only, share.
I guess that F/S is the 'obvious' solution.  

Thanks, Tim and Roy, for the clarifications.

--

Tim


metadata - that's the word I keep trying to remember

Roy Lambert

woops!  F/S should be C/S