My ASP.NET page is able to access VFP databases that are local to IIS.
However, problems arise when the VFP databases are stored on another machine.
I tried to use both (a) mapped drives, and (b) UNC names in the Oledb connection string, and failed.
In the case of mapped drives, error message says "Invalid Path". For UNC name, error message says "Invalid path or filename."
I have tried many ways to get it to work, eg.
- Changed <processModel> tag's user/password attributes in machine.config,
- Created domain user account for aspnet user
- Set up logon scripts which maps network drives (using "NET USE"
for both local/domain aspnet user.
All of which fails to work.
This whole thing is driving me "bananas"!! why did Microsoft make a simple issue of accessing file-based databases over a network so difficult? To make people switch to SQL Server, I suppose.
Would appreciate very much if someone can help, thanks.
However, problems arise when the VFP databases are stored on another machine.
I tried to use both (a) mapped drives, and (b) UNC names in the Oledb connection string, and failed.
In the case of mapped drives, error message says "Invalid Path". For UNC name, error message says "Invalid path or filename."
I have tried many ways to get it to work, eg.
- Changed <processModel> tag's user/password attributes in machine.config,
- Created domain user account for aspnet user
- Set up logon scripts which maps network drives (using "NET USE"
for both local/domain aspnet user.All of which fails to work.
This whole thing is driving me "bananas"!! why did Microsoft make a simple issue of accessing file-based databases over a network so difficult? To make people switch to SQL Server, I suppose.
Would appreciate very much if someone can help, thanks.