Possible DDE bug?

iwadmin · Post by **iwadmin** » Tue Jul 04, 2006 9:56 am

Hello,

I have been practicing the use of Macro Scheduler for an automation process involving the transfer of data to Excel.

Searching through the forums I have found that it is possible to use different methods to transfer the data. I have tested all of the suggestions, but I have found DDE to be the fastest method.

Everything works fine up to 64k of data (txt file size of 65535 bytes) after that I get an Application Error: "Exception EStringClass msched.exe at 000AF2EC. FindResource on FunctionNames failed" and then "The instruction at 0x00401f01 referenced memory at 0x30363030. The memory could not be written"

I have found a way around this by inserting every single line read from the file through DDE, but this is slower that inserting all the data at once, not as slow as the other methods, though.

I have searched on the internet to see if it was a MS DDE bug, but the only reference I found on the 64k limit was regarding 16bit apps and Windows 95/98. I am, of course, executing Macro Scheduler on XP sp2 or on Windows 2k3 server...

Could this be a bug or is it a limitation?

Thanks.

Post by **Marcus Tettmar** » Tue Jul 04, 2006 11:52 am

I understand that DDE is limited to data sizes of 64k. DDE is actually a very old technology. Microsoft have pretty much abandoned it and there is no guarantee that it will be in future versions of Office. A more future-proof and less restrictive approach would be to use VBScript/ActiveX:

http://www.mjtnet.com/forum/viewtopic.php?t=1470
http://www.mjtnet.com/forum/viewtopic.php?t=1464