Observed with VFP8 and VFP7SP1 on W2KSP4 and W2KSP3:
This has been killing me for several hours now. I even finally removed SP4 of Win2K (PRO) to learn if that was implicated in the problem. It wasn't!@#!#@ [at least it doesn't look like it because the problem persists after backing it out]

I have a form that has a DE that has tables pointing to mapped drives in it. The mappings are ALL to directories ON THE SAME MACHINE (it's C: drive) as the instance of VFP is running on, for instance X: is mapped to \\ADVOLT100\C:\ADVOSecure and appears in the Windows Explorer as "ADVOSecure on 'Advolt100\C'(X:) Advolt100 is the 'name' of the machine running VFP.

Now when I d-click on the form to open it for edit I get the error message: Error loading file - record number 3. Cursor3 < or one of its members>. :File access denied x:\Mercontrol.dbc. with an OK and Help button.
Clicking on Help yields: Error loading file - record number n. "object < or one of its members>. "Issue": "error" (error 1881) and offers some simple steps to try to access/correct the problem.

A very interesting aspect to this is that ALL the .DBCs and tables, ALL OF THEM MAPPED TO DRIVES X:, Y:, or Z: appear under the data tab of the Project Manager and their field names are accessible by clicking the +-sign beside a table's name. In addition I can d-click any table to cause the Table Designer to appear and it is NOT in read-only mode!

Another interesting aspect is that, with VFP still open and with the subject project still open I can go to Windows Explorer and d-click on MerControl.DBC in the mapped (X:) directory and here's what happens:
1) A simple VFP error box appears with the words; File access denied x:\mercontrol.dbc. and an OK and a Help button;
2) Clicking on the OK button presents the Database Designer window wit the databases' tables all appearing properly. Stored procedures are accessible too!

Now if I go directly to the directory ADVOSecure on the C: drive and then d-click on the Mercontrol.dbc, there is NO error message and the Database Designer appears directly.

Since I had installed SP4 the day it came out I decided to remove it and try again. Unfortunately there was NO CHANGE in the situation.
It is possible that some prior "critical update" caused this problem. I tend to keep this system right up-to-date.

I have several projects with DEs using this scheme. I don't even want to try to open them until I get this one solved.

Any ideas will be greatly appreciated.
Thanks