🚀 go-pugleaf

Classic codeguard and ADOExpress incompatibility... don't really know that
there is or isn't a memory leak, but there doesn't seem to be much you/I can
do
about it...

I believe it to be a codeguard bug because of the following example:

If you open an ADO connection using its Open() method CodeGuard reports
a similar error report but if you open it using its Connected property it
says that
everything is ok, even though changing the Connected property only calls the
Connection object's Open() method.

HTH,
    Jurko

"Markus" <kemetter@mbnet.fi> wrote in message news:3c5e51b2$1_2@dnews...
>
> Hi,
>
> I'm creating a TADODataSet like this:
>
>  TADODataSet *MyDataSet = new TADODataSet(this);    // tried this also
with
> NULL as argument, same result
>
> Works fine but when switching codeguard on it stops on the constructor of
> TADODataSet in ADODB.hpp:
>
>  /* TCustomADODataSet.Create */ inline __fastcall virtual
> TADODataSet(Classes::TComponent* AOwner) :
>   TCustomADODataSet(AOwner) {  }
>
> and says:
>
> Error 00043. 0x130C10 (Thread 0x05AC):
> Method called on illegally casted object: Attempt to access 584 byte(s) at
>  0x01176B74. The 'this' pointer points to heap block 0x01176B74 which is
> only
>  580 bytes long.
>
>
> Any ideas?
>
> Markus
>
>
>