Hello

I would dearly like to have a project group in D2009 that contains all my EDB based utilities, but whenever I try to add a new engine to a project
within that group, or open a form from another group, and the second form contains an Engine component, I get that error message.

I can have a form open, with an engine on it, in D7, and the same in D2009, but not 2 D2009 projects, or 2 D7 projects, at the same time.

Is there a way around that issue?

Regards & TIA

Peter

Peter


Having been caught several times by it I can answer NO.

The only reason I have an engine component explicitly in an app is to set 1 property - UseLocalSessionEngineSettings - to True. If this was set to True by default rather than False there wouldn't be a problem.

I know Tim would be reluctant to change a default but maybe he could be persuaded.

Roy Lambert [Team Elevate]

Roy

Thanks, I guess if we create the components dynamically then the conflict cannot occur. Have you tried that?

Regards

Peter

Peter

>Thanks, I guess if we create the components dynamically then the conflict cannot occur. Have you tried that?

I believe that's correct but haven't tried it because then I wouldn't be able to set the session local information in the IDE and have it used for the database and down to the tables. So I wouldn't be able to open tables in the IDE.

At least that's my guess.

Roy Lambert [Team Elevate]

Roy,

<< I know Tim would be reluctant to change a default but maybe he could be
persuaded. >>

I can't figure out a way yet to have intra-component notification at
design-time to propogate property changes among the different TEDBEngine
components, or else I would do it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Peter,

<< Thanks, I guess if we create the components dynamically then the conflict
cannot occur. Have you tried that? >>

If using the components dynamically, then you can just refer to the global
Engine() function in the edbcomps unit in order to access the global
TEDBEngine component.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< I know Tim would be reluctant to change a default but maybe he could be
>persuaded. >>
>
>I can't figure out a way yet to have intra-component notification at
>design-time to propogate property changes among the different TEDBEngine
>components, or else I would do it.

I love it when you talk dirty

I suspect its because I use f/s rather than c/s that I don't understand some of the stuff in the engine and session.

Roy Lambert