It may be that Excel is that slow, but DDE in general is not.  Obviously,
you can make anything slow if you code it to be, but it looks to me as if
DDE is relatively quick.  I have a VC++ application that accepts data from
other applications which are usually VB.  The transfer time is only
perceptible if the exchange involves hundreds of records.

I know, I know, it should be COM, but the other apps tend to be garage shop
applications and DDE is a helluva lot easier to explain.

--McD

----- Original Message ----- 
From: "John Pearson" <xero@cmc.net>
To: "pic microcontroller discussion list" <PICLIST@mitvma.mit.edu>
Sent: Friday, April 29, 2005 1:58 AM
Subject: [OT:] Is DDE that slow?


> I am trying to incorporate DDE into a  MS VC++ MFC program. The program
receives serial input, and I want to pass it along to Excel via DDE. As soon
as I make the first data poke to Excel, my program slows down so much I can
see each serial port character displayed on the screen one by one, instead
of a line of data appearing instantly (9600 baud), even while there is no
more data being sent to Excel. If I break the DDE connection, the program
resumes normal speed again. Is this typical of DDE, or is something wrong
somewhere. Or is there some kind of messaging continuing between Excel and
my app even while there is no DDE data exchanges occuring?
>
> Please suggest I use COM only if you have some well documented stand-alone
VC code examples I can incorporate into an MS VC++ MFC app.
>
> Thanks
> John
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist