🚀 go-pugleaf

"Martin C" <martinc@aol.com> wrote in message
news:3f4a98a3@newsgroups.borland.com...

>    if(Message.CopyDataStruct->dwData > 0)

You need to use a unique value for dwData.  Don't just assume any arbitrary
value.  The VCL itself uses WM_COPYDATA for its own internal usage, as may
other windows/components.  Your code needs to use its own unique value as
well, and then test for that specific value so that your code knows that it
is really intercepting your WM_COPYDATA message and not someone else's.

>    AnsiString
TheRecievedString=reinterpret_cast<char*>(Message.CopyDataStruct->lpData);

You are not taking the cbData value into account at all.  You should be
doing that, as that tells you how many bytes are in the lpData.  Do this
instead:

    char *ptr = reinterpret_cast<char*>(Message.CopyDataStruct->lpData);
    AnsiString TheRecievedString(ptr, Message.CopyDataStruct->cbData);

>          Memo1->Lines->Add(TheRecievedString.c_str());

You don't need to use c_str() there.  TheRecievedString is an AnsiString,
and Add() takes an AnsiString parameter:

    Memo1->Lines->Add(TheRecievedString);

> and  I really receive the data from the dll, but corrupted at
> the end of each string received...!!

That typically happens if you are not sending the null terminator along with
your string.  Your current receiving code is expecting a null terminator to
be present since you are not taking the actual data length into account.
But if you do not actually send the null terminator, then you are going to
get mixed results.  So you need to either make sure that you always send a
null terminator with your string data, or else utilize the cbData value, or
better yet, a combination of both.


Gambit


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/03