Hi Guys,
Given the normal EDB configuration - Engine/Session/Database/DataSets.

And assuming one or more DataSets are Open.

When closing an App, is it acceptable/safe to simply close the Engine, EDBEngine.Close, or is it better to close the DataSets/Database/Session/Engine in order?

Or, doesn't it matter one-way or the other?

Just curious.

Regards,
Ian

Ian


Most of the time I'll just let the app (or form)  close and let it sort out what needs to be closed in what order. The only time I bother about things is in the case of some databound controls where there is an OnChange event and I have to add code to stop the control reacting to the table going AWOL

Roy Lambert

Hi Ian,

<< Given the normal EDB configuration - Engine/Session/Database/DataSets.

And assuming one or more DataSets are Open.

When closing an App, is it acceptable/safe to simply close the Engine, EDBEngine.Close, or is it better to close the DataSets/Database/Session/Engine in order?

Or, doesn't it matter one-way or the other? >>

You only need to close the engine, but I close all of them in order like you listed because I'm fussy.  

= Steve

I am with Steve on this.

I just had a quick look in the help but could not find it, however I do
remember Tim writing somewhere that closing the Engine will first close
anything else still connected.

In spite of that I do specifically Close the Database then Session then
Engine while I imagine Tim rolling his eyes!

But if I had stuff open/active in the IDE for some reason, I simply
Close the Engine before closing the project.

Malcolm

Ian,

<< When closing an App, is it acceptable/safe to simply close the Engine, EDBEngine.Close, or is it better to close the DataSets/Database/Session/Engine in order?

Or, doesn't it matter one-way or the other? >>

Typically, it doesn't matter, but my preference would be for either just closing the TEDBEngine component or closing things in order.

Tim Young
Elevate Software
www.elevatesoft.com