Hi,

I'm running into a bit of a problem. With my application, if during
designtime I forget to go to the main form, and close the TEDBEngine
component, and distribute the application - my clients are unable to use
the application as it errors out because the application attempts to
connect to a database on a non-existent path (a path used by my
development machine), instead of first loading the parameters from their
local .ini or registry entry.

I've tried to combat this by putting in an "If not initialised then
EDBEngine1.close" event in the EDBEngine1BeforeStart event, but this
hasn't worked for me.

I have also tried EDBEngine1.Close on the OnCreateEvent of the form, but
this also has failed to fix the issue.

Obviously if I remember to deactivate the engine before building it
works OK - but this is unfortunately happening quite a bit, and causing
some problems with some clients.

I was just wondering - can anyone recommend any method to closing the
engine off during runtime so this doesn't occur if I do forget to close
it during design time?

Thanks & Regards

Adam.

Adam


Depending on the version of Delphi you're using (if you are using Delphi) you can install GExperts which has a nifty utility which allows you to set things like this. I have it set to set Active to false for all table, query, database, session and engine components.

The only problem is for quick tests I have to remember to activate things in the forms OnCreate event or sit staring at the screen thinking "why isn't the grid populated"

Roy Lambert

I wrote a little utility to clear the property in the .dfm, and then have that
called by my FinalBuilder script. This ensures that I can never do that by accident
(as well as a load of other possible things I might forget).

/Matthew Jones/

Adam,

<< I'm running into a bit of a problem. With my application, if during
designtime I forget to go to the main form, and close the TEDBEngine
component, and distribute the application - my clients are unable to use the
application as it errors out because the application attempts to connect to
a database on a non-existent path (a path used by my development machine),
instead of first loading the parameters from their local .ini or registry
entry. >>

Courtesy of my time machine:

http://www.elevatesoft.com/manual?action=viewprop&id=edb2&product=delphi&version=7&comp=TEDBEngine&prop=StoreActive



Tim Young
Elevate Software
www.elevatesoft.com

Thanks All for your replies...

Looks like Tim's got the easiest answer for me though. (Thanks Tim!)

Sorry I missed this in the Manual. (To tell you the truth Tim, I didn't
actually expect this to be part of the component - as simple as setting
StoreActive to false... brilliant!)

Cheers

Adam.

> Courtesy of my time machine:
>
> http://www.elevatesoft.com/manual?action=viewprop&id=edb2&product=delphi&version=7&comp=TEDBEngine&prop=StoreActive
>
>
>
>
> Tim Young
> Elevate Software
> www.elevatesoft.com