>>>>I've renamed the config file to config.fpw, and put a _STARTUP = "myfile.prg" statement in it.
>>>
>>>Change that to
>>>
>>>_STARTUP=myfile
>>>
>>>and make sure that you have an FXP file, not just the PRG file.
>>
>>No joy.
>>I used COMPILE to create an .FXP file from my .PRG.
>>Via filemon, I see my app looking for several .FXP files, including REPORTBUILDER, REPORTPREVIEW, REPORTOUTPUT, GETXPR, and GENPD, but not mine.
>>I assume my app's project does not need to know anything about this program, right?
>>I do have it in the project but did not include it in the .exe.
>>I'm back to testing with no internal config.fpw, just an external one invoked using the -c command line parameter.
>>
>>I tried setting the title text and several other things that might show that my config statements are being executed but haven't seen anything that changes - what's a good one to use for this?
>>
>>I have seen a couple of things in the documentation about cases where VFP will ignore statements in a config file but as far as I can tell.
>>
>>
>>I'm stumped -
>
>Are you trying to get "COMMAND" or "_STARTUP" to work while firing off an EXE you built with VFP? I think the "COMMAND" and "_STARTUP" are only used when starting VFP IDE up. I think exe's you build and don't use those commands in the config file.
Yes, that is what I'm trying to do.
I have a shipping app with a problem that I'd like to try to fix without re-releasing the app, as a temporary fix.
I'd like to send the customer a config.fpw file, an .FXP file, and not touch their .exe file.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only