Hi Geoff,

No, I don't have any code in the BeforeDisconnect event.
Below is the callstack just after the access violation.

77E8F142 C:\WINNT\system32\kernel32.dll
40005B68 C:\WINNT\System32\rtl60.bpl
77F8F3FA ntdll.dll
77FA0346 ntdll.dll
00430A33
Ib_components::TIB_Connection::GetCharacteristics(Self=:00C96510)
0042FE64 Ib_components::TIB_Connection::GetSQLDialect(Self=:00C96510)
0043E3A0 Ib_components::TIB_Statement::SysDeallocate(Self=:00C97028,
AllowCachedHandle=true)
00431428
Ib_components::TIB_Connection::DeallocateStatements(Self=:00C96510)
00430F12
Ib_components::TIB_Connection::SysBeforeDisconnect(Self=:00C96510)
00430DDF Ib_components::TIB_Connection::SysDisconnect(Self=:00C96510)
0042DFA4 Ib_components::TIB_Connection::Disconnect(Self=:00C96510)
00401DE0 TForm1::Button1Click(this=:00C9480C, Sender=:00C96058)

Thanks,
Peter.

-----Original Message-----
From: Geoff Worboys [mailto:geoff@...]
Sent: Thursday, July 17, 2003 5:12 PM
To: Peter Vinci
Subject: Re: [IBO] Problem reconnecting to the database

> I've tried stepping through the source code and I've found
> that an AccessViolation is raised in the
> SysUpdateCharacteristics function when calling Disconnect or
> ForceDisconnect.
> The exception is caught by the Disconnect function but
> causes the API_Disconnect call to be bypassed.

> Anyone know what could be wrong?

Do you have any code attached to the BeforeDisconnect event?

I am trying to work out where SysUpdateCharacteristics is
being called - since it does not seem to be part of the normal
disconnect processing. If you dont have code in the
BeforeDisconnect event, can you give the callstack that results
in the call to SysUpdateCharacteristics.

--
Geoff Worboys
Telesis Computing