I provide a setup form that uses the registry to store the path to the data. The user has to map the drive if it is a network drive... not a big problem if they understand enought to install a network application.

I store the data directory in the application object when the application fires up it tries to open the database if it is not where it thinks it is then it prompts the user to find it or bail out.

IN my forms if the application object I get the data path and reset the cursors path to that directory before I load the tables in the DE. If the application object is not present that means that I am just running the form in development so I don't need to change anything.

If the you wish to use this approch then I can send you the code to do so.

John

>I have an app designed under the following hierarchy:
>
>app c:\myapp\myapp.exe
>data c:\myapp\data\*.dbf,*.cdx
>
>The user, upon installation, may want to change the data to reside on the v: drive and may want to later move it to the m: drive. How do I handle this without making the user find the data everytime they run the app?