Hi,


"Geoff Worboys" <geoff@...> wrote in message
news:1983894843.20020107073011@......

> > are there any known problems when using IBO inside a dll, running a
> > script (with an error in it), shutting down, unloading the dll
> > (seems to work just fine), but, upon closing the application,
> > generates an Access Violation...
>
> > If I try this (via a lot of stuff), when closing the application, it
> > generates an Access Violation and I really have no idea where to
> > look...
>
> So you unload the DLL after the script has finished? (Sometime before
> the application is closed.)

Eh, the DLL is unloaded when the application closes...

> It could be that there is an object around that is trying to access
> another object which no longer exists because the DLL has been
> unloaded. IBO tends to create a few objects in unit initialization
> sections and I am not sure how this will impact your particular
> situation.
>
> If you can supply the callstack at the time of the AV we may be able
> to offer more help (presuming your DLL is enabled with debug info).

If there was a callstack, I'd be happy ;)

Anyway, I read the part in the IBO help file about ISAPI (and dlls)
again -- now, I've also created a TIB_Session (didn't do that yet),
just at initialization time of the DLL. That seems to remove (why?)
the AV when closing down...

But do I have to create a session component per connection then?
Guess, so, right?


--
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."