UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Win10 Inconsistent State, Any Versions    
 
   
mari13598
post Feb 3 2019, 03:19 PM
Post#1



Posts: 11
Joined: 21-June 18



Hello,

Running an 2013 access db that lives on a network drive with up to 10 users. All users were running windows 7. This has been working well for the last couple of years until users were upgraded to windows 10.

Now we are getting the error message "Microsoft Access has detected that this database is in an inconsistent state, and will attempt to recover the database."

I am able to recover the database and have not lost any data. We may go a few days without the error and then may have a problem with it two or three times in one day. Have experienced this error after monthly patch updates were installed.

What are the options to eliminate this error?

I wanted to split the database but cannot put it on the local drive of my LT. It would have to stay on a network drive. Is that possible?

Thanks,

Marianne
Go to the top of the page
 
isladogs
post Feb 3 2019, 04:04 PM
Post#2



Posts: 1,061
Joined: 4-June 18
From: Somerset, UK


There is a Windows bug that affects Access for Office 365. Not sure about A2013. See https://www.devhut.net/2018/06/13/access-bu...ognized-format/

--------------------
Go to the top of the page
 
mari13598
post Feb 3 2019, 04:22 PM
Post#3



Posts: 11
Joined: 21-June 18



Will splitting the database help?
Go to the top of the page
 
isladogs
post Feb 3 2019, 04:39 PM
Post#4



Posts: 1,061
Joined: 4-June 18
From: Somerset, UK


YES!!!!!
You would never allow several people to drive your car at once as it would crash
Similarly NEVER allow users to share a database - it will at some point become irretrievably corrupted and unuseable
Indeed that may have already happened to some of your data.

You should split any production database with multiple users. Backend on a shared network drive
Each user MUST have their own copy of the frontend on their own hard drive - NOT on a NETWORK drive

This is an URGENT PRIORITY. Until that is in place, BACKUP several times each day just in case.

Also do NOT allow users to connect to the network wirelessly

--------------------
Go to the top of the page
 
mari13598
post Feb 3 2019, 06:06 PM
Post#5



Posts: 11
Joined: 21-June 18



Thanks! I appreciate all the help very much!
Go to the top of the page
 
isladogs
post Feb 3 2019, 06:51 PM
Post#6



Posts: 1,061
Joined: 4-June 18
From: Somerset, UK


You're welcome. Don't put off splitting the db and distributing local copies of the FE to all users

--------------------
Go to the top of the page
 
DanielPineault
post Feb 3 2019, 07:18 PM
Post#7


UtterAccess VIP
Posts: 6,404
Joined: 30-June 11



You may like to review, for general knowledge, the following articles:

http://www.devhut.net/2017/04/09/setting-u...ccess-database/

http://www.devhut.net/2017/04/20/access-be...shooting-steps/



--------------------
Daniel Pineault (2010-2018 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...(you are responsible for your choices and actions)
Go to the top of the page
 


Custom Search


RSSSearch   Top   Lo-Fi    22nd February 2019 - 10:04 AM