I had already tested it, and encountered problems. After I sent the message I was able to figure out a solution. The problem I was having was that the project file references to the database, tables, class libraries, etc. referred to a network drive letter rather than UNC paths. This returned an error when I tried to use UNC paths in code. Once I changed the project references to UNC paths, including all inherited classes from class libraries on the network, the code worked. This method also prevented me from having to code the DE to manage tables, because the file references in the DE will now use UNC paths that are in the project file references. I have since changed the default options for forms, class libraries, and field mapping in the tools, options menu of VFP to UNC file references by using Network Neighborhood in Windows '95. Thanks for the feedback.


>>Does anyone know if VFP 5.0 can accept UNC paths in the SET PATH, SET DATABASE, SET DEFAULT, etc. commands?
>
>how much time will it take you to test this ? :)
>
>
>> Also, how can I use a UNC path for a table that is included in a form's dataenvironment? The dataenv. automatically uses the >drive letter, which means that users in a different department won't be able to run an application that accesses a database on >my department's network drive.
>
> you can always set the DE programatically in the BeforeOpenTables event (or use DE's in code)
>
>Arnon