Split Database Design

wricoasolutions

Registered User.
Local time
Today, 07:56
Joined
Aug 24, 2005
Messages
18
I am combining 12 Databases. I have split all 12 between the server and the desktop. My question is “Should I combing all of the data table on the server into one database or should I leave all of the individual application data tables in separate Databases on the server”. Additionally, is there a limit to the number of tables an Access DB can handle? My inclination is to keep the functionality separated but the problem I have is that some of the functionality within the applications overlap. Recommendations!
 
Thanks Pat, will be sure to check all overlaps and am most interested in ensuring that referential integrity is intact through out the design.

Again, Thanks.

Bill
 
Last edited:

Users who are viewing this thread

Back
Top Bottom