Hi JJ,
In addition to the Office service packs that John Vinson has advised that
you install, I'd like to add that you should make sure to install the
latest
service packs for your operating system and the JET database engine as
well.
Here is a KB article that provides information to assist you:
How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=300216
As to your statement:
"The code thingy window opens pointing at a command134 which I deleted
yesterday. It was a button that I decided I didn't need."
When you delete controls (command buttons, text boxes, list boxes, etc.)
on
a form, any code that was associated with the control is NOT automatically
deleted (at least not in Access 2000 / 2002--I'm not sure about Access
2003).
This leads to code that is still present for non-existant controls. You
should go through your code and delete all unused procedures. I call this
cleaning out the spiderwebs.
To prevent spiderwebs in your code in the future, make sure to display the
properties dialog (View > Properties in form design view). Select the
control
in question. Make sure that you see the name of the control shown in the
blue
title bar of the properties dialog (it will be blue when selected). Select
the Event tab in the properties dialog for a control before deleting it.
If
you see any event procedures listed, click into the event procedure. You
should see a build button display. This is a small button with three dots.
Click the build button. It should cause the Visual Basic Editor (VBE) to
open
up, with the cursor positioned in the proper event procedure. Select the
entire procedure and delete it. Return to form design view. Follow any
additional event procedures in a similar manner, and delete them. When all
event procedures have been removed, you can then delete the control.
In Access 97 and 2000, you can easily get an ambiguous name error if you
delete a control that had code behind it, without first deleting the code,
and then you later add the same control back with similar code and the
same
exact name. The command button wizard includes the ability to assign a
name
to the control as a last step in the wizard. If you pick the same name the
second time around, in versions of Access prior to 2002, you will get the
ambiguous name error when you attempt to click on the command button. This
error is prevented by first cleaning out the spiderwebs, as I have already
described.
Good Luck,
Tom
______________________________________
:
Hi
Everything was fine. Created a database, very basic, tables and forms.
Now when I'm clicking the buttons I created I'm getting this message.
"Error accessing file. Network connection may be lost".
Huh???? what network connection??
The code thingy window opens pointing at a command134 which I deleted
yesterday. It was a button that I decided I didn't need.
Then when I close the code thingy window, it says it's debugging althought
nothing seems to be happening at all.
I do have a copy of the database which works ok but what on earth did I do
wrong and how can I avoid that happening?
JJ
