One big database or several smal?

  • Thread starter Thread starter Katrin
  • Start date Start date
K

Katrin

I have a split db. front and back(tables). My problem is to decide; Have one
back database for each customer and reelink to the db each time wee log on,
or a big one with every custom tables inside.
Its easyer to not have to reelink every time, but it feels safer to have a
db for each customer so the data cant mix.
Hope someone can help mee with this. --
KT
 
Katrin

Access is a relational database, not a spreadsheet. While you might need to
use a separate spreadsheet for each customer, this is not the recommended
approach to organizing your data when using Access.

If "relational" and "normalization" are not familiar terms, plan to spend
some time coming up to speed on them before trying to make Access work for
you. You'll want to build tables in Access that reflect a "well-normalized"
model of your situation.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
There are only a very, very few scenariors whereby a single database used in
industry *doesn't* contain records from multiple customers. Its not about
whether or not the records are co-located in the same tables/database. Its
all about how the primary and foreign keys unique identify to whom the
records belong.
 
Back
Top