> Why does this happen in v8.1 and not 8.0 ?

> Hi,

> > procedure DefaultRecv(ADestStream: TIdBuffer; var VByteCount: integer);
> >   begin
> >     // No need to call AntiFreeze, the Readable does that.
> > -->  VByteCount := IOHandler.Recv(ADestStream.Memory^,
ADestStream.Size);
> >   end;

> > Why does this happen in v8.1 and not 8.0 ?

> I don't know this, but what i would do is make some tests to see if the
> buffer is assigned before actually using it, so rewriting the proc as
> follows:

> > procedure DefaultRecv(ADestStream: TIdBuffer; var VByteCount: integer);
> >   begin
> >     // No need to call AntiFreeze, the Readable does that.

>        // check if the buffer exists
>       if assigned(ADestStream) then
>         VByteCount := IOHandler.Recv(ADestStream.Memory^,
ADestStream.Size)
>      else
>         vByteCount := 0; { or -1 to indicate that your buffer wasn't
> assigned or something..}
> >   end;

> This will prevent many a problem when somehow this procedure gets called
> somewhere halfway the destruction parts on termination of your
application.

> "Arthuro" <hexorha...@vaxor.com> wrote in message news:3b402757_2@dnews...
> > "Steve" <s...@icon.co.za> wrote in message news:3b3fda5c_1@dnews...
> > This will prevent many a problem when somehow this procedure gets called
> > somewhere halfway the destruction parts on termination of your
> application.

> Hi Arhuro

> I tried a if assigned...etc and I still get a access violation ? So I cant
> see what VByteCount returns.
> Do you think its a Indy 8.1 problem or a problem with my application ? Im
> assuming the problem is with 8.1 because my code has been working with
'all'
> the previous versions of Indy....unless theres a problem with my code and
> now only Indy 8.1 is showing it ?