>>>>>>>>>We have the runtime for 3 installed on all of the machines here (including my development pc). I have written an app in 5 and have created a generic setup with the wizzard. After running the setup on a machine, I run my app, which is on the network. When it runs, I get a Fox Error Asking if I want to Convert 3.0 Resource File to 5.0 Format. It doesn't matter whether I say Yes or No, either way, I get another Fox Error saying "File 'myapp.exe' does not exist" Then it quits. In my config.fpw I have a line Resource = C:\Windows\Temp\FoxUser5.Dbf So, I thought, it wouldn't conflict with the 3.0 resource files. What does all of this mean and how do I fix it?
>>>>>>>>>
>>>>>>>>>TIA
>>>>>>>>In config.fpw "set resource off" then if you need it set it to appropriate one in your startup.
>>>>>>>>Cetin
>>>>>>>
>>>>>>>That didn't work. Still get the same Errors. Any other ideas?
>>>>>>>
>>>>>>>TIA
>>>>>>Your config.fpw is the one that's used and "resource=off" fail ? Strange worked all the time for me. Other ideas, in a manner based on the fact that you can disable or change resource file via config.fpw or command line.
>>>>>>You could keep more than one config.fpw - config3.fpw and config5.fpw. In commandline (shortcut typically) "myapp.exe -Cconfig5.fpw" and you must be sure, you're really indicating different resource files. If you don't need them just "resource=off" is the best.
>>>>>>Cetin
>>>>>
>>>>>I'm including the config.fpw in the executable. I've been wondering when I should actually use a resource file? What benefits are gained by using/not using a resource file?
>>>>>
>>>>>TIA
>>>>Keep config.fpw external. Resource file first of all keep window, toolbar positions etc. If you ever using Fox diary it also needs resource file. Generally you keep all of them in your app and don't need it (in old times it was needed more for pdsetup, preferences etc). I don't use it anymore.
>>>>Cetin
>>>
>>>Ok, putting an external copy got rid of the first error asking about the resource file. Now I'm just getting the error "File 'timecard.exe' does not exist" Any ideas on that one? Why does the config.fpw not work when it's included? Let me rephrase that. Everything in it seems to work, except for the resource line, why?
>>Now try toexplain it w/o making definition errors. Your exe is really not the only one that executes and has control. There is also a runtime.dll (vfp500.dll). If you include it, it's accessed "later", after a resource is set. resource in fact not the only one that would be affected but most them are burried with FP2.x (long live FP 2.x). In VFP I think _screen=off would be affected the same way, and if ever used tmpfiles, sortwork,progwork,editwork etc.
>>Now "timecard.exe" doesn't exist is extremely app specific. Maybe you should hard code its path. It's not the same place where you start your exe and home(). Home() is typically windows\system (winnt\system) whereever the vfp500.dll is. For path problems also in config.fpw you could use "default = cDefPath" and "path=cPath".
>>Cetin
>
>You lost me here. Maybe I should hard code its path? Where would I do this? Timecard.exe is the file that I'm running. It's the main executable, and I don't call any other exe's or app's. Also, I don't reference Home() anywhere in my code for this app. As far as including vfp500.dll, I didn't think that was allowed. Even if it is, why would you ever want to do that? Isn't the whole idea of using a dll is that it is sharable between apps? Including it, would defeat that purpose.

And now I'm lost too. "File 'timecard.exe' does not exist" where does this message come from ? If it's the main executable, how you start it ? In config.fpw is there a line with "command=" or something like that ?
I didn't also mean to include VFP500.dll, only wanted to say if you ever use home() in your app, it refers to vfp500.dll's dir. It's sharable of course and after just one setup, if you ever need to deliver another exe all you need is to copy your new distribution tree w/o using setup again.
Cetin