This is not exactly a conversion question, but it does involve moving
data from one SQL platform to another, so this seemed like the best
place to post my question.

I'm involved in upgrading our company's database. The new version will
need to talk to a remote MS-SQL-based system. We will have the "real"
database, and the other company will maintain a mirror of the data on
their MS-SQL servers. We need to be able to update data in both
directions. We will have in-house people entering data into our
database through an in-house front-end, and remote users will be able
to enter data into the MS-SQL system via the web. Our system will
accept the remote data, merge it with our internal data, and generate
reports, etc.

So basically, we need to be able to query and update the remote
database, which also needs to be able to query and update our database.

The other company is already committed to MS-SQL. They will be doing
most of the development of our in-house database as well. Their
developer wants us to use MS-SQL for our new database, because he says
it is not possible for MS-SQL and Interbase to communicate this way.
Is he correct?

How feasible is this? It needs to be practical enough to justify the
use of IB to the MS-SQL developer. I'd like to hear from anyone who
has done something similar to this. I can provide more details if
needed. Advice greatly appreciated...

Bill Mercer
bmerc@...
352-334-0911