Hi David,
I am not splitting them up. They are already in two
different databases.

At the moment the 'new' database links to two tables in
a database created several years ago. The 'old' database
isn't split but it has been in the back of my mind on
and off that I should split it.

Earlier today I was thinking about splitting both
databases and combining the back ends. I came back here
to ask Allen if he foresaw any problems with doing that.
The 'old' database isn't large. The principal table has
almost 1,000 records. The 'new' is really an unknown
quantity but I expect it to outgrow the old in 12-18 months.

--
Len
__________________________________________________ ____
remove nothing for valid email address.
"David W. Fenton" wrote in message
36.91...
| ".Len B" wrote in
| :
|
| What happens when I split and the tables are in different
| back ends? Am I in trouble?
|
| Why would you do that? If the tables are sufficiently related that
| it is necessary to enforce RI, then they belong in the same back-end
| file. If you are splitting them up because your dataset is getting
| too big, then you've outgrown Jet/ACE as a data store and should
| instead use a more suitable back end, i.e., one that can handle more
| than 2GBs of data.
|
| --
| David W. Fenton http://www.dfenton.com/
| usenet at dfenton dot com http://www.dfenton.com/DFA/