Access Subform Locks Up After Report Print Preview

M

Mark Bigelow

I have a form with five different tabs and three different subforms (on
different tabs). This just started happening recently and I can't tell
what I did to make it happen.

If I click a button on the main form to print preview a report (based
on the current form and subforms) the report comes up just fine. But
when I close it, the subforms are no longer accessible. The main form
elements work just fine. But when I click on the subforms it's as if
they are completely frozen. Drop-downs don't work and I can't add or
delete records.

Oh, and there's no code involved in previewing or closing the report.

Any ideas?
Thanks!
Mark
 
A

Allen Browne

Mark, what you describe is a pretty straight forward kind of operation, so
something else has to be wrong.

Presumably this happens with just this one combination of form and report,
i.e. you can print/preview other reports okay while the form is open?

If so, try following these standard steps for recovering a database that is
corrupting:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html
 
Top