At 11:31 PM 5/09/2004 -0400, you wrote:

>Has anyone used the IBO replication component? I looked at it a while back
>when I first got IBO, but didn't purchase it (don't think I really needed it
>at the time, but it looked kinda cool).
>
>I want to give my customers more redudancy and a lesser down time in case a
>FB server goes down. Our typical setting is probably about 3-4 workstations
>(some as large as 15, 20, even 35) and a local server computer that runs FB
>Database and credit card processing software service as well.
>
>I thought it would be nice if I could replicate the main database to one or
>more work stations in the background so that if the connection becomes lost
>(server down), we can show the users a list of available servers to connect
>to until main server becomes available. At that point, I would want to
>replicate the latest changes in the temp db to the main db when it comes
>online.
>
>Feasible with the IBO replication?

IBO replication is one-way, so, out-of-the-box, it's no good for a
briefcase-style replication system.But your scenario would make it feasible
(apart from the bit about replicating back to the dead database...that
doesn't seem to make sense...).

>Any hints, gotchas, etc?

You can look at the IB_RPL project that's in the root dir of your
installation. It's documented on-line - click through to the Modules page
for the replicator components and look for the On-line Help link. (WinHelp
version comes with the package).

Helen