Large .accdb gets corrupted (2 Viewers)

JohnPapa

Registered User.
Local time
Today, 20:48
Joined
Aug 15, 2010
Messages
1,132
A client's .accdb gets corrupted every couple of months. The size of the db is around 300MB and the network is around 15 pcs. It is a dental practice management db. On the same server there two other dental .accdb with the same structure but much smaller, maybe 30MB and 70DB. Never had a problem with the latter.

When the corruption occurs, I can compact and repair the db, I can enter the FE (.accde), but some functionality is lost.

I have copies of the non-corrupted db and the corrupted db. Are you aware of a way to find out where are the differences, so that I maybe find out the reason and how to fix it?

It does not help that maybe 8 of the pcs are 4th generation (2013) i3.

Is there a tool, apart from writing vba, to compare the two dbs.
 
I have a tool that can do a side-by-side comparison of two accdbs. It's called AccessDiff. It is a paid commercial product. I used it regularly when I was still working with client databases and needed to compare versions during development.
 
I can compact and repair the db, I can enter the FE (.accde), but some functionality is lost.
I am not sure what that means. I interpret that to mean that after you C&R the corrupted backend you lose some features in the front end? That seems strange and I can only guess that the backend is still corrupted but to a lesser extent. Can you explain the features that you lose? I have never heard of anything like that.
 
It does not help that maybe 8 of the pcs are 4th generation (2013) i3.
I don't see using older computers causing a problem, unless they have problem network cards or are crashing while your application is open. I am just now replacing some computers this old but they have been connecting to a BE with 30 other users without issue. You may want to verify that none of your users are connecting over WIFI or a WAN, even occasionally because that will lead to corruption. You are running a split FE/BE and all users have a private copy of the FE?
 
Along those same lines, I recall an installation at a client site where the "network guy" had actually draped the Cat5 network cables over the top of a fluorescent light fixture instead of going to the bother of putting it above the ceiling tiles. When the lights were turned on or off in that room, the network responded by blinking ever so briefly. Access database corruption regularly ensued.
 
I am not sure what that means. I interpret that to mean that after you C&R the corrupted backend you lose some features in the front end? That seems strange and I can only guess that the backend is still corrupted but to a lesser extent. Can you explain the features that you lose? I have never heard of anything like that.
The corruption is in the BE. The same FE works fine in the non-corrupt BE
 
I don't see using older computers causing a problem, unless they have problem network cards or are crashing while your application is open. I am just now replacing some computers this old but they have been connecting to a BE with 30 other users without issue. You may want to verify that none of your users are connecting over WIFI or a WAN, even occasionally because that will lead to corruption. You are running a split FE/BE and all users have a private copy of the FE?
In our case the forms are complicated, one has 500 controls with graphics etc
 
Also, what is not helping is that the tables are linked. The patient table has 20 000 records, each record has many fields, so each time it deals with this number of records.

The software also has a connection to a telephone system and can dial telephone numbers and lookup incoming telephone numbers.
 
I have a tool that can do a side-by-side comparison of two accdbs. It's called AccessDiff. It is a paid commercial product. I used it regularly when I was still working with client databases and needed to compare versions during development.
Could always try it out?
1764949836486.png
 
In our case the forms are complicated, one has 500 controls with graphics etc
500 controls on a single form points to a usability issue not corruption unless it also opens and hold locks on 100s of tables.
 
Also, what is not helping is that the tables are linked. The patient table has 20 000 records, each record has many fields, so each time it deals with this number of records.

The software also has a connection to a telephone system and can dial telephone numbers and lookup incoming telephone numbers.
Save edits before connecting to the telephone system.
 
You described a lot about your users, but how are they connected into this system? Is there even the slightest chance that they are using Wi-Fi?
 
I'm sorry to hear you have trouble installing the AccessDiff 15 day trial. I've had the product installed since around 2007 and found it very useful for comparing versions of mdbs and accdbs for clients whose applications I worked on.

On my computer, the latest version I have is the 2013 version, in both 32 bit and 64 bit. It runs just fine under M365 and handles accdbs created and modified in M365. The only limitation (if you can call it that) is that i have to use the appropriate bitness for accdbs created with 32 bit or 64 bit Access. I would imagine that it might have trouble with newer features like Extended Date and Time fields. Not something I've had occasion to deal with.

You mentioned searching for a URL that it couldn't find. I am certain that the product is not out of support, but it is likely that their focus is more on .net products than Access products. I don't know what to tell you about that beyond suggesting a visit to their support page. https://kellermanstores.com/Help/AccessDiff/webframe.html#Welcome.html assuming you really want to give it a serious try.

However, all of this may be a moot point, if you have other ways to track down the corruption problem.
 
I'm sorry to hear you have trouble installing the AccessDiff 15 day trial. I've had the product installed since around 2007 and found it very useful for comparing versions of mdbs and accdbs for clients whose applications I worked on.

On my computer, the latest version I have is the 2013 version, in both 32 bit and 64 bit. It runs just fine under M365 and handles accdbs created and modified in M365. The only limitation (if you can call it that) is that i have to use the appropriate bitness for accdbs created with 32 bit or 64 bit Access. I would imagine that it might have trouble with newer features like Extended Date and Time fields. Not something I've had occasion to deal with.

You mentioned searching for a URL that it couldn't find. I am certain that the product is not out of support, but it is likely that their focus is more on .net products than Access products. I don't know what to tell you about that beyond suggesting a visit to their support page. https://kellermanstores.com/Help/AccessDiff/webframe.html#Welcome.html assuming you really want to give it a serious try.

However, all of this may be a moot point, if you have other ways to track down the corruption problem.
Until about a year ago I also used A2013 and it did serve me well. I was using 32 bit and invested the time and made it work on both 32 and 64 bit.

I now use A365 and even though it runs on both 32 and 64 bit, I have upgraded all clients to 64 bit. It makes my life a bit easier, since I do not have to have Access 32 bit around anymore.

Regarding the corruption, as I mentioned on the specific server there are 3 .accdb, with the largest being around 300Mb. The other two are under 100MB. The problem which appears only on the large db happens every couple of months and is always the same, in the appointments the patient's names disappear but not the other info that is stored for each appointment. If I do a compact and repair the names appear but I cannot add the name in the appointment. Now that I think about it the problem may be in the patients table which stores about 20 000 patients.

I ended up doing a backup of the .accdb every 2 hours, which minimizes the data loss. My backup is very crude, I first create a copy of .accdb and then use 7zip to copy the copied file on the cloud. The corruption does not happen when I do the backups and since I do not work on the db itself, the problem is minimized there. I use Task Scheduler which appears to work fine. I may try to use a proper backup software like CrashPlan.
 
Cloud? That's a significant issue. Is there a chance that any part of the affected DB is trying to run from a cloud server?
 

Users who are viewing this thread

Back
Top Bottom