[thelist] SQL - Foreign Key Constraint - in another database?

[spinhead]

Apologies; babbling incompletely again:

MS SQL 2000 - created a db for our Request for PO application. It included
employee info. Later, built a 'grand scheme' core db for other ongoing
purposes, which also included employee info. PO app needs to reference the
employee table in the new db now, but foreign keys from two tables point to
the original employee table.

I'm thinking my only solution is to remove said constraints, move the tables
to the new db, then create new constraints.

Is there an easier way?

spinhead


----- Original Message -----
From: "Joshua Olson" <joshua at alphashop.net>
To: <thelist at lists.evolt.org>
Sent: Friday, August 31, 2001 1:50 PM
Subject: Re: [thelist] SQL - Foreign Key Constraint - in another database?


> I've never heard of a database that supported that feature  :(  Perhaps
you
> can code something in the middleware to get it working again?
>
> -joshua
>
> ----- Original Message -----
> From: "spinhead" <evolt at spinhead.com>
> Subject: [thelist] SQL - Foreign Key Constraint - in another database?
>
>
> : I'm stretching here, 'cause I don't want to have to combine two very
> : different databases just to get this working again. Is it possible for a
> : field in one database to reference a field in another database?
> :
> : spinhead
>
>
> ---------------------------------------
> For unsubscribe and other options, including
> the Tip Harvester and archive of TheList go to:
> http://lists.evolt.org Workers of the Web, evolt !
>