Derek Brown
asked on
Version Conflicts?
This is the same problem as posted earlier. The suggested Microsoft "Database is in an inconsistent state" fix has not solved this problem.
I have a client that uses my Access 2002 applications using 2002 runtime 5 users split database. They, independently, decided to create another stand alone Access 16 database linking to the same back end data (on server) All worked for years now they are having Disc or network error messages, crashes and error text in form text and number fields.
We are currently migrating all our DBs to Access 16. In the mean time the questions:
1. Is the linking of another version of Access to the BE likely to cause this issue
2. Will updating our application to the same version have any effect.
3. Is it more likely to be a data corruption problem. I noticed when compacting and repairing the BE Data that it took a very long time over 3 minutes. (using their native Access 16) File size 369,000 kb
I have a client that uses my Access 2002 applications using 2002 runtime 5 users split database. They, independently, decided to create another stand alone Access 16 database linking to the same back end data (on server) All worked for years now they are having Disc or network error messages, crashes and error text in form text and number fields.
We are currently migrating all our DBs to Access 16. In the mean time the questions:
1. Is the linking of another version of Access to the BE likely to cause this issue
2. Will updating our application to the same version have any effect.
3. Is it more likely to be a data corruption problem. I noticed when compacting and repairing the BE Data that it took a very long time over 3 minutes. (using their native Access 16) File size 369,000 kb
This could be a disk issue (i.e. the disk may be failing). Can you run CHKDISK to confirm if the disk is stable?
also, if you are running compact and repair on the BE are you:
1. making sure that no one else is using the BE
2. copying it to your local PC to perform the C&R, if not, I would recommend this
Have you confirmed that the person running Access 16 is connected to the DB via a hard connection, not WiFi? NEVER use Access over WiFi.
1. making sure that no one else is using the BE
2. copying it to your local PC to perform the C&R, if not, I would recommend this
Have you confirmed that the person running Access 16 is connected to the DB via a hard connection, not WiFi? NEVER use Access over WiFi.
ASKER
Jim The file is an .mdb only containing data tables. When I posted the question we had not seen the "Inconsistent state" issue because we never usually have need to open the backend data and wrongly assumed that the error message would appear in the front end. It does not. However it did appear when I opened the BE data with Accesss 16. It did not appear when opened with Access2002. So having seen it I closed it transferred it to my PC opened with 2002 compacted and repaired 3 times then transferred the data to another PC that has Access 16 and Windows 10 It opened without issue and compacted with Access 16 in 30 seconds. Just to be absolutely sure I then created a blank DB and imported all tables, 64 of them, In previous attempts to create a new DB only 33 of the 64 tables imported. So whatever has changed is quite dramatic. I now plan to do the same with the client’s up to date data and I will report back when we have a result.
We have applied the Microsoft Fix:
REG ADD HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Se rvices\lan manserver\ parameters /v DisableLeasing /t REG_DWORD /d 1 /f
What I never considered was that the above Microsoft fix will not fix the Inconsistent data problem. Obviously it’s designed to stop it happening in the first place, not repair it.
Dale I had assumed and I'm pretty sure all users are hard wired in. But I will make sure
Nakul. I think IT will have done that but again I will double check.
We have applied the Microsoft Fix:
REG ADD HKEY_LOCAL_MACHINE\SYSTEM\
What I never considered was that the above Microsoft fix will not fix the Inconsistent data problem. Obviously it’s designed to stop it happening in the first place, not repair it.
Dale I had assumed and I'm pretty sure all users are hard wired in. But I will make sure
Nakul. I think IT will have done that but again I will double check.
Just as an FYI, a compact and repair is not always successful. It may finish, but that does not mean the DB is good.
<<Obviously it’s designed to stop it happening in the first place, not repair it.>>
Yes, once a DB is corrupt, it's been corrupted and might be repaired, or it might not.
I would go to a known backup at this point.
Jim.
<<Obviously it’s designed to stop it happening in the first place, not repair it.>>
Yes, once a DB is corrupt, it's been corrupted and might be repaired, or it might not.
I would go to a known backup at this point.
Jim.
<<We have applied the Microsoft Fix:>>
You did this on the machine where the BE is hosted yes?
Jim.
You did this on the machine where the BE is hosted yes?
Jim.
ASKER
Hi Jim
Yes the fix was applied to Clients server and PCs.
Is there any way to check if there is corruption after a compact/repair?
Yes the fix was applied to Clients server and PCs.
Is there any way to check if there is corruption after a compact/repair?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will report back when we have run for a few days
Thank you all !!!
Thank you all !!!
ASKER
Problem still persists. Can a table be saved as text and re-imported. Would it help get rid of corruption or does Access remove corruption and leave blank fields in it's place?
<<Can a table be saved as text and re-imported.>>
You'd have to write that. Nothing built-in.
<<Would it help get rid of corruption or does Access remove corruption and leave blank fields in it's place?>>
It's impossible to tell what you'd see as it would depend what was written over the top of it.
Jim.
You'd have to write that. Nothing built-in.
<<Would it help get rid of corruption or does Access remove corruption and leave blank fields in it's place?>>
It's impossible to tell what you'd see as it would depend what was written over the top of it.
Jim.
ASKER
Thanks Jim
<<1. Is the linking of another version of Access to the BE likely to cause this issue>>
No.
<<2. Will updating our application to the same version have any effect.>>
No.
<<3. Is it more likely to be a data corruption problem. I noticed when compacting and repairing the BE Data that it took a very long time over 3 minutes. (using their native Access 16) File size 369,000 kb>>
Well I would ask, what corrupts as I'm not sure I understand what your your trying to say here. If your repairing the BE and it's a true BE with nothing but data, well then it is data corruption.
<<This is the same problem as posted earlier. The suggested Microsoft "Database is in an inconsistent state" fix has not solved this problem.>>
Is this the error message you are getting? When did the problem start? What OS's are involved?
Jim.