Event Procedure on subform (2K)

Topic

New Reply

I am currently working on making changes to a database originally created by someone else.

The main form has a tab control, and one of the tabs contains a subform. I’ve just redesigned the subform from datasheet to continuous forms. When I try to run any event procedure from an event or command button on the subform I get the following error:

“The expressions On Click you entered as the event property setting produced the following error: A problem occured while SHIP database 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.”

I looked in the MSKB and I changed the name of the command button and the subform control to resolve any possible naming conflicts, but I am still getting the error.

I have tried running a message box with a test message from a command button, field double-click event, and form before-update event, but I always get a version of this message.

Can anyone help?
Thanks,
Karl

Reply | Quote

Replies

If you added a command button to your subform, and put a single line of code (nothing more than a msgbox warning) in the Click event procedure for that button, you still get the system error message?

Reply | Quote

Yes, I still get it.

Reply | Quote

You wrote that the database was originally created by someone else. Does the main form or subform contain an ActiveX control, such as the Calendar control, or a TreeView? If so, you may have a different version on your PC, or a different install location. The easiest remedy is to write down the properties of the offending control, delete it, put a new one on your form and set the properties as they were for the original one.

Reply | Quote

No, there aren’t any ActiveX controls on the subform or the main form.

Thanks,
Karl

Reply | Quote

As a follow-up to my problem, I ended up rebuilding the form from scratch, and I no longer receive the error.

Thanks again to Mark & Hans,
Karl

Reply | Quote

Unfortunately, a corrupted form can give you that message even though it is misleading. I suppose the “server” in question in this case is Access itself.

Reply | Quote