Well, if I remember correctly, there was something extra you had to setup in the Properties of the DOS shortcut for running the Foxpro with the additional memory manager (that EMM386 ... Extended Memory Manager) if you compiled under FoxproX ... at least I *think* that's what it was. I'm assuming that since your customers already have a shortcut set up to run this app, and they are probably still trying to run the updated version from that shortcut, then it's not currently expecting whichever version you just gave them.

So, if you compiled it under X then I'm guessing that a regular compile is what it's looking for.

I had a few old FPD 2.0 apps that I wrote in the early 90's and maintained until about 2000 or so (cash register polling). I probably still have some old customers who still use the thing, but I haven't done a darn thing to it since then and don't intend to (I'm totally out of that business now anyway). I have the source code lying around somewhere, but damned if I wanna drag it out and mess with it!!!! <g>

~~Bonnie


>Thanks Bonnie
>
>I must admit that I've generally only had to do maintenance with FPD26, taking over other people's progs, rebuilding apps, etc., but never getting well stuck into it. I wasn't aware of these issues. I've been using VFP for some 12 years now and it kills me to have to use 2.6 :-)
>
>Terry
>
>>Terry,
>>
>>I haven't used Foxpro DOS in a very long time, but I think you might be right that the problem is that you compiled with FoxproX and probably should've used Foxpro. I remember that there were issues with one and not the other with Win98, I just can't remember exactly what the issues were.
>>
>>Wanna try it again? <g>
>>
>>~~Bonnie
>>
>>
>>>I've just sent out a bug fixed system (in FPD26) to a client who has just reported to me the following sequence:
>>>
>>>On trying to run the system from his existing icon he gets the message:
>>>
>>>"This program is set to run in MS-DOS" and says that he needs to close all other programs.
>>>
>>>He is in W 98 and nowt else is running, so he answers Y" to the continure message.
>>>
>>>A message then pops up that "AMM386 is not installed".
>>>
>>>He hits a key and the computer reboots.
>>>
>>>Now, it's possible I built this system using FoxproX, rather than Foxpro. Could this be the reason? As in my other thread today, this is the same system that many clients are/were happily using. This is embarrassing as this was meant to fix a wee bug he had (to do with the printing to a file from the other message) but now it's catastrophic.
>>>
>>>I'm losing the plot today as I have at least 3 clients with problems so please HELP!!!!!
>>>
>>>'ppreciate it
>>>
>>>Terry