I simply

set resource to (myfile)

then I get an error message that says "memo file is missing or invalid"

if I try to

=fopen(myfile,0)

I simply get -1 which means could not open file for read only access

and if I at this point do

use (myfile) in 0

I get "file in use" error

If I do =fopen(myfile,0) or use (myfile) in 0 BEFORE I call set resource to (myfile) they work and the file opens file and I can even browse it and view the memo, but once set resource to (myfile) is called even in the on error handler I cannot get access to this file even if I try doing set resource off before =fopen(myfile,0) or use (myfile) in 0. So it appears that the memo file is NOT invalid before calling set resource to (myfile) and after that call something other than open tables is using the file even though SET("RESOURCE") returns OFF.

So since it appears to me that this is a bug in VFPSP1 - that when SET RESOURCE TO is called and it does not like the file it DOES not let go of a file handle to the file even though it says the resource is turned off it is on and set resource off is called. I even tried setting another file as the resource file besides the problem file and it still retains a file handle to the file that does not allow it to be FOPEN() or USEd until I exit VFP and re-run VFP.

So since there is a bug in VFP about not letting go of a file handle in a invalid memo in a resource file, does anyone know of a way to determine if there is something in a resource file that VFP9 does not like that it would raise a memo file missing or invalid message for so that I can check and fix it before doing a SET RESOURCE TO since the bug in VFP will not allow me to access the file once that error has occurred?