Michael


As a guess at that point the engine has been freed.

Roy Lambert

On Sat, 11 Aug 2007 08:02:02 +0100, Roy Lambert
<roy.lambert@skynet.co.uk> wrote:

>As a guess at that point the engine has been freed.

Maybe. I checked and the engine is not nil at this point though. And
if I remove the line in the destroy event it still AV's somewhere
after leaving this event..

Michael,

<< For some reason I can't get breakpoints to work. But through logging I
have traced the problem to the DataModuleDestroy event. All I do there is
set the DBEngine.Active:= False; Why would this cause an AV? >>

Is the data module declared as the first form/module in the creation order
for the project ?

--
Tim Young
Elevate Software
www.elevatesoft.com

On Mon, 13 Aug 2007 16:21:34 -0500, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< For some reason I can't get breakpoints to work. But through logging I
>have traced the problem to the DataModuleDestroy event. All I do there is
>set the DBEngine.Active:= False; Why would this cause an AV? >>
>
>Is the data module declared as the first form/module in the creation order
>for the project ?

No second. I tried putting it first and last but get the exact same
problem no matter which position it is in.

Michael,

<< No second. I tried putting it first and last but get the exact same
problem no matter which position it is in. >>

It should be first if you're referring to it in any subsequent forms that
are also auto-created.

Are you using a shared memory manager or any runtime packages in the DLL ?

--
Tim Young
Elevate Software
www.elevatesoft.com

On Tue, 14 Aug 2007 16:51:38 -0500, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< No second. I tried putting it first and last but get the exact same
>problem no matter which position it is in. >>
>
>It should be first if you're referring to it in any subsequent forms that
>are also auto-created.

There is only one other form and it does not refer to the DataModule.

>Are you using a shared memory manager or any runtime packages in the DLL ?

I am not using a shared memory manager. The only third party packages
used in the dll besides EDB are the TurboSynch Palm components from
TabDee. Note that the conduit dll had no problems at all when using
DBISAM.

Michael,

<< I am not using a shared memory manager. The only third party packages
used in the dll besides EDB are the TurboSynch Palm components from TabDee.
Note that the conduit dll had no problems at all when using DBISAM. >>

I understand, but that really doesn't mean much in the grand scheme of
things since DBISAM is a completely different product.

If you want to send me the source code to the project along with any
components used, I can test it here and find out what the issue is.

--
Tim Young
Elevate Software
www.elevatesoft.com