>>>>>>
>>>>>>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
>>>>
>>>>Marcia,
>>>>
>>>>One thing you didn't mention was what was GPFing, the 16 bits apps or VFP. If it's VFP, the problem may be relataed to the graphics card. What makes me say this is your mention of the CADD viewer and a couple of recent threads that mentioned this. I believe that there's a list of the "problem cards" available in the Microsoft VFP area, but I don't know the exact location. Perhaps one of these kind folks will post it in response to this.
>>>>
>>>>If it's the 16 bit apps, then I'm afraid I'm out of ideas.
>>>>
>>>>DevCon in Orlando is a real possibility. My mother-in-law lives there (Lake Mary actually) and I've been down there a number of times. The only problem is the time of year. I've got kids in school. However, it's not a bad drive (about 8 hours) and from the photos, it looks like everyone had a great time, both at DevCon itself and San Diego. If I do go, I'll have to remember to bring my pool cue.
>>>>
>>>>George
>>>Hi George.
>>>
>>>It is not VFP giving the GPFs. It is the 16 bit apps. And like I said, only under windows 95. Everything is peachy keen under windows 95.
>>>
>>>Thanks.
>>>
>>>Marcia
>>
>>Maricia,
>>
>>I don't think that either VFP or Windows is the problem here. The reason that I say this is based on my experience with other 16 bit applications as mentioned earlier. I to test the validity of this, I'd try to initiate a DDE conversation from some other application with them. If I get the same results then I'd know where the problem was. In that case, I'd contact the appropriate vendor for support.
>>
>>Peachy Keene? I grew up with him as a kid on the South Side of Chicago. Good guy.(g)
>>
>>George
>Hi George.
>
>If it's the 16 bit apps, why don't I have the same problem under windows 3.1? Hmmmmmmmmmmmmmm.
>
>Marcia

Marcia,

There was a logical reason for me saying that your problem was being caused by the 16 bit apps rather than FoxPro. DDE is, in reality, part of the Windows messaging system. All that's really going on is that text messages are being passed between applications. When FoxPro, through DDEExecute, tells an application to do something, it's must tell it in a way that the application understands (such as its macro language). After that, it's up to the application to carry out the instruction.

Given this, there are two possible reasons for something going wrong. Either the command passed to the application isn't valid or the application itself isn't executing something properly.

Since you didn't have the problem in 3.1, I would assume that the command is valid. You might, however, want to test the second possibility. Most any application that supports a macro language (such as a word processor or spreadsheet) will probably include DDE command syntax in it. To test, all you'd have to do is write a short macro to open a DDE channel with one of the applications you're having problems with and, using the same syntax, tell it to shut down. If it GPFs then, you know that the problem is with the application and not FoxPro.

I wouldn't put too much stock in the fact that the apps don't GPF under 3.1. Win95 is a very different environment. The one thing that I've noticed is that if an application doesn't follow the 3.1 rules, it's more likely to have problems under Win95. It may work fine under 3.1 however. This may be the case here.

George