>>>>Hi Everyone.
>>>>
>>>>I have a VFP 3.0b app that at different times, sets up some DDE conversations with a couple of 16 bit applications. When I issue the QUIT command for the DDE server app, under windows 95 I get a GPF. This does not occur under windows 3.1. Is there anything that I can do to change thsi ugly behavior under windows 95? I cannot replace these 16 bit server apps with 32 bit ones because the app has to be able to run on both platforms for about the next year.
>>>>
>>>>TIA.
>>>>
>>>>Marcia
>>>
>>>I assume that you're using DDEExecute to tell the application to terminate, and that when it's issued you get the GPF. I think the problem may be caused by the DDE channel being still opened without a server related to it. I'd suggest that you first close the DDE channel, then, using the Windows API, shutdown the application. Unfortunately, I haven't done this.
>>>
>>>Since the apps are 16 bit, I would assume that you'd use the Win 3.1 API call TerminateApp through RegFN/CallFN. If you need additional help, please post a reply.
>>>
>>>HTH,
>>>
>>>George
>>Hi George.
>>
>>Thanks for the help. Yes! I do need some additional help to set this up. Are the relevant commands available thru VFP help files? If you tell me what to look up, I'm there. I am curious, though. Why isn't this issue of using DDEExecute to send a quit command cause the GPF under window 3.1?
>>
>>Are you going to be in San Diego tomorrow? If so, maybe I'll see you there!
>>
>>Thanks again.
>>
>>MArcia
>
>Marcia,
>
>Well, I've got more than a bit of egg on my face from this one (In keeping with my reputation, I have to say that the "yokes" on me). I forgot that TerminateApp is a debugging function and won't be available to your application. Sorry!
>
>However, since I'll have to deal with a similar scenario, I decided to run a test or two to see what was going on and perhaps be able to gather some information for us both. So, here's what I did. I started the same 16 bit app (Lotus 1-2-3 Release 5) from both FPW 2.6a and VFP 5.0 (separate sessions). I then established a DDE channel, and sent 1-2-3 its macro command to exit. In both instances, 1-2-3 terminated without causing a GPF. Additionally, I closed the DDE channel after 1-2-3 had shutdown. In both cases, the result of the call indicated no error occurred (the value returned by DDETerminate was .F.).
>
>I know this doesn't help much, but from the above, it appears that the problem is not with FoxPro nor with Windows, but rather the 16 bit application you're communicating with. If you can provide some more information (what app, etc.) perhaps I can help further.
>
>I wish I was going to San Diego. Maybe next year I'll be able to make it. If they decide to have it in Atlanta, I'd be sure to be there. Enjoy yourself.
>
>George
Hi George.

San Diego was wonderful. Exhausting, but wonderful. The next DevCon is not in Atlanta next year, but much closer to home...Orlando.

One of the 16 bit apps that I am talking to is DLWIN..a cadd viewer. The second one is not a commercial product. It is a module that
I wrote in Delphi 1.0. When I send the quit command, the Delphi app just does an Application.end.

Thanks.

Mga