Error 3159 and 3022

We are having a corruprion problem at one of our users.
Since Dec 2007 they have had about 6 or 7 serious corruption problems.   The basics are that the index inside the database gets corrupted.   In the end the user ends up with a 3022 error or a 3058 error.
We end up having to Jetcomp the file and in one case the only way to recover was to export all tables to text format and import them back in.
The database is in Access 97 format and the front end is VB6.   The app has been running fine for many years.
The only other "downside?" is that this client is using windows Vista on abotu 1/2 of the workstations.
Any ideas would be great... thanks.... Dave
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

ClassicCanadaConnect With a Mentor Author Commented:
For some reason a second export and cleanup seems to have fixed the problem.   We decided the XP compatibility was not what we wanted.
Run it under XP compatability.  I have seen this problem beffore and it was fixed by enabeling compatablility mode

Right click the Microsoft Access 97 executable > click Properties >
Compatibility (tab)

Thats strange... I wonder if it has something to do with vistas retar... um funny file security.
Closed, 500 points refunded.
Community Support Moderator
All Courses

From novice to tech pro — start learning today.