To Link or Not to Link

  • Thread starter Thread starter Scuda
  • Start date Start date
S

Scuda

Hello all. Quick Question. My db has many functions/features. Is it better to
link to more than one BE db, or keep them all in one?

Thanks!

Steph
 
Objects that might typically be described as functions/features, like
forms, reports, code, etc. don't exist in the BE. The BE contains only
the tables and relationships. Is your FE approaching the Access size
limit? If not, what is the reason you are considering this?
 
thanks for responding. What I meant was having my FE, which I do, but having
linked tables go to 2 different BE mdb's.

Is there any reason to do that, or should I just keep them all in one BE mdb?

Thanks again.
 
Unless you have a large BE that is going to exceed the Access
size limit of 2GB, I don't see a reason to use multiple back ends.

That is not to say that there couldn't possibly be another reason,
but if you have another reason why you think you should, you
haven't said.
 
Scuda said:
Hello all. Quick Question. My db has many functions/features. Is it better
to
link to more than one BE db, or keep them all in one?

Thanks!

Steph
Click to expand...
 
Thanks so much thats all I needed!



Beetle said:
Unless you have a large BE that is going to exceed the Access
size limit of 2GB, I don't see a reason to use multiple back ends.

That is not to say that there couldn't possibly be another reason,
but if you have another reason why you think you should, you
haven't said.
Click to expand...
 
I have several databases that use the Employee table. Unless I plan to
incorporate each new database into the existing database that includes the
Employee table I have little choice but to link to a different BE for the
Employee information. However, if you need to break the BE into two
database files because of size considerations alone it may be that your
design needs a closer examination.
 
Back
Top