> >
> > The FoxPro resource file FOXUSER.DBF holds a variety of resource information (for example, window positions, color sets, Browse window configurations, label definitions, and so on.). FOXUSER is a standard FoxPro table with an associated memo file (.FPT). If the index file does not exist, it is created when the FOXUSER file is opened.
> >
> > It is possible to define the location/name of the Resource File with a command line switch...
> > -LFileName
> > Specifies a resource file (including path if necessary) other than the default. Using this switch makes it possible for you to use Visual FoxPro in a language other than the current language specified by the system.
> >
> > Also, it may be set within the program itself, which you would not be able to determine from an .exe. Is the path of the old folder the same as the new folder including the drive letter?
> >
> > This FOXUSER.DBF file may also be corrupted. You could also try deleting it from the folder and it will create a new one.
> >
> > KTB
>
> Hello Ken!
>
> First of all, thanks for your help.
> But it doesn't work!!!
>
> I can exclude a problem with the Paths, they are just the same as on the old machine.
> the whole Error message is : "Visual FoxPro Cannot start - Could not load resources"
>
> I tested something new today, maybe this could help to solve the problem: I started Visual Foxpro 5.0 and then I made the Application run with "Program - Run"
> and this worked!
> After this I tried to start the Application normaly, but this failed again.
>
> The Resource File "Foxuser.DBF" and its Memo-file are existing with the same contend and on the same paths on all machines I tried, as I told you already, it works everywhere, but not on this one Computer
>
> Has anybody more Ideas to this
>
> Regards
> A very confused
> Thomas Mauric

How are you trying to run the .exe? If from a shortcut, make sure the shortcut is starting up in the proper directory. Does it run if you double click on the .exe from Windows Explorer?

So you say that running the .exe from within VFP5 works? That means that VFP5 is setting up some paths for you and the .exe is not.


KTB