Compact & Repair MDB problem with multi-core CPU

My environment: business use, connected to a domain.  PC = Win7-Pro SP1 64bit, i5-3570 CPU, 8GB RAM, Office2010 Pro V14.0.6125.5000 (32bit) installed.

 

Are there any updates or hotfixes to fix an Access2010 Compact & Repair problem with multi-core CPU’s?

 

Problem: when I run a Compact & Repair on an existing MDB database, eight tables are completely deleted (with no error messages).  If I set the MSAccess.exe affinity to a single CPU and run the Compact & Repair on a copy of the original MDB file, everything is fine.  Original MDB files size = 1.21GB.

 

Added 1/25/2013:  I found a comment on another MS forum that discusses the CPU affinity fixing an Access 2010 problem.  That's where I got the clue to give it a try.

http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/b188f2fe-8f5d-4a7b-b5f8-bc4c26854164

 

Thanks for any suggestions,
BWilliamsSFR

 

Question Info


Last updated April 29, 2019 Views 768 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Not sure how you managed to get your MDB to 1.21 Gb, given there's a 1 Gb size limit. I think that may be the issue here, not that you're using a multi-core CPU. I don't believe Access is multi-threaded, so it only uses a single processor.
Doug Steele, Microsoft Access MVP
www.AccessMVP.com/djsteele

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sadly I do not have a solution for you, but I can tell you that I run Access on a multi-core PC and have never experience such an issue.

 

Are your installations up-to-date (OS, MS Office/Access)?

What about your PC's BIOS?

 

It is interesting however that changing the affinity would stop the issue?!

 

Have you tried creating a new blank db, importing all your database objects and trying again just to see?

--
Daniel Pineault
Microsoft MVP 2010-2019

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I agree with DJSteele and Daniel.  I have not seen the problem on multi-cpu boxes and Access only uses 1 processor.

 

You problem more likely is from the files size.  It is time to move to at least SQL Server Express.  Though there are many things you can do to make Access and SQL work better, you can often get away with NO changes at all to your coding with your data moved to SQL and the using Linked tables.

Jack Stockton
Microsoft Access MVP 2012 - 2017

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

If I remember correctly, since Access 2003 there is a 2GB MDB file size limit.  I have compacted & repaired larger Access databases on WinXP without any problems.

 

As I stated, if i set the affinity to a single CPU the compact & repair works perfectly.

 

Thanks,

BwilliamsSFR

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Everything is up to date, it's a new PC.  I have not tried importing into a blank DB and then trying the compact & repair.  Good suggestion, I will try it this afternoon.

 

Thanks,

BWilliamsSFR

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

The problem is repeatable.  I have compressed & repaired larger Access database successfully on my XP box in the past.  If I compress & repair the exact same file on WinXP, no problem (same version of Access).

 

I agree it's time to move to SQL.  It's in the works, but for now I have to deal with the existing MDB backend database.

 

Thanks,

BwilliamsSFR

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

New PC  does not equate to up-to-date!  My new PC was 13 version behind for the BIOS!  Little alone OS and Office.  You should verify this carefully.
--
Daniel Pineault
Microsoft MVP 2010-2019

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Not sure how you managed to get your MDB to 1.21 Gb, given there's a 1 Gb size limit. I think that may be the issue here, not that you're using a multi-core CPU. I don't believe Access is multi-threaded, so it only uses a single processor.
Doug - it's 2 gigs upper limit. It's been that way since at least Acc2002.

Bill Mosca
ThatllDoIT.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

With a file that big, I hope you are compacting locally. It might be a network connection hiccup.

Bill Mosca
ThatllDoIT.com

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Good point.  Everything is up-to-date.

 

Thanks,

BWilliamsSFR

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.