Should I start db over?

[G deady via AccessMonster.com]

I probably should have asked this question before now but better late than
never. Recently, I got a coding error that completly locked me up. I had to
do a hard reboot. When I reopened my db every line of code in the db was gone.
Fortunately, so I thought I had backed up the db. So I opened the backup and
proceeded from there but it didn't seem right. I would compile code then save
a form. When I reopened the form the code would be gone. Or my event coding
would keep disappearing from the property setting. I was afraid I had trashed
Access and would have to reinstall. Before I did that I started the db from
scratch and built the first few rables from scratch. I didn't have any any
problems. After that I started importing my tables, forms, querys, etc.
Then earlier today I put calendar controls on the form bound to the table I
was working on when I crashed and coded them. The code was working perfectly.
I saved the form. I just reopened it and now I get an error message when I
try to fire the event for either calendar. So far I am only going errors on
this form. I have imported about 10 other tables and forms and have had no
problems. Do I delete this one table and rebuild it then continue to import
the others and hope for the best or do I bite the bullet and start the db
over from scratch?
Am I likely to have other problems down the road. As much as I don't want to
I'd rather start over now than get all done and find out I have a fatal error.

 

[Allen Browne]

It is possible to configure and run Access so it does not corrupt your
database. The specifics will depend on your version.

This article lists the things that will cause your database to corrupt:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

Work through both the general list (for installed databases), and the
developer's list, one at a time.

The article does not suggest keeping your references to a minimum, but that
can also help to avoid errors (not so much corruptions.) For example, I
personally perfer to use a standard Access form as a calendar rather than
another library to reference. There's one you can copy at:
http://allenbrowne.com/ser-51.html
And there's more info on references at:
http://allenbrowne.com/ser-38.html

 

[G deady via AccessMonster.com]

Allen, Thank you. I will read but I'm afraid it may be too late. I think I
have a serious problem. I went to delete the table the form I am having
problems with is bound to and I got a message telling me "the OLE server may
not be registered. To register the Ole server reinstall it."
Does that mean I have to reinstall Access? I am using Access 2003

 

[Allen Browne]

If another database (such as Northwind) works, then the problem is unlikely
to be with the Access/Office install.

 

[G deady via AccessMonster.com]

If another database (such as Northwind) works, then the problem is unlikely
to be with the Access/Office install.

Allen, I followed the instructions in your article and created a new db then
imported. Everything imported except for 3 forms including the one that had
been giving me trouble.(I didn't expect the other 2 to import. I had changed
the underlying tables and hadn't gotten ro fixing the forms yet). Everything
has been working fine. My code recompiled fined. I still don't undersand
how a form in my backup db got trashed when got crashed . Apparently Access
trashed all forms in any db with the same name as the one I was working on at
the time I locked up. Not sure how that is possible but nothing else makes
sense. Anyway, your help is greatly appreciated. I was really afraid I was
going to have to start from scratch.