Prev: Set up db to lookup and concatenate large amounts of text
Next: Food Pantry Database
From: .Len B on 18 Dec 2009 09:05
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" <XXXusenet(a)dfenton.com.invalid> wrote in message
news:Xns9CE4C5787BB52f99a49ed1d0c49c5bbb2(a)74.209.136.91...
| ".Len B" <gonehome(a)internode0.on0.net> wrote in
| news:#Yy00SvfKHA.6096(a)TK2MSFTNGP02.phx.gbl:
|
| > 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/



From: David W. Fenton on 18 Dec 2009 17:49
".Len B" <gonehome(a)internode0.on0.net> wrote in
news:edf5xs#fKHA.1648(a)TK2MSFTNGP05.phx.gbl:

> 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.

If the tables have data that is related to each other, they belong
in the same back end. I don't think that's an issue on which there
can be any dispute.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
First  |  Prev  | 
Pages: 1 2
Prev: Set up db to lookup and concatenate large amounts of text
Next: Food Pantry Database