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
__________________________________________
> 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
[quoted text clipped - 9 lines]
> Thanks,
> James
JamesJ - 20 May 2007 10:58 GMT
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
> Hi James,
>
[quoted text clipped - 49 lines]
>> Thanks,
>> James