Opening a form cause Access to quit unexpectedly

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,
When opening some of the forms in my database or when saving changes in the
form design or in the form code, the project gets closed unexpectedly
(Ms-Access 2000). It does not happen all the time, but sometimes, I have to
try 2 or 3 times before successfully opening the form. It happens more often
on some PC stations than on others, usually more on those working on Windows
XP than in Windows 2000 for example.
The form source is a linked table, and the On_Open and On_Current events of
the form itself contain code that controls the user's restrictions to some
data by checking a table in a secured external database, and locks some of
the controls on the form accordingly.
However, no error message shows when it happens. Only the "Send error
message to Microsoft" shows up when the database is already closed.
I've tried storing the backend database on the same computer to avoid
network interactions, but it doesn't help. I've also tried to debug and
simplify the code in the form, but it doesn't help me identify where the
problem is, since this problem doesn't not happen systematically.
Does anyone have a clue of what the problem could be?
 
Could be several things.

Firstly, since multiple users use this database, make sure you have split
it, and given each user a separate copy of the front end. If that's a new
concept, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html

There's a good chance that something is corrupting in this db. Try this
standard squence (in order):

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/Repair

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 (holding down the Shift key if you have any startup code),
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, reference ambiguities are resolved,
and the code syntax is compilable.

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
 
Thanks.
This will surely help. For now at least it explains why some code suddenly
gets so long to run without any good reason.
 
Back
Top