SOLVED
Home

Access reports that databases are in an 'inconsistent state'

%3CLINGO-SUB%20id%3D%22lingo-sub-664714%22%20slang%3D%22en-US%22%3EAccess%20reports%20that%20databases%20are%20in%20an%20'inconsistent%20state'%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-664714%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20some%20help%20with%20this%20Issue.%20Background%3A%20we%20moved%20from%20an%20office%202010%20.adp%20project%20to%20a%20access%202016%20database%20project%20the%20access%20database%20project%20has%20custom%20vba%2FDAO%20and%20linked%20tables%20to%20a%20backend%20sql%20server%202012.%20We%20host%20the%20access%20project%20on%20a%20network%20share%20which%20was%20never%20an%20issue%20in%20the%20past%2C%20but%20now%20we%20have%20noticed%20that%20the%20file%20size%20of%20the%20access%20project%20will%20grow%20and%20then%20users%20will%20start%20receiving%20the%20%22inconsistent%20state%22%20message%3F%20at%20the%20link%20below%20there%20is%20a%20report%20that%20this%20is%20a%20known%20issue.%20I%20am%20not%20able%20to%20update%20the%20leasing%20on%20the%20server%20as%20noted%20in%20the%20work%20around%20area%20of%20the%20article.%20Does%20anyone%20have%20any%20suggestions%20or%20advice%20on%20how%20to%20fix%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Faccess-reports-that-databases-are-in-an-inconsistent-state-%25EF%25BB%25BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Faccess-reports-that-databases-are-in-an-inconsistent-state-%25EF%25BB%25BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-664714%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-691419%22%20slang%3D%22en-US%22%3ERE%3A%20Access%20reports%20that%20databases%20are%20in%20an%20'inconsistent%20state'%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-691419%22%20slang%3D%22en-US%22%3EHI%20I.M%20COCO%20HOW%20IS%20IT%20GOING%20GOOD%20I%20HOPE%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-699767%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20reports%20that%20databases%20are%20in%20an%20'inconsistent%20state'%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699767%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353669%22%20target%3D%22_blank%22%3E%40programmer1235245aBE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMake%20sure%20each%20user%20of%20the%20application%20is%20storing%20the%20Access%20frontend%20on%20their%20local%20PC%20and%20not%20sharing%20it%20with%20anyone%20else%20on%20the%20network.%20One%20advantage%20to%20this%20approach%20is%20when%20a%20user%20goes%20down%20no%20one%20else%20does.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20drawback%20is%20having%20to%20rollout%20new%20versions%20of%20your%20frontend%20to%20everyone%2C%20but%20if%20you%20search%20the%20web%20you%20will%20find%20solutions%20to%20this%20issue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20that%20helps!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-706212%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20reports%20that%20databases%20are%20in%20an%20'inconsistent%20state'%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-706212%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F10231%22%20target%3D%22_blank%22%3E%40Juan%20Soto%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethank%20you%20Juan%2C%20I%20was%20able%20to%20figure%20out%20a%20work%20around.%20We%20marked%20the%20access%20database%20file%20as%20readOnly%20and%20the%20issue%2Ferror%20went%20away%20and%20the%20database%20quit%20growing.%20I%20would%20rather%20have%20users%20have%20a%20shortcut%20on%20their%20desktops%20then%20a%20copy%20of%20the%20file.%20thanks%20for%20your%20response.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
programmer1235245aBE
New Contributor

Hi Everyone,

 

I need some help with this Issue. Background: we moved from an office 2010 .adp project to a access 2016 database project the access database project has custom vba/DAO and linked tables to a backend sql server 2012. We host the access project on a network share which was never an issue in the past, but now we have noticed that the file size of the access project will grow and then users will start receiving the "inconsistent state" message? at the link below there is a report that this is a known issue. I am not able to update the leasing on the server as noted in the work around area of the article. Does anyone have any suggestions or advice on how to fix this issue?

 

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-...

 

3 Replies
HI I.M COCO HOW IS IT GOING GOOD I HOPE

@programmer1235245aBE 

 

Make sure each user of the application is storing the Access frontend on their local PC and not sharing it with anyone else on the network. One advantage to this approach is when a user goes down no one else does.

 

One drawback is having to rollout new versions of your frontend to everyone, but if you search the web you will find solutions to this issue.

 

Hope that helps!

Solution

@Juan Soto

 

thank you Juan, I was able to figure out a work around. We marked the access database file as readOnly and the issue/error went away and the database quit growing. I would rather have users have a shortcut on their desktops then a copy of the file. thanks for your response. 

Related Conversations