SAVING CHANGES TO FORM SHUTS DOWN DATABASE!

[st8employee]

It's the weirdest thing:

I have worked in this form a thousand times...and mever a problem before,
but now all of a sudden when I go into the design view of the form to edit
controls when I save, I get an error message that wants to send an error
reprot to microsoft and then it shuts down my database and creates a backup.

What happened? Why does this only happen on this one form and not any
others? I have experienced this also in another database in the past...and I
remember I could do nothing to resolve it:

I tried SELECT ALL and copying all of the objects to a new form - still
shuts down.

I tried importing a copy of the form from an earlier version the same
database before I experienced problems - still shuts down.

I tried compact and repair - still shuts down.

I tried rebooting the computer (last ditch effort) then repeated all of
these - STILL shuts down.

PLEASE help me. My users have GOT to have this data entry form...and I
REALLY don't want to COMPLETELY rebuild it...

Any assistance will be much appreciated.

 

[John W. Vinson]

I tried rebooting the computer (last ditch effort) then repeated all of
these - STILL shuts down.

PLEASE help me. My users have GOT to have this data entry form...and I
REALLY don't want to COMPLETELY rebuild it...

Your database is corrupt, probably in the code portion but maybe elsewhere.

See http://www.granite.ab.ca/access/corruptmdbs.htm for a thorough discussion
of corruption.

Do you have a backup copy of the database? If not... you now know why all
serious Access developers keep backups. :-{(

If you're VERY lucky you may be able to create a new, empty database and use
File... Get External Data... Import to import all the objects in this database
into a new one.

If you have not already done so (as would appear to be the case) you should
immediately split your database into a "backend" containing only the tables,
and a "frontend" containing the forms, queries, reports, etc. Each user
should have their own copy of the frontend (and you'll be able to work on form
changes freely without worrying about corrupting the only working copy).