Database Design Question

[JamesJ]

For years I've had my db basically the same but now I have some reservations
about the design because of problems that have been occurring with the db
since installing Vista.
I access several tables from my db - Auto Maintenance,
Contacts, Movies, Home Inventory and Reminders.
Seems all templates I find on the Office web site deal with only one type
of data - contacts etc.
Question is should I split this into a couple databases instead of
keeping all in the same database? Is this bad db design?
Not sure if it has anything to do with the problems.

Thanks,
James

 

[Guest]

Hi James,

Question is should I split this into a couple databases instead of
keeping all in the same database?

That should not be necessary. While a database is usually topic oriented, I
suppose you could say that all of the issues you listed (Auto Maintenance,
Contacts, Movies, Home Inventory and Reminders) are topics of interest to
you.

Is this bad db design?

Not necessarily.

What type of problems are you experiencing now that you have upgraded to
Vista? I really doubt that splitting up your database would solve these
problems, whatever they are. You might want to have a look at Access MVP
Allen Browne's web site:

http://allenbrowne.com/tips.html

For instance, there is a nasty problem waiting if you share a database
between two Vista machines in a peer-to-peer network. Splitting your one
database into more than one would not help with this problem.

Allen has lots of good information on his web site. There is a Search button
in the menu on the right-hand side. Here is some information I found by
entering Vista as a search term:

http://allenbrowne.com/bug-17.html


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[JamesJ]

Been to Allen Browne's many rimes and has helped me through
much.

This was just a thought.
Problem(s) concerning my db I post normally in .forms or .formscoding.

Thanks much for the info,
James