Tab Control

G

Guest

I recently created a form with a tab control. I placed a command button
(find record) on the form and I get the following error:

The expression On Click you entered as the event property setting produced
the folliowing error: A problem occorred while Microsoft Office Access was
communicating with the OLE server or ActiveX Control.

I get this error if when I use any command button using the wizard?

Anyone know what is happening?

Thanks.
 
A

Allen Browne

The error indicates that there is some name in your procedure that Access
can't make sense of, or a problem with the procedure itself.

In the code window, choose Compile on the Debug menu.
Does this point you to a particular line that is the problem?

If not, copy the whole procedure out to Notepad, and delete it from your
code. Is the database working okay now? Including the wizards?

If so, you can then work through that procedure to identify which part has
the problem.

If nothing else helps, it might be a corruption.
The steps below might help, but they are not specific to your issue:

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.
 
S

strive4peace

'~~~~~~~~~ Compile ~~~~~~~~~

Whenever you change code or references, your should always compile
before executing.

from the menu in a module window: Debug, Compile

fix any errors on the yellow highlighted lines

keep compiling until nothing happens (this is good!)


you may need to check your references too:

from a module window: Tools, References...

if anything is MISSING, uncheck it and find an appropriate substitution


Warm Regards,
Crystal
*
:) have an awesome day :)
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top