Even if the servers don't support replication you could take data from the one
database and populate a table on the other by creating your own replica. You could
then add a
foreign key constraint to this table or use a query to check the data. Just remember
that if it is being used as a foreign key, you can't drop the data and replace it, you
will
need to do update/inserts. This could give the app a way of validating the data
entered or even give them a parts lookup.
-----Original Message-----
From: Brett W. McCoy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 1:21 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: sql table joins
On Tue, 1 May 2001 [EMAIL PROTECTED] wrote:
> different databases on different servers
Yikes! That does introduce extra problems for you! Yeah, the only way
you can really handle that is via external scripting, unless your servers
support some kind of replication|mirroring|distributed querying or
something along those lines.
I guess your big problem is that you can't verify your data integrity
until after the data has already been entered. How big of a gap in time
does this occur, between data entry and data validation?
-- Brett
http://www.chapelperilous.net/btfwk/
------------------------------------------------------------------------
"Ninety percent of baseball is half mental."
-- Yogi Berra
