A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Two databases or one



 
 
Thread Tools Display Modes
  #1  
Old April 5th, 2010, 04:08 PM posted to microsoft.public.access.tablesdbdesign
AccessKay
external usenet poster
 
Posts: 106
Default Two databases or one

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.

  #2  
Old April 5th, 2010, 04:15 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default Two databases or one

Ask yourself this - How often will you need the combined data?


--
Build a little, test a little.


"AccessKay" wrote:

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.

  #3  
Old April 5th, 2010, 04:55 PM posted to microsoft.public.access.tablesdbdesign
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default Two databases or one

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.


"AccessKay" wrote in message
...
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.



  #4  
Old April 5th, 2010, 06:52 PM posted to microsoft.public.access.tablesdbdesign
AccessKay
external usenet poster
 
Posts: 106
Default Two databases or one

Thank you. This answers my question.

"KARL DEWEY" wrote:

Ask yourself this - How often will you need the combined data?


--
Build a little, test a little.


"AccessKay" wrote:

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.

  #5  
Old April 5th, 2010, 06:53 PM posted to microsoft.public.access.tablesdbdesign
AccessKay
external usenet poster
 
Posts: 106
Default Two databases or one

Thanks. This answers my question also.

"Jeff Boyce" wrote:

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.


"AccessKay" wrote in message
...
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.



.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:38 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.