Welcome Guest. Please Login or Register. Apr 5th, 2018, 10:22pm
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
Re: WM_COPYDATA problem
« Reply #4 on: Sep 25th, 2013, 1:52pm »
[quote author=Richard Russell All I can say is that receiving a 'No such variable' message is consistent with heap corruption, so that's something to investigate. [/quote]
OK - I will double check...
[quote author=Richard Russell Incidentally - although it can't be the source of the problem - your comment 'This has to be fast' seems rather incongruous alongside the actual code, which appears to have been written to be about as slow as possible!
Richard. [/quote]
Thanks for that. Like many experienced programmers with precious little time to go up the learning curve, I usually opt for things that are least likely to be additional reasons for something to break. But I am sure it can be re-written to be faster - your suggestions would be most welcome.