Re: VFP7 application booted out - DDE causing it?
From: Anders Altberg (x_pragma_at_telia.com)
Date: 03/21/05
- Next message: Phil Hollingworth: "A Bug in VFP 9.0? - Error: 1808"
- Previous message: Anders Altberg: "Re: Communicate with vb.net application"
- In reply to: Bernie Beattie: "VFP7 application booted out - DDE causing it?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Mar 2005 12:40:28 +0100
DDE was replaced by COM (Common Object Model) technology, where you
initialized the connection and create a reference with CREATEOBJECT(),
CREATEOBJECTEX() , GETOBJECT() or GETINTERFACE().
-Anders
"Bernie Beattie" <BernieBeattie@discussions.microsoft.com> wrote in message
news:0AF14250-0063-416A-8D0B-753E37F4E68E@microsoft.com...
> I posted the following a few days ago-
> At one of our customer sites, they are having frequent problems of being
> booted out of our VFP7 application after it has been minimised for a
while.
> They are also running a GIS application (ArcView). The 2 applications
> actually communicate with each other using DDE services. It is happening
on
> all their pcs. To me this sounds like Windows (2000 and XP) memory
management
> not coping very well but are there other issues I should be looking at?
This
> has only started happening since they upgraded from our VFP6 application
> version to our VFP7 one. They may have also had some network changes but
> it's hard to pin them down.
>
> The only replies mentioned that DDE is old fashioned. It is code from a
few
> years ago and there hasn't been any reason to change it as it was working
> well with the VFP6 application. What should we be using now?
>
> Thanks for any suggestions.
> Bernie
>
- Next message: Phil Hollingworth: "A Bug in VFP 9.0? - Error: 1808"
- Previous message: Anders Altberg: "Re: Communicate with vb.net application"
- In reply to: Bernie Beattie: "VFP7 application booted out - DDE causing it?"
- Messages sorted by: [ date ] [ thread ]