Command Button Wizard error message

[pfb77]

When I try to use the wizard to put a command button on a form I get this
error message:

Error accessing file. Netword connection may have been lost.

It then wants to send an error report to Microsoft and shutsdown Access. I
have try everything to correct this problem and I need desperately to use
this function. I have created macros to go around this problem, but I get
the same results.

Any help would be appreciated.

I am running MS Access 2003 and had a trial version of 2007 that will do the
same thing.

I run windows XP and have 1GB of RAM.

 

[Allen Browne]

Presumably this problem occurs in one database file only?
For example, if you try to run the wizard in the Northwind sample database,
it's okay there?

If so, there is a problem with this database. It could be several things.
This sequence (in order) should address most of them:

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