>>>I am attempting to run my VFP application (as an EXE file) from a remote site using universal naming convention instead of a mapped drive. (Note the application works perfectly with a mapped drive).
>>>
>>>I make no references to paths in the program except that I open all my table and databases using a relative path name. Example:
>>>
>>>use database\atable.dbf shared in 0
>>>
>>>My CONFIG.FPW file has no path names hard coded for table access.
>>>
>>>I get the following error when running the EXE:
>>>
>>>Unable to access \:\\FS_RENAL2\USER1\APPS\DB\MAIN\DATABASE\PATDB.DBC
>>>
>>>This looks fine except for the "\:" at the start. How did that get there? Should that be there? What is causing it?
>>
>>Sorry folks the error message is acutally
>>
>>"\:\\FS_RENAL2\USER1\APPS\DB\MAIN\DATABASE\PATDB.DBC does not exist."
>Evan,
>I think it's not dbf but backlink info causing error. This works quite well :

mfname = "\\poseidon\d$\goruntu\data\images"
>use (mfname)
>browse
>? dbf()
>* "\\poseidon\d$\goruntu\data\images" prints correctly

Might it be in original design DBC was in root of where DBF reside ?

Cetin,

I don't understand your reply. I think you are answering another question.
In my application I have no paths hard-coded to open my tables or databases. I simply say:

use database\atable.dbf
use database\another.dbf
use database\thisone.dbf

Therefore the application only "knows" that it should reference the database tables in a subdirectory underneath the directory where the application is executing. This works find when I map a drive, but does not work when I use UNC (Universal Naming Convention).

Example if I map a drive P: to FS_RENAL2\USER1\APPS
I can then run the application p:\db\main\vmain.exe with no problems.

If I dispense with the drive mapping and simply start the application by directory referencing FS_RENAL2\USER1\APPS\DB\vmain.exe it can not seem to find the "database" subdirectory.

Any thoughts?