Hi everyone

I am in a challenge of migrating my applications from DBISAM to ElevateDB.

I have a inherited (from DBISAM) set of components called HProTable and HProQuery. I am planning to use a compiler directive {$ifdef ELEVATE} to separate specific features like Exists, CreateTable, Recno, etc.

Question:
These components are in a package and there are a define to compile using Elevate or DBISAM.

When I switch Elevate to DBISAM development or vice-versa I have to recompile the package.
Is there an easy way to handle this situation ?

Jose Eduardo Helminsky wrote:

> When I switch Elevate to DBISAM development or vice-versa I have to recompile the package.
> Is there an easy way to handle this situation ?

Ouch!

Not easy I'd have thought. It might be possible to have different Register() lines according to the conditional compile, but you'd have to have different package names too. Ick.

Might be easier to have two virtual machines, one with DBISAM and one with EDB installed, and then switch between them instead. Good luck!

--

Matthew Jones

Eduardo,

<< I have a inherited (from DBISAM) set of components called HProTable and HProQuery. I am planning to use a compiler directive {$ifdef ELEVATE} to separate specific features like Exists, CreateTable, Recno, etc.

Question:
These components are in a package and there are a define to compile using Elevate or DBISAM.

When I switch Elevate to DBISAM development or vice-versa I have to recompile the package.
Is there an easy way to handle this situation ? >>

I would create two sets of design-time/run-time packages, one for DBISAM and one for EDB, each with their own compiler directives set in the packages.  Then, install them each, one-at-a-time, in the Delphi IDE, making sure to unload the other before trying to install/load the next.  This can be done very easily in Delphi via the Component/Install Packages/Design Packages list - just check or un-check the one that you want to be loaded at any given time.

Of course, it would also pay to set up a batch file, or something similar, that will build these two sets of packages in a nice, neat fashion so that you don't have to do it by hand constantly.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks you Matthew and Tim.

I realise,at least for me, the Tim suggestion will be the best.