buttons don't work

[Peter]

Hi,

I have an Access 2000 database that I was working on in the office. I
uploaded the mdb file onto my server and then I downloaded it onto my home
computer. But for some reason none of the buttons on my form work.

I get the following error everytime I press the buttons:

The expression OnClick you entered as the
event property setting produced
the following error : A problem occurred
while Microsoft Access was communicating
with the OLE server or ActiveX control.

*The expression may not result in the
name of a macro, the name of a user-defined
function, or [Event procedure]

*There may have been an error
evaluating the function, event or macro


As a matter of fact any new button that I create in the form will have that
error.

However, if I create a new form and I create a new button with an event
procedure, it works fine.

Anyone have any idea why?

Thanks.

Peter

 

[Gary Miller]

Peter,

Sounds like this could be a 'missing reference' problem.
This is common when moving a program from one computer to
another.

Open up any code module and then go to Tools/References on
the menubar and see if any are listed as 'Missing'. If so,
you will need to investigate what it is that is missing and
correct the problem.

Gary Miller

 

[Ken Snell]

Also sounds as if the form that's not working may be corrupted, especially
as you note that a new form works ok.

 

[Dirk Goldgar]

Also sounds as if the form that's not working may be corrupted,
especially as you note that a new form works ok.

Hi,

I have an Access 2000 database that I was working on in the office.
I uploaded the mdb file onto my server and then I downloaded it onto
my home computer. But for some reason none of the buttons on my
form work.

I get the following error everytime I press the buttons:

The expression OnClick you entered as the
event property setting produced
the following error : A problem occurred
while Microsoft Access was communicating
with the OLE server or ActiveX control.

*The expression may not result in the
name of a macro, the name of a user-defined
function, or [Event procedure]

*There may have been an error
evaluating the function, event or macro


As a matter of fact any new button that I create in the form will
have that error.

However, if I create a new form and I create a new button with an
event procedure, it works fine.

Anyone have any idea why?

I've seen this happen when there's a compile error somewhere in the code
behind the form. The form's class module can't be compiled, so though
you can open the form, clicking the buttons to call into the class
module causes this error. The first thing I'd do to investigate is open
the VB Editor and click Debug -> Compile. See if an error is then
brought to your attention. It may well be an error due a broken
reference, but it could also be something else.

 

[Peter]

Thanks for all of your replies. But I found that the buttons worked again
after I downloaded the same file back to the office computer.

Could my Access 2000 at home have something that is preventing me from using
buttons ?

Peter

Also sounds as if the form that's not working may be corrupted,
especially as you note that a new form works ok.

Hi,

I have an Access 2000 database that I was working on in the office.
I uploaded the mdb file onto my server and then I downloaded it onto
my home computer. But for some reason none of the buttons on my
form work.

I get the following error everytime I press the buttons:

The expression OnClick you entered as the
event property setting produced
the following error : A problem occurred
while Microsoft Access was communicating
with the OLE server or ActiveX control.

*The expression may not result in the
name of a macro, the name of a user-defined
function, or [Event procedure]

*There may have been an error
evaluating the function, event or macro


As a matter of fact any new button that I create in the form will
have that error.

However, if I create a new form and I create a new button with an
event procedure, it works fine.

Anyone have any idea why?

I've seen this happen when there's a compile error somewhere in the code
behind the form. The form's class module can't be compiled, so though
you can open the form, clicking the buttons to call into the class
module causes this error. The first thing I'd do to investigate is open
the VB Editor and click Debug -> Compile. See if an error is then
brought to your attention. It may well be an error due a broken
reference, but it could also be something else.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

 

[Dirk Goldgar]

Thanks for all of your replies. But I found that the buttons worked
again after I downloaded the same file back to the office computer.

Could my Access 2000 at home have something that is preventing me
from using buttons ?

As Gary Miller originally posted, it's most likely a References problem.
Often when databases don't work on one particular machine, it's because
of a broken or missing reference. This page discusses the problem
exhaustively.


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

 

[Guest]

Hi all,

I am having a similar, yet different problem to that described below. I have a form/subform setup, in which the
methods for the data members (click, lostfocus) cause the following error:

The expression On Lost Focus you entered as the event property setting produced the following error: A
problem occurred while ... System was communicating with the OLE server or ActiveX Control

* The expression may not result in the name of a macro, the name of a user-defined function, or [Event
Procedure].
* There may have been an error evaluating the function, event or macro.

Every other form and subform in the System works, but for this one. Why is it so?


----- Dirk Goldgar wrote: -----

Thanks for all of your replies. But I found that the buttons worked
again after I downloaded the same file back to the office computer.
from using buttons ?

As Gary Miller originally posted, it's most likely a References problem.
Often when databases don't work on one particular machine, it's because
of a broken or missing reference. This page discusses the problem
exhaustively.


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html