Problem with Combo Box Why?

[Guest]

I have always put a combobox using the combox wizard on my form that search a
record on the form, but this time, its telling that the expression after
update you entered as the event property setting produced the following
error: A problem occurred while Proffesional Database was communicating with
the Ole Server or ActiveX Control.

I checked the references and there is nothing missing, and I have checked
the right references, so what could be the problem....

 

[rmullen]

you may not want to use the combo box wizard .. wizards are great to do simple queries . .but what you're pulling in could be confusing access .. can you paste your underlying query of the combo box and maybe i'll take a look at that and hopefully that's where the problem is

 

[Allen Browne]

If the references are fine, and the code compiles okay, it sounds like the
database has begun to corrupt.

Try this sequence:

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