Today’s guest blogger is Michael Groh, co-author of the popular Access 2007 Bible. I think it's safe to say that anyone who's worked with really large Access databases (like,
Office 2007 Product Key, in excess of 50 or 100 megabytes) has encountered slow compact and repair cycles. My favorite anecdote in this regard is a very large database managed by an old buddy of mine. His database has several large tables containing more than 20 million rows each. When it's time to compact and repair, he starts it up on Friday before leaving work, and the operation is usually complete by Monday morning. Not to worry! What Steve really needs to do is break up his humongous ACCDB file into multiple ACCDBs, each containing just one of his big tables, then link the individual database files to a central database. The central database, of course,
Office 2007 Pro, would contain the forms, reports, queries,
Microsoft Office 2007 Ultimate Serial, and other database. He'll find that compacting the constituent databases (as sequential operations) goes much faster than compacting the one big database. Also, one advantage of breaking big databases up into smaller pieces is that, in the event of database corruption,
Microsoft Office Standard 2007 Serial Key, the corruption will affect only one portion of the total database. Presumably,
Microsoft Office Professional Plus 2007 produit cl��, the database system is easily restored by replacing the corrupted database from a backup. Have an Access Power Tip that you want to share? Send it to Mike and Chris at accpower@microsoft.com. <div