Different behavior. how so. ?
my startup file(included in my exe file ) has the all important read events where the app file does not.
Could that be your trouble. ?
You do need to have a startup prg in your exe.
the reason byw, that I dont include my app, in my exe... is that I like having fast loading programs, I can get my exe down to about 12K keeping everything out of it, and having class files and app completly seperate.
Bob Lee
>That was my idea too, but I am getting different behavior on machines running VFP and those running the VFP runtime. I thought if I could include the APP in an EXE, I might get around this.
>
>Thanks
>
>Rex
>
>>What I do is create the app file, (which gets updated.) and the exe stays very small. That way the exe I never have to update, but the app file. (well you know. updates are never ending )
>> I can have the user just copy the new app file to the working directory. (or have the exe check for a newer version over their network. and copy it before the exe calls the app.... That way the user always has the latest copy of the app...
>>
>>Bob Lee
>>
>>>All,
>>>
>>>I have a module compiled into an .APP. I need to call this module from an EXE. Can I include the APP into the EXE, or can I leave the APP as a separate file? I now have the APP separated from the EXE and I am getting errors on machines with just the VFP runtime installed. If I need to combine the two, how can I do this?
>>>
>>>TIA
>>>
>>>Rex
In the beginning, there was a command prompt, and all was well.