>>>>>OK I have a strange situation.
>>>>>
>>>>>I have a bug in a just released version of our POS app. Its not a show stopper but its highly annoying. I'm trying to find a way to get an update out with out a new release.
>>>>>
>>>>>The EXE is 6mg and sending that is not an option. Some locations can only accept 1mg email and have little to no web access. Distribution is by physical media and some locations can take 2+ months to get a version and get it installed. Rolling out a new version only weeks after the last would be a logistical headache.
>>>>>
>>>>>I had two ideas:
>>>>>1) Their is a patch point in the EXE where I can send and run code. I tried sending a replacement VCX for the one with the bug. I can force the app to access this exe and not the one in the EXE by rewriting the set procedure and set classlib paths. Unfortunately once in the new VCX it can't seem to find any of the VCX's or forms that are in the EXE. I've tried many varriations of accessing the new VCX and they all seem to fail at differing points when I need code from the EXE.
>>>>>
>>>>>2) I isolated the actual bye change (at least I think I did) and wrote a program to go to that spot in the EXE and make the change which made the EXE one byte longer (as expected). But the resulting EXE will not run. The vfp runtime starts and then I get an "is not an object file" error. My bet is something needs to be changed as a result of making one section longer but I do not know what.
>>>>>
>>>>>
>>>>>I'm afraid that I'm SOL and with 80+ locations distributed locations they may just have to live with it till the next release but I'd like to do something if I can.
>>>>>
>>>>>Any ideas?
>>>>
>>>>You could consider a professional patch product such as RTPatch: http://www.pocketsoft.com/
>>>I'll give that a try.
>>>
>>>Any other suggestions just in case?
>>
>>No, I think a patch product is ideal for your circumstance. Effectively it should do your second method for you, taking care of all the nitty-gritty details. You might want to ask the vendor if their product can patch VFP executables. I'm wondering whether there is some sort of checksum written to a VFP executable, which might be why your manual patch attempt is failing.
>
>
>I got the trial from pocketsoft and generated and tested a 59k patch this will be perfect.

That's good to know - thanks for the follow-up.