>>>>>>>
>>>>>>>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.
>>>>>
>>>>>I'm pretty sure _STARTUP and COMMAND are ignored unless starting the VFP IDE. You could build another EXE and set the _ASCIICOLS in that one and have that one "DO" your EXE. If they have shortcuts they would need to update them all to the new exe. So it might not be a great solution.
>>>>
>>>>
>>>>Thanks Chuck,
>>>>
>>>>Before I give up on this idea, does anyone else have any thoughts about this?
>>>>How does one know which config file functions work with VFP runtime and which work only with the IDE?
>>>>
>>>>"If you intend to distribute your Visual FoxPro applications using a run-time library, you can establish configuration settings in two ways: with a configuration file..."
>>>>
>>>>Looks like 'Starting Visual Foxpro' means starting the IDE although it seems ambiguous to me in the documentation.
>>>>Wishful thinking I guess -
>>>
>>>
>>>Are the reports built into the EXE as well? Does any file lay outside the EXE?
>>
>>REPORTOUTPUT.APP and REPORTPREVIEW.APP are outside the EXE.
>
>I don't have much help for you. I was thinking if a report file was outside you could put a function call into the report that would set the var or if you used a database container and tracked database events that you could add to the DBC_OpenData event the code to set _AsciiCols.


OK
Thanks very much for the help!