Microsoft (and I) have encountered a problem

[Middlemarch]

I'm getting really fed up with Access 2003 and 'Microsoft has encountered a problem....' after that I can't save my work or even get a screenshot of code. Three times in 2 days and a several hours of work lost.

It happens as I'm writing code and may have stopped execution, then changed something - e.g. reming out a line or Dimming a new variable. Especially, it seems, when it's anything to do with a Date.
It then offers to make a backup and eventually you get the database back, but both it and the backup are missing any last changes before the crash. So what's the point of restoring it as you could just load in the backup ?
I don't suppose there's any way to get back what you lose - or prevent the stupid thing from crashing in the first place ?



Thanks. I suppose one redeeming feature is, as I redo the code I make it better!

[RuralGuy]

Don't make any changes while still in the debugger.

[ssanfu]

I agree with RG.

Editing code while executing in single step mode is a known cause of corruption and crashes.

End the execution, make the changes, SAVE the changes, then single step through the code again.
After making changes to code, I always compile the code. After 3 compiles, I do a Compact and Repair.

Since following those steps, I have only had 3 crashes in the last 2 years....

[Middlemarch]

OK. Understood... guess I've been lucky until now and got into bad habits.
Thanks