Too Many Objects in Database?

[Bill6868]

Too Many Objects in Database?

I have a database I’ve been using for about 10 years, and over the years it has gone through a lot of evolving developments. I have quite a collection of objects – macros, forms, reports and queries. My concern is with the number of these objects. Can you reach a point where having too many objects is detrimental to the health of the database?

It has reached 91 MB but everything works just fine and it is not bogged down at all. It even contains over a thousand photos.

Seeking advice/comments on the numerous number of objects. Will I push it over the limit at some point? I’m using Access 2007.

Thank you for your comments.

Bill

 

[dhookom]

I would just make sure the database is backed up and compacted regularly.

Duane
Hook'D on Access
MS Access MVP

 

[lameid]

My experience says you should also split the database. Corruption always seems to happen most frequently to the file that has the application objects. If you lose your frontend and haven't made changes to the design in a month and you have a week old backup, you are good... Now if you made a bunch of changes yesterday that you don't want to lose and things go south, your data is at risk.

The only drawback is that split files run locally vs. combined are slightly slower. On a network faster, because the network speed is the bottleneck and the frontend is put local.

Access 2007 limits...

http://office.microsoft.com/en-us/access-help/access-2007-specifications-HA010030739.aspx