OldxBaser
Programmer
- Nov 5, 2009
- 24
We have run into a problem on 2 of our clients who upgraded to a 64-bit network with Windows7 workstations.
They experienced some "File not found..." types of errors, but we noticed the network path to the file was incorrect.
e.g., assume a drive on the server - \\Server1\Apps\
Map to this drive from a workstation as R:
Assume an application in R:\MyDir\
--- on a 32-bit network ---
FULLPATH() returns R:\MyDir
--- on a 64-bit network ---
FULLPATH() returns \\Server1\Apps\Server1\Apps\MyDir
I wrote a quick utility EXE and ran it on several different client networks; all 32-bit networks correctly returned the expected pathname.
But the 2 clients' 64-bit networks both returned the path with the doubled server-drive name.
My utility displays return values from FULLPATH(), CURDIR and SYS(16)
The client's network techs are in the dark on this.
I would greatly appreciate any input or suggestions.
Our large distributed multi-user application is compiled in VFP9.
They experienced some "File not found..." types of errors, but we noticed the network path to the file was incorrect.
e.g., assume a drive on the server - \\Server1\Apps\
Map to this drive from a workstation as R:
Assume an application in R:\MyDir\
--- on a 32-bit network ---
FULLPATH() returns R:\MyDir
--- on a 64-bit network ---
FULLPATH() returns \\Server1\Apps\Server1\Apps\MyDir
I wrote a quick utility EXE and ran it on several different client networks; all 32-bit networks correctly returned the expected pathname.
But the 2 clients' 64-bit networks both returned the path with the doubled server-drive name.
My utility displays return values from FULLPATH(), CURDIR and SYS(16)
The client's network techs are in the dark on this.
I would greatly appreciate any input or suggestions.
Our large distributed multi-user application is compiled in VFP9.