A problem occured while Microsoft Access was communicating with the Ole server or ActiveX Control

Marcin Zmyslowski <ma*****@kapy.b ydg.pl> wrote in
news:HJ******** *****@news.uswe st.net:

I have a database created in MS Access 2003 which works fine in
Win2000. This database shows me the following message in WinXP:

"The expression On Load you entered as the event property setting
produced the following error: A problem occured while Microsoft
Access was communicating with the Ole server or ActiveX Control"

I also get similiar errors On Load, On Click etc. with the same
sentence "The expression...Ol e server or ActiveX control"

I have the newest version of Microsoft Jet 8.0 SP installed on
WinXP.

I have all references active in reference window. There is no
missing references in the VB code form when I open it both on
WinXP and Win2000.

When I compile the vb code there is no error message shown.

Do you have any idea why it gives me such errors?

An ActiveX control used somewhere in the application is not
installed/registered properly on the WinXP machine.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

It is likely to be an ActiveX Control as David suggests.

If it's not you may wish to check your MDAC installation with the
ComChecker available at:
http://www.microsoft.com/downloads/d...displaylang=en

An ActiveX control used somewhere in the application is not
installed/registered properly on the WinXP machine.

Thank you for your help. I will check it tomorrow. Now I am at home.
Could you give me some suggestions how to register ActiveX control.
I am using only subform.

M.

Marcin Zmyslowski wrote:

Hello all!

I have a database created in MS Access 2003 which works fine in Win2000.
This database shows me the following message in WinXP:

"The expression On Load you entered as the event property setting
produced the following error: A problem occured while Microsoft Access
was communicating with the Ole server or ActiveX Control"

Do a Google search on the error message.

This type of error is caused by all kinds of things. Most have
nothing to do with using an ActiveX control.

"news.onet. pl" <ma************ **@poczta.onet. pl> wrote in
news:dr******** **@news.onet.pl :

An ActiveX control used somewhere in the application is not
installed/registered properly on the WinXP machine.

Thank you for your help. I will check it tomorrow. Now I am at
home. Could you give me some suggestions how to register ActiveX
control. I am using only subform.

Well, you have to identify what the ActiveX control is first, and
then you ave to determine if the files for it are on the machine and
unregistered, or completely lacking.

One possibility is that you are using the calendar control and it
was not installed when the WinXP had Access installed on it. I can't
say for A2K3, but with other versions of Access, the calendar
control was not installed by default.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

First, identify the ocx you're missing

Then, using the "START/RUN..." menu option enter

regsvr32 ocxpath

e.g., regsvr32 C:\WINDOWS\syst em32\MSCOMCTL.O CX
You can drag the ocxpath from explorer into the run command
Mark

On Tue, 31 Jan 2006 21:32:50 +0100, "news.onet. pl"
<ma************ **@poczta.onet. pl> wrote:

An ActiveX control used somewhere in the application is not
installed/registered properly on the WinXP machine.

Thank you for your help. I will check it tomorrow. Now I am at home.
Could you give me some suggestions how to register ActiveX control.
I am using only subform.

M.

I think it is not a problem of unregistered ocx.
I haven`t added any new references into the database and I haven`t put
any not needed references.

I`ve removed all other references and now I have only such references:
- Visual Basic For Application
- Microsoft Access 11.0 Object Library

After these changes the database works correctly on Win2000/AC2003, but
it doesn`t work well on WinXP/AC2003 machines and it stills return the
same error I`ve mentioned before.

I don`t use any ActiveX controls in my database, but only subform and I
use a public function written in a module.

Moreover, I have completely different database which I`ve opened on this
WinXP/AC2003 machine. It works fine and there is no ActiveX controls
inside a form, so that (first) database is causing so many problems - I
don`t know.

Do you have any idea why it doesn`t work?

Thank you in advance for all posts
M.
*** Sent via Developersdex http://www.developersdex.com ***

I have checked again. I have imported this form into the new clean
database. I have removed all events from a form. And I still gets the
same error messages.

I have checked if any other databases are working similar like it which
is causing so many problems. And I have noticed that every other
database is working fine, except from this special one.

Do u have any idea what it is going on with this database?
Kindes regards
Marcin
*** Sent via Developersdex http://www.developersdex.com ***

"Marcin Zmyslowski" <ma*****@kapy.b ydg.pl> wrote in message
news:qy******** *******@news.us west.net...

I have checked again. I have imported this form into the new clean
database. I have removed all events from a form. And I still gets the
same error messages.

I have checked if any other databases are working similar like it which
is causing so many problems. And I have noticed that every other
database is working fine, except from this special one.

Do u have any idea what it is going on with this database?
Kindes regards
Marcin

There are only a limited number of tricks you can try and you seem to have
tried a few already. Nobody has yet mentioned the /decompile switch which
might help (see http://www.granite.ab.ca/access/decompile.htm) and you could
look at the general page http://www.granite.ab.ca/access/corruptmdbs.htm

At some point, you may have to give up on this and re-create the form
manually. Is it only one form causing the problem and how much work would
this be for you?