>I want to allow my users to install my .exe anywhere they want (c:\...,k:\..., m:\... etc.) and am wondering if I need to use a config.fpw to set the path for the data based on where they installed the .exe. If so, what should be included in the .fpw, and do I need to reference it on start up (how)? Any help would be appreciated. Thanks in advance.
>
>Mike

Mike,
The best solution (IMO) for this is for you to specify the directory structure under your application. The end user can install your software anywhere they like but the relative pathing remains the same.

Ex.
Program - D:\MyInstall
Data - D:\MyInstall\Data

If you can't do that because your user wants to separate applications from data, the best case here is to ask the user when you initially launch your application where the data is. Store this information somewhere (INI, registry) and use it the next time the application is loaded.

However, you may get into a situation where the client doesn't want the user asked anything (liek we did). We had to write a utility that, when loaded, searched the available network shares to find the database and store that inforamtion. The reason for this was user turn over. New users and new systems were constantly being introduced into the mix and a new user may not know what was going on.