Hi,

just tried to install EDB in D2007. When Delphi starts, I get the following error message :

(translated) Package "edb109r2007design.bpl" could not be loaded. It contains the unit
"edbversion", which is also part of the package "edb109r2007run".

Any Ideas ?

TIA,

Heiko

Problem solved, I needed to remove a 3rd party component...

Heiko


Which 3rd party component?

Roy Lambert

Contextsoft EDB Extensions...but it seems I compiled them with an older version of EDB a
while ago. After removing I was able to recompile them, and now both EDB and the
Extensions work fine.

No big deal, just stupid me...

Heiko


I know that one. I have a few homebrew components that rely on commercial components. Upgrade time should be deducted from my time in purgatory  

Roy Lambert

Related Question :
I have several components that rely on DBISAM, and in D6 upgrading was a matter of text
search & replace in my components folder. No big deal.
D2007 seems to be a bit more bitchy there...and I dislike the idea of manually upgrading
10+ components in the future when I migrate everything to EDB/D2007.

Just a thought : If I derive every EDB Component and create a package that doesn't change
the filename with every build...use the derived components instead of the original ones in
my other components...won't upgrading then be a matter of just upgrading my derived
components ? Anyone tried this yet ?

TIA,

Heiko

Heiko,

<< Just a thought : If I derive every EDB Component and create a package
that doesn't change the filename with every build...use the derived
components instead of the original ones in my other components...won't
upgrading then be a matter of just upgrading my derived components ? Anyone
tried this yet ? >>

I'm not quite sure what you're trying to do here.  Are you saying that
you're going to replace your TDBISAM* components now with your own set of
wrapper components, and then change the internal references to the TDBISAM*
components over to the TEDB* components when you switch to EDB ?
Personally, this sounds like more work than just switching the TDBISAM*
components to TEDB* components and being done with it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>>and then change the internal references to the TDBISAM*
>>components over to the TEDB* components when you switch to EDB ?

Ah...no I try again.

This is not about migrating from DBISAM to EDB, but to speed up upgrading to new builds of
DBISAM/EDB with D2007.

I'm used that new builds in D6 were easy and fast to install, just run the DBISAM/EDB
installer (didn't even need to uninstall before), search&replaced the package name in the
3rd-Party and homebrewed component source files, started D6, and everything worked. With
D2007 it seems I have to manually remove every component that relies on DBISAM/EDB,
recompile it and then add it again to work without trouble. Maybe there's an easier way,
but that's the only failsafe way I discovered until now.

I just wondered if it would work to create a DBISAM/EDB wrapper package, use this package
in my 3rd-Party and homebrewed components, and when a new DBISAM/EDB build arrives, just
open, edit and recompile only one, the wrapper package, instead of many.

Sorry, should have started a new thread...

Tim


What he's trying to achieve is an end to component upgrade hell. The sort of thing where you alter from 109 to 200 and us poor suckers have to go through and alter all our references. Also as he says D2006 onwards seems less forgiving than previous Delphi's.

At least that's my interpretation.

Roy Lambert

Roy,

<< What he's trying to achieve is an end to component upgrade hell. The sort
of thing where you alter from 109 to 200 and us poor suckers have to go
through and alter all our references. Also as he says D2006 onwards seems
less forgiving than previous Delphi's. >>

Ahh, yes, now I understand.  I've looked into the version number issue
before, and although it seems simple from the outside, it is a significant
change to our internal systems.

--
Tim Young
Elevate Software
www.elevatesoft.com