cgajendran
New member
- Local time
- Today, 10:32
- Joined
- Feb 24, 2009
- Messages
- 2
Hi, I am support a application which was running for the past 4 years. This is completely developed by MS access and written in VBA.
Suddently the application is facing the above error at the following lines,
DoCmd.OpenForm FormName:="frmNewPeerGroup", View:=acNormal, windowmode:=acWindowNormal, OpenArgs:=5
Many instances this DoCmd.OpenForm command it giving the error in message box says,
_____________________________________________________________
The expression On Click you entered as the event property setting
produced the following error: The OpenForm action was cenceled.
* The expression may not result in the name of macro, the name of a
user-defined function, or [Event procedure].
* There may have been an error evaluating the function, event, or macro.
_____________________________________________________________
This is the error message i am receiving.
My problem is, the same code was running around 3 years, but suddenly some updates to microsoft or office updates might have changed this.
Could any one came across this error in the past weeks. Please let me know what else we can make this to work.
Suddently the application is facing the above error at the following lines,
DoCmd.OpenForm FormName:="frmNewPeerGroup", View:=acNormal, windowmode:=acWindowNormal, OpenArgs:=5
Many instances this DoCmd.OpenForm command it giving the error in message box says,
_____________________________________________________________
The expression On Click you entered as the event property setting
produced the following error: The OpenForm action was cenceled.
* The expression may not result in the name of macro, the name of a
user-defined function, or [Event procedure].
* There may have been an error evaluating the function, event, or macro.
_____________________________________________________________
This is the error message i am receiving.
My problem is, the same code was running around 3 years, but suddenly some updates to microsoft or office updates might have changed this.
Could any one came across this error in the past weeks. Please let me know what else we can make this to work.