Corrupt database and disk i/o error 1

[PetitPal]

Dear all,

Here's an interesting one for you (well ok probably not, but none the less). I am currently unfortunate enough to be supporting a VB 3 app. running on an Access 2 database. I have a customer who's database spent most of last week corrupting itself on their new server, running windows 2000, (which nothing else corrupts on) and, apparently, they get the error message 'disk i/o' error when it dies and they try to access it. They also have problems backing this database up of the server, but don't have problems with anything else on the system.

According to MSDN 'disk i/o error' can mean that there is a problem with the database security file rather than the database. However I doubt this is the problem as the database itself becomes corrupted.

Does anyone have any ideas, at all, from the dim and distant past which might explain why an Access 2 database might kill itself repeatedly like this?

In desperation!

=)

PetitPal

p.s. I would guess a hardware problem, but everything else seems OK.

 

[NickISD]

PetitPal,
I have had this problem when a customer updated their lan to have a dedicated NT server running NTFS file system. Originally all worked fine when the Access 2.0 MDB was on one of the workstations on a shared drive. Once the MDB was moved to NT box the Access 2.0 would not allow connection via VB3. To fix this we deleted the locking file .LDB and then used Access 97 (without converting the database) to run a Repair on it. In 99 out of a 100 times this worked ok. For the other one we created a new Access database, then imported the existing table structure and data and all was then Ok. Access 2 does not like going from a Win 95/98 FAT file system to NTFS - there must be some kind of change occuring during the copy process.

When we created new Access 2.0 databases directly on to NT PC there has never been a problem.

Hope this helps

Regards, Nick W.

 

[PetitPal]

Thanks for your help, I'll give it a go!

=)

PetitPal