Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Finding mysterious FoxUser resource file

Status
Not open for further replies.

RickSchummer

Programmer
Jan 23, 2003
167
US
Problem: starting a VFP 8 SP1 custom runtime EXE, the user gets a message on the client machine to
convert FoxUser from 3.0 to 6.0.

App is run off server from a workstation. Running app on server displays same question.

CONFIG.FPW is compiled into the EXE:
RESOURCE = OFF
ALLOWEXTERNAL = OFF

No CONFIG.FPW in the application folder so it cannot be pointing to a resource file. No -C parameter
on the shortcut. No FoxUser in the application folder, not in search path, no FoxUser is created in
the application folder after answering No to the question to convert.

Doing a SET in DOS window does not show the old FOXPROWCFG or FOXPROCFG environment variables.

Stumped. Anyone have any fresh ideas where the FoxUser could be found? Nothing in the Microsoft KB, nothing in my personal experience.

_RAS
VFP MVP
 
Hi

Few things to check..
1. In the registry..
HKEY_CURRENT_USER:
Software\Microsoft\VisualFoxPro\8.0\Options
or suitable version..

2. Start VFP and see if the same question is asked. If yes, try running with -C switch from command line or RUN box

3. Copying a Foxuser of the correct version in the application directory and then try.

4. Check the project files for an accidental inclusion of Foxuser in the comiplation. Still, I feel this should give a read-write error and so this is last chance. Dont know why then I am suggesting this. When an error of this nature takes place, something odd is taking place.

5. Checking in the directory spaces referred by CONFIG.FPW for a Foxuser file.

Now I am running out of clues.

:)

____________________________________________
ramani - (Subramanian.G) :)
 
Hi Rick,

Use Window find utility to find and erase alll instances of foxuser.dbf and foxuser.fpt. Has the config.fpw file been included in the build?

Regards,

Mike
 
>>1. In the registry..
HKEY_CURRENT_USER:
Software\Microsoft\VisualFoxPro\8.0\Options
or suitable version..<<

VFP is not installed on these machines, it is a run-time application

>>2. Start VFP and see if the same question is asked. If yes, try running with -C switch from command line or RUN box<<

Again, run-time app.

>>3. Copying a Foxuser of the correct version in the application directory and then try.<<

RESOURCE = OFF in internal Config.fpw file, I do not want one.


>>5. Checking in the directory spaces referred by CONFIG.FPW for a Foxuser file.<<

There is no PATH statement in the app.

Keep them coming.


_RAS
VFP MVP
 
Mike,

Cannot delete the existing files as there are other FPD and FPW apps installed on the server and workstations. My app is new and needs to play in the existing environment.

I am most perplexed by the fact that I have a Config file compiled into the app with no external access or -C usage to override and RESOURCE = OFF, yet the program is looking to convert.

_RAS
VFP MVP
 
I think somewhere in your application,

SET RESOURCE ON

is set by code.

May be worth a code references search on your project for keyword RESOURCE.

:)

____________________________________________
ramani - (Subramanian.G) :)
 
Hi Rick,

Perhaps codepage?
SET CPDIALOG OFF and re-build.

Perplexing indeed, and why 3 to 6 and not 3 to 8?

Regards,

Mike
 
Hi Rick

When u get an error, that got to be a difficult catch. Not this simple that I suggest. Anyway, that stays at the back of my mind until you post your find. I will post newer idea if i get one.

____________________________________________
ramani - (Subramanian.G) :)
 
Mike,

I believe the FoxUser file format changed when VFP 6 was released and is likely the reason for the "hardcoded" message. I have seen this before, but only when I am using a resource file.

_RAS
VFP MVP
 
Hi Rick,

Is it the user, or you that are seeing the error? What OS and what file permissions. Windows Find in some OS's doesn't search system and hidden folders by default. Also a logged in user possibly won't search another users folders.

To me, the error message means the file has to be there even if we can't find it.

Regards,

Mike
 
Naturally it is the users who are seeing this (I cannot reproduce it), and recent information is that it is happening only on two machines out of 10 total (it happened on the first two, so naturally it was 100% failure at the time).

Hidden file is an interesting take. I guess I am more concerned that this is a bug in VFP since I have done everything I can to avoid the resource file and it is still finding one.

_RAS
VFP MVP
 
Where are fox runtimes (dll) located? Are they in same folder as your exe/app, or they are in some Windows Common or Shared folder?
 
Rick
This is somewhat a blind suggestion but I have experienced similar when permissions are not correct or when a file or folder is read only on the server. Worth a check perhaps.


Bob Palmer
The most common solution is H2O!
 
1)
>> run-times are located in the standard run-time folder under C:\Program Files\Common Files\Microsoft Shared\VFP

So try make a copy of run-time dlls where your application is.

2)
what about DOS environment variables FOXPROCFG, FOXPROWCFG ?
Aren't they set ?
 
>>So try make a copy of run-time dlls where your application is.<<

I am not following why this would matter. Can you explain more?

>>what about DOS environment variables FOXPROCFG, FOXPROWCFG ?
Aren't they set ?<<

Ah, the old legacy stuff to bite you in the butt. This was one of the first things I checked. Nothing of the sort in the results from the old DOS SET command.

_RAS
VFP MVP
 
what do you get if you place a V6 foxuser dbf and fpt in the app launch dir on the server? Just as a matter of interest.

As I put in my prev post I had this condition with a win 98 server on a small network where other VFP apps were running and the user had shared the app folder read only.

Bob Palmer
The most common solution is H2O!
 
1)
>>So try make a copy of run-time dlls where your application is.<<
>> I am not following why this would matter. Can you explain more?

99% this is a blind way, 1% common runtime location creates a possibility find an improper foxuser from other application? I don't know. (but if you have runtimes at your application, then nobody other can update your runtimes with improper service-pack, so I think, this can be better solution? - but this has nothing with the question)

2)
If you cannot remove other foxuser files on the machine, because they are from 3-rd party applications, then try rename them temporarily. Is then the behaviour same?
 
Hi Rick,

Because VFP is so persistent to convert the FPW/DOS foxuser files that it locates, I would feed it an empty version specific one of it's own yet still specify "resource=off" in the config file. That is I would include a foxuser file in the setup but not actually use it, thereby satisfying VFP's tenacious appetite for a foxuser file and yet excluding it's use in the application.

Glenn Domeracki
Traverse City
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top