>Hej Sven
>
>Thanks for your kind answer.
>
>As my app is using BDE and Paradox, I don't see any other way to get to using the Firebird database other than switch BDE and Paradox to IBO >and Firebird in one go.
>
>Is there another way?

I'd say that, conceptually, it is a three step conversion process. First BDE/Paradox to BDE/Firebird, then BDE/Firebird to IBO/Firebird and lastly IBO/Firebird to IB_/Firebird. You chose to do this in two steps, skipping the BDE/Firebird step and haven't yet reached IB_/Firebird.

Mentally, you also have to (unless you've already done so) go through a conversion at some point, from thinking in terms of tables to thinking in terms of datasets and start displaying only a few relevant rows/fields rather than millions of mostly irrelevant rows.

>I have worked intermittently on this for a year, and I'm now at a point, where it is up and running, Infopower grids are functioning, >QuickReport reports are ok, etc. I think this problem with transactions is my last hurdle in this phase.

Yup, for most reporting tools, you need to keep the IBO/Firebird components, there exists some tools that can use IB_ components, I don't know whether Infopower or QuickReport is amongst them.

>I have dual version code with {$IFDEF BDE} and {$IFDEF FIREBIRD} conditional defines, a GReplace script and a datapump in place, so I can
>keep the app in the air on the BDE while working on the migration.

Sometimes it is more practical to do changes in small steps, rather than a major rewrite, sometimes it is the other way around. The path you've chosen may be very sensible.

>You are right, at this point the IBO/Firebird version is slower than the BDE/Paradox version.
>
>When my app is running correctly using BDO/Firebird, my next step will be to look for ways to utilize the IBObjects and Firebird more fully.

Good to hear that you haven't been turned off by the perceived slowness!

Set