Access 2007 Deleted records. All fields replaced with ####

[notconfident]

I have an access accdb database created in Access2007. It is loaded on another Access2007 PC in the office where it is shared by 2 other PCs using Access2010.
It has been running fine for years with around 11,000 records.
Lately we have encountered a bug which has happened on two occasions weeks apart.
The database created a MSysCompactError table saying "Unrecognized database format 'Z:\Backup of MyDatabase.accdb'." - ErrorCode -1206. Plus it created a backup of the database.
Z: is the Folder on an Access2010 PC referring to the Access2007 PC where the database actually sits.
On the first occasion 3 records had ALL string fields replaced with #. If it was a field of say 10 characters it would now contain 10 x character #. The greatest number of ## was 16 even if the field could hold more so the record was effectively lost. On the second occasion 2 records were affected.
To "fix" the problem we deleted the bad records, ran Compact and Repair and the database would be ok again !!!
We cant work out what was actually happening at the time but it looks like the PC that was using the database appears to work ok its just when another user tries to open the database.

Each time I perform a mod to the programming of the database I run Compact and Repair to tidy things up but that is not when the error happens.

Any ideas ????

 

[lameid]

Access 2007 and Access 2010... Are both systems fully patched and running 32 bit Access vs 64 bit Access (I think only possible starting in 2010 for 64 bit)?
If not, make it so or upgrade to fully patched 2010 at least on both machines to run mixed 32 and 64 bit Access.

After that two thoughts, there is a hardware / network problem or the file is corrupt.
For file corruption, I just posted something in another thread, see thread181-1785494
Also if you could try tabbing on the error data as described in that thread and letting us know the result it would be appreciated.

Smart money is it is the HD on the host machine or Random file corruption that is just not getting cleaned up by conventional means (see the thread above).

That said I am going to throw out some broad hardware / network thoughts that can be researched more in more appropriate forums.

The rest - Easiest to prove by moving the file to a different machine and not using that machine as a client but does not necessarily cover all problems

Network: First on the host machine for the backend ensure the network drivers are current.
It could be a patch cable (including kinks or overly sharp turns), a port on a switch, a chip on a switch, network drop or Electro Magnetic interference near any part of it.

Hardware on the machine - really anything but usually moving parts so the HD itself (check the SMART codes for the drive), the cables or just the seating of the cable (unplug it and plug it back in) or anything cooled by a fan that is getting too hot because of a failed fan.