Subject | Re: [ib-support] Access Violation 'USER32.dll' extended info |
---|---|
Author | lester@lsces.co.uk |
Post date | 2001-10-14T08:42:04Z |
( Third attempt at sending this - BTInternet is crap but
it's their phone bill ! )
because of the remaining niggles in Interbase, and I never
even started using IBX, but a couple of comments.
other than IB/FB. The one thing I do still get is a problem
where an application will not shut. The fix that usually
works is to close the connection in the CanClose event,
trapping any error and working out what is wrong. It usually
relates to Windows trying to run events that are no longer
needed, but still try to access the connection.
orphan connections messing up the server. Now I monitor how
many connections are open, and flag when the max number goes
up. Since I have a fixed number of 'users' (dumb computers
without operators) this number should not change, and has
not this year, but still did with the earlier IB6 code.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
it's their phone bill ! )
> The system isI'll have to bow out at this point - I switched to Firebird
>
> Windows 2000 Pro, SP1
> Interbase 6.01 (not Firebird) ~ I havent gone to firebird as IB had
> been working without a hitch and I want to keep the architecture as set
> as possible
> IBX 4.62 Delphi 5 Update 1
because of the remaining niggles in Interbase, and I never
even started using IBX, but a couple of comments.
> An issue which may be related is the problems in the tcp servers As I said - USER32 errors are usually caused by something
> sometimes (and it seems to be when Interbase is having the problems
> described above) these apps dont shutdown when I click the close
> button/AltF4 .. they disappear from the taskbar but remain in the task
> manager process list, and even worse they block a reboot from occurring
> until I manually terminate every process that has done this .. if anyone
> can explain this I will be even more grateful (and feel the beginnings
> of relief, as you can imagine!)
other than IB/FB. The one thing I do still get is a problem
where an application will not shut. The fix that usually
works is to close the connection in the CanClose event,
trapping any error and working out what is wrong. It usually
relates to Windows trying to run events that are no longer
needed, but still try to access the connection.
> If there is any more information I can provide to help clarify theOne of my main reasons for moving to IB6 was because of
> situation, Ill be only too happy to do so :-) (as you can imagine!)
orphan connections messing up the server. Now I monitor how
many connections are open, and flag when the max number goes
up. Since I have a fixed number of 'users' (dumb computers
without operators) this number should not change, and has
not this year, but still did with the earlier IB6 code.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services