Large .accdb gets corrupted (3 Viewers)

[JohnPapa]

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.

 

[GPGeorge]

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.

 

[MajP]

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.

 

[RonPaii]

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?

 

[GPGeorge]

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.

 

[JohnPapa]

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

 

[JohnPapa]

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

 

[JohnPapa]

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.

 

[Gasman]

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?

 

[RonPaii]

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.

 

[RonPaii]

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.

 

[JohnPapa]

Could always try it out?
View attachment 122525

Goes up to A2016. I use 365.
Towards the end there was a problem with the installation.

 

[tvanstiphout]

Goes up to A2016. I use 365.

99.999% chance it will work with 365 as well.

 

[The_Doc_Man]

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?