Alan McDonald wrote

> you might need to clarify what you mean (expect) by embedded application..
> some people think that it can all be wrapped into one exe. you need to
> install the server as a separate service on a "server" - it's not
> a desktop
> application unless you install a server on each machine with your
> application (not intended)

Kevin,

I can't help on your migration tool question, but i would like to vouch for
the embedded approach. I often see comments in this group that FB is not
suited to paradox replacement as an embedded backend. I selected to go this
way once it looked like IB was about to go open source (I couldn't face
adding $100 on to our app which was being sent out to many of our existing
customers free of charge).

Rational:
I went this route because many people said IB was zero admin, no dba etc. I
had heard lots about paradox index corruption. I also wanted to deploy
mainly to individual desktops but in a few cases use departmental servers. I
use a wise script which installs my app and the IB6 embedded server at the
same time.

Problems encountered:
Out of over 500 installs, i have twice met situations (both in germany)
where IB5.6 was already on the desktop embedded behind another app.
I have had 4 instances where the database had become corrupted due to a
short period when i distributed the gdb with forced writes off and the pc
crashed at a bad moment. these were all fixed using gfix type functions
through the IB6 service api.

I would have migrated to FB but i am waiting for the day when the registry
keys and client dll become fully seperated to as to minimise problems with
users who are using IB for other apps apart from mine.

good luck

Kind regards,
Pete