I assume when you install a new version of IB, you uninstall the previous
one, rebuilt the new and install... and maybe you delete the compiled
package files before rebuilding.
That's said, it seems like you stepped in some object or memory location
that IBO handles itself. Other source of those errors are destructors that
forget to call the inherited virtual destructor, but probably this case
doesn't apply to you.
Maybe you'll want to use the free memproof (a leak detector) to see if it
helps you to discover something. Beware that it might report some errors
that aren't errors... the perfect leak tester doesn't exist.

C.

> -----Original Message-----
> From: Don Gollahon [mailto:dlgllhn@...]
> Sent: Miércoles 21 de Febrero de 2001 23:08
>
> I'm getting an EAccessViolation on exit of my app. Everything is running
> fine except for this. I've stepped through it as best I could. Upon exit
> the program exits my form and then goes through ib_utils, ib_session, and
> ib_header. It executes the following code several times:
>
> XSQLDA_LENGTH
> FreeBlobRefList
> FreeBlobNodeData
> HexTextToBinary
>
> The final code I could step into was:
>
> BinaryToHexText
>
> and just when I step through the "end" of that function I get the error:
>
> Exception EAccessViolation in module VideoCat.exe at 000FFCCE.
> Access violation at address 004FFCCE in module 'VideoCat.exe'.
> Read of address 00000000.
>
> I'm using Delphi 4, Windows 2000, IB 6, and IB_Objects 3.6Cf.
>
> Thanks.
>
> Don Gollahon
> (dlgllhn@...)
> "What in Eternity does it matter?"
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>