Solved Access error after upgrading from Windows XP to Windows 7

May 16, 2016 at 04:28:49
Specs: Windows 7
I have a client that recently upgraded from Windows XP to Windows 7 64 bit workstations. They are running Office 2007 Pro with SP3.
After the upgrade their access database program started failing and giving the following error message:
"Microsoft Office Access has detected that this database is in an inconsistent state, and will attempt to recover the database.
I am not sure why this is happening. Any ideas?

See More: Access error after upgrading from Windows XP to Windows 7

Report •

✔ Best Answer
May 23, 2016 at 07:39:14
Otherwise, if everything is corrupted then you may help the utility Access Recovery Toolbox. This way, you will save if not all the information, then at least some part. Access Recovery Toolbox
Be sure that ALL machines are fully up to date regarding Office and Windows. Check the Windows Update history to be sure that you don't have bunch of failed updates.


#1
May 16, 2016 at 05:38:21
Dose a recent backup of the database in question work without error? If so, it sounds like they have a corrupted database.

How To Ask Questions The Smart Way


Report •

#2
May 17, 2016 at 06:06:51
Try the built in repair feature.
How to use the repair process in the 2007 Office programs
https://support.microsoft.com/en-us...

Report •

#3
May 23, 2016 at 07:05:17
Here is the full error message: Microsoft Office has detected that this database is in inconsistent state and this database will attempt to recover the database. During this process a backup copy of the database will be made and all recovered objects will be placed in a new database. Access will then open the new database. The names of the objects that were not successfully recovered will be logged in the ?Recovery Errors? table.
The database itself is on a network share (windows server 2012). It was working fine when we were running XP on the desktops. Nothing changed except for the workstations

Report •

Related Solutions

#4
May 23, 2016 at 07:07:22
already tried this:
Putting a database on a server is asking for trouble if it also has the forms,
queries, reports, modules and macros. These objects corrupt easily over a slow
network or when multiple users are in the database.

Best practice is to split the database using the Database splitter under the
database utilities on the menu. Be sure to do it on your local copy. Once the
database is split move the back end (the file with just the tables) to the
server and give each user a copy of the front end. best of all, if a user does
manage to corrupt his copy of the FE you just have to give him a new one and the
data remains safe.


Report •

#5
May 23, 2016 at 07:15:48
So, does the backup copy work, or not?

How To Ask Questions The Smart Way


Report •

#6
May 23, 2016 at 07:35:45
unfortunately not. ( (

Report •

#7
May 23, 2016 at 07:37:45
So you have split the database, and you now have the Data portion (i.e. the "Backend") on the server, and the UI portion (i.e. the "Frontend") installed directly on each user's workstation? They're not running the Frontend from a network share?
The error you're getting generally means corruption, so have you performed maintenance on the database?
If not, then first make a backup and then do these things:
1. Compact the database
2. Compile the database - from the VBA Editor click Debug-Compile. Fix any errors that are found, and then continue doing this until that menu item is disabled.
3. Compact the database
You may also need to Decompile it. To do that, create a shortcut with this as the Target:
"full path to msaccess.exe" "full path to your database" /decompile
Run this shortcut, then do the 3 steps above
You might also consider moving everything over to a new, blank database. This takes care of any container corruption.
Perhaps this topic is on the Microsoft something to help. https://social.msdn.microsoft.com/F...

Report •

#8
May 23, 2016 at 07:39:14
✔ Best Answer
Otherwise, if everything is corrupted then you may help the utility Access Recovery Toolbox. This way, you will save if not all the information, then at least some part. Access Recovery Toolbox
Be sure that ALL machines are fully up to date regarding Office and Windows. Check the Windows Update history to be sure that you don't have bunch of failed updates.

Report •

#9
May 27, 2016 at 06:16:19
Thank you guys for your feedback and help. Sorry, that long time did not respond. This is because the issue was solved and I forgot to tell.) Thank you!

Report •

Ask Question