There are two primary reasons that I have found for your error message. They both have to do with where the FOXUSER.DBF file is kept.
1. The first possibility occurs when you are in an operating system such as Win 2K or Win XP where each individual workstation user has their own set of file access privilages.
If the directory where the FOXUSER.DBF table is kept does not allow Full Access rights to Everyone, then some users will get this error while others may not.
You say that "There is a foxuser.dbf/fpt in the current directory", but does Everyone have READ & WRITE privilages to that directory?
2. The second possibility is that the directory where the FOXUSER.DBF file is kept may not be accessible at all and/or not mapped to the user's workstation.
If you are using a CONFIG.FPW launch file, check it to see if a directory is referenced which is not present and/or not accessible to the user's workstation.
Could it be that the FOXUSER.DBF resides in the "current" directory, but maybe you are using a CONFIG.FPW file which makes VFP want it to be elsewhere?
You may be operating both Foxpro earlier version and VFP8 executable. These try to use the FoxUser.DBF in their respective formats and so replace them with their respective versions with the prompt you specified.
Unfortunately, this may have nothing to do with FOXUSER. MS calls .DLLs "resource" files also. If the VFP .DLLs are version mismatched or missing you can get an error like this too. Any chance you install SP1 on the developer system, but did update the user's runtime files to SP1? How did you install this application on the user's system? With the included (but separately installled) VFP ISE?
The user has no VFP installed. So, the only VFP runtime files are VFP 8 SP1 files installed by the application.
I believe if the dlls are not correct version, the error is Resource file version mismatch not The resource file is not valid.
Need to double check the access right. But I really doubt this since the same workstation has no problem few days and then will get this message again. Need to ask whether the same login is used.
I got this error several times when I first installed VFP 8.0. It made no difference whether you agreed to overwrite the file with a new one, the same behaviour occurred next time you went into VFP.
I finally solved it by searching for, and deleting, every occurrent of Foxuser.* in my system.
I have already asked the user to check for all the foxuser.* but haven't gotten any update yet. BTW, do you know why other foxuser.* will matter? I assume you already check config.fpw already. Besides config.fpw, are there anything else (such as registry entry) related to foxuser.*?
I can't guarantee that deleting all the foxusers will solve the problem. All I know is that it seemed to work for me. But it's worth a try.
, do you know why other foxuser.* will matter? I assume you already check config.fpw already. Besides config.fpw, are there anything else (such as registry entry) related to foxuser.*?
There are several different ways in which a resource file can be specified on startup: with command-line switches, with RESOURCE= in config.fpw, from a desktop shortcut, etc. In my case, I didn't bother to trace through all these, I just did the delete thing.
As far as I know, the registry isn't an issue here.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.