>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?

If you have the data path stored in an INI file or the Registry, you can give the users an interface to change the data path.

However, if they move it and don't use your interface to tell the application what the new path is, then you will have to prompt them for it. You can then store the new data path in the INI file - preferably with the UNC name instead of a drive mapping, unless your client has standardized network drive letters - then you'll only have to prompt them once.