>Hi...I'm getting ready to deploy Opus 1, on a network. I've been developing this on my home network but now need to be able to deploy on multiple workstations with the data files on a Novell server and an .EXE file located on each workstation. The environment at the client site is different than my own...(different drive mappings, folder names, you name it.).
>
>So my question is, can you use the setup wizard to deploy this thing on client machines? Some of the things I'm worrying about are:
>
>1. The project file so far, includes the data files (.DBC and tables)
>2. The data environment also includes the data files (there is a data environment for each form.)
>
>
>Since the Setup Wizard includes everything in the subdirectory, I'm thinking that I could remove the data files and place them on my home server, and then rebuild the project. However, unless the drive mappings, etc are identical, the client's executable wouldn't know where to find the data. (Is it smart enough to ask the first time and then remember? I don't think so.).
>
>The app builds and deploys fine as a standalone application. I'm using VFP 6.0 with the latest service pack (3)
>
>Any suggestions would be greatly appreciated.
>
>Thanks.
>
>---- Larry

I use the following:-

On the user's machine (i.e. via the executable):-

Check my .INI file for the location (UNC, Drive letter, etc) of the last DBC access
if the entry is blank
   prompt the user for the location
   save the location to the ini file
endif

if the file doesn't exist
  prompt the user for the location
  save the location to the ini file
endif   

set path to dbcPath;dataPath;.....

Note that I assume that the data files are location in a subdirectory DATA\ 'under' the DBC location, but it doesn't really matter, you can extend the method for other locations. It also assumes that there is only one DBC.

This will work for each user (even if they have a different logical route to the data e.g. \\server\here or X:\there) plus if the DBC is moved or is unavailable they are prompted.

You don't have to use an INI file, you can use the system registry or a VFP table.

Just my tuppence.