Error while openning form

[Rana]

When I try to open a for in an Access database I get a pop-up dialgue box
with the follwoing message:

The expression On Current you entered as the event property setting produced
the follwoing error: A problem occurred while Microsoft Access was
communicating with the OLE server or ActivX 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.

How to solve this problem?!!

 

[ruralguy via AccessMonster.com]

Open the db while holding down a <SHIFT> key and then troubleshoot the
problem.

When I try to open a for in an Access database I get a pop-up dialgue box
with the follwoing message:

The expression On Current you entered as the event property setting produced
the follwoing error: A problem occurred while Microsoft Access was
communicating with the OLE server or ActivX 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.

How to solve this problem?!!

 

[Rana]

The db open normaly when I hold down <shift> key

Open the db while holding down a <SHIFT> key and then troubleshoot the
problem.

When I try to open a for in an Access database I get a pop-up dialgue box
with the follwoing message:

The expression On Current you entered as the event property setting produced
the follwoing error: A problem occurred while Microsoft Access was
communicating with the OLE server or ActivX 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.

How to solve this problem?!!

 

[ruralguy via AccessMonster.com]

Holding down a <SHIFT> key when you open a db will disable any startup code
that is in place. Now that you are in the db, you can troubleshoot the error
you were getting. Examine the Autoexec macro or whatever form you were
loading at startup.

Open the db while holding down a <SHIFT> key and then troubleshoot the
problem.

[quoted text clipped - 11 lines]