Problem occured while communicating with OLE Server or Active Cont

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

Guest

What once worked fine in Access 97 now gives the following error message: "A
problem occured while MS Office Access was communicating with the OLE Server
or Active Control"

I have a simple command button that updates data in 2 different fields.
This triggers a text field setup with a Conditional Format to change
depending upon the data.

Immediately after converting to Access 2003, the function worked but it was
sluggish. Also, when I selected the Design View button some of the subforms
would remain in Form view.

I downloaded the latest Windows Updates but this did not have any impact
 
There are several possible issues here, but it is most likely either a bad
reference or a corruption.

Firstly, Access 2000 and later do show your subforms in place in design
view. Microsoft listened to feedback that many of us hated that, so you can
now right-click the subform control and choose Subform In New Window.

Next, there was no Conditional Format (CF) in A97, so the sluggishness may
be related to that. It's not difficult to trigger an endless recalcuation
loop with CF. Remove any CF on this form until you get this problem solved.
If it is still sluggish without the CF, there is a whole raft of issues to
consider. Tony Toews has a great list called the Performance FAQ at:
http://www.granite.ab.ca/access/performancefaq.htm

Now, to solve the actual problem:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
If you want to know why, see:
http://members.iinet.net.au/~allenbrowne/bug-03.html

2. Compact to get completely rid of the "Name AutoCorrupt" stuff:
Tools | Database Utilities | Compact

3. Open a code window, and choose References on the Tools menu. Are any
reference marked "MISSING"? If so, you need to re-register that library.
Details in:
http://members.iinet.net.au/~allenbrowne/ser-38.html
The article also explains the references you do need - typically just
Access, VBA, and DAO. Uncheck the boxes for any libraries you don't need.
(This is important to the robustness of the app.)

4. Close Access. Decompile a copy of 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"

5. Open Access, and compact again.

6. Open a code window, and check that the application compiles (Compile on
Debug menu).

At this point, you probably have a working application, and so you can work
on getting the conditional formatting running again. If not, the next step
is to get Access to rebuild the database for you, by following the steps for
the first symptom in this article:
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html
 
Back
Top