Two databases or one

A

AccessKay

Hi,

What if you have two organizations and you plan to design a database to do
the same task but within that task, the defined tables will vary because of
unique qualities related to the individual organization. Would it be best to
create separate databases for each organization or keep the two organizations
together?

Anyone know the guidelines related to this?

Thanks for any feedback.
 
J

Jeff Boyce

Also ask yourself whether the two organizations ever "share" information
(e.g., both use the same/a common "customer" list...)

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
A

AccessKay

Thanks. This answers my question also.

Jeff Boyce said:
Also ask yourself whether the two organizations ever "share" information
(e.g., both use the same/a common "customer" list...)

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.





.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top