>We are getting ready to distribute our first VFP5 .EXE which is a re-write of a small DOS application. The application uses tables that are part of another existing) application. I am looking for suggestions on how to handle file/table locations in WIN 95/NT since different users may opt to install the application(s) in different locations.
>
>The DOS version relied on either table entries or DOS memory variables to point the application in the right direction (extract values then set path/default). What is the proper 'Win-compliant' approach? .INI files,
>Win Registry entries, etc.?
>
>Registry.prg which is included with VFP, contains custom classes that access INI files and the WIN registry but there doesn't seem to be much
>information on how to use the functions (what parameters to pass, etc.)
>
>TIA,
>Jim

INI files are probably the most Win-Compliant, but I find the easiest is to use the CONFIG.FPW file. This text file can be different for every installation, and can include references to the default data path, screen title on loading, etc.

HTH
Barbara