CORRUPT DATABASE? I'VE TRIED EVERYTHING, PLEASE HELP!!!!

[franksirvent]

Hi there

I am trying to make changes to a form and when I try to save it the whole database stops while the HourGlass is there, supposely doing something...
Stays like that for several minutes
The only way to recover is by pressing alt+ctl+del then deleting the MDB from the list (which says 'Not Responding')

I've tried everything:
1. Used /decompile from within DOS (OK)
2. Ran Compile from within Visual Basic Window (OK)
3. Ran Compact and Repair (OK)
4. Imported al ltables, forms, queries, etc to new database. (OK)

But as soon as I do any changes to any form on the database it stops...Not Responding.

This is only a Front End (the data is on a separate database)

None of the above works.

I've tried doing same on two different PC's but same problem, so I assume the problem is within the database...

Any more ideas before I pull out the few hairs I got left ???

thanks

 

[franksirvent]

Thanks for your comments pseale
I am doing exacly what you said, backing up 3-5 times lately after what happened.
It is really frightening to loose a lot of work thinking hat 'nothing will happen in the next few hours'

Obviously I am learning that Access is not as stable as I thought it was...

thanks

 

[jsteph]

Frank,
I still use Access 97 for much of the Access projects I do, for the rest I use Access 2003. I will never use Access 2000 for anything ever again--even though I recall that there was a service pack/patch put out that addressed those code corruption issues.

The problems I had with Access 2K were so severe that it's like when you get food poisoning--even after the restaurant has been cleared by the health department, you still can't go back there--the memory of the sickness is so strong and won't go away.
--Jim

 

[franksirvent]

Dear jsteph,

Thanks for your info.

There is no question that something is 'funny' with the version of Access 2000. What it does simply is not trustworthy and I know one day something will go really bad and I won't be able to recover.
Also I don't like that fact that it seems to be getting worse...one day I will not be able to recover as previous back ups will also have that problem...

I have already made enquiries and my IT dept will purchase Access 2003 for me, however I do need to know if I can save my applications as .MDE from Access 2003 and will it work with Access 2000 which is what the rest of the users will use.
Do you know?

 

[lameid]

I don't know for sure about you MDE question. However I remember reading another thread that suggested that there may be a reference difference between the versions and therefore compiled code may not work even if the databases are in 2000 format. Something to check into... I don't
use Access 2000 and 2003 so I can't check or compare but the concern seems valid.
The references I have for Access 2003 are...

Visual Basic For Applications
Microsoft Access 11.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library

You could look at the Visual Studio Tools for Office so that you could package and distribute the Access 2003 runtime for free. That is of course assuming I.T.'s issue is cost for deploying Access 2003 and not labor.