Closing a Form with a Command Button

[JoeM]

I have an old 2003 (mdb) Access database that I am working on (I currently have Access 2007). We still have some users who use Access 2003, so we have not updated/converted it yet (the database is split into back/front-ends).

I have created a few new forms. First, I have a Selection Form where the users enters in the criteria to bring up their particular clients data. In then opens up a Continuous Form for data entry. I placed a Close/Exit command button in the Form Footer. If I use the Command Button Wizard for this buton, it creates the following code:

Private Sub cmdClose_Click()
On Error GoTo Err_cmdClose_Click

    If Me.Dirty Then Me.Dirty = False
    DoCmd.Close
Exit_cmdClose_Click:
    Exit Sub
Err_cmdClose_Click:
    MsgBox Err.Description
    Resume Exit_cmdClose_Click
    
End Sub

When I first created it, it worked. But now when we try to use this button, we get the following error message:

The expression On Click you entered as the event property setting prodcued the following error: A problem occurred while Microsoft Office 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.

I tried simplying my code to these variations, but it made no difference:

 
Private Sub cmdClose_Click()
    DoCmd.Close
End Sub

 
Private Sub cmdClose_Click()
    DoCmd.Close acForm, Me.Name
End Sub

I have searched the internet, and found various posts on the topic, but haven't found one yet that seems to apply to my situation.

I should also add, if they just click on the "X" in the upper right-hand corner, the form closes without issue. It just doesn't seem to like the Close/Exit command button anymore.

Any ideas?

[Missinglinq]

Since your code has absolutely nothing to do with any ActiveX Controls, my guess would be that the Command Button has become corrupted! While we usually thinks in terms of Forms or entire Databases becoming corrupted, Controls can and do become corrupted, as well. I'd replace the errant button and use your original code.

Linq ;0)>

[JoeM]

A good thought. I failed to mention that I already tried creating a brand new command button to close the form, and that new button returned the same error. So that does not seem to fix it.

[JoeM]

Is it possible for the Form itself to become corrupt, or the VB module itself?
I tried adding a new command button somewhere else on the form that simply returns a Message Box with the phrase "Hi", and that returns the same error.
So I think the issue is on a bigger scale, related to the Form itself or VBA module.

[JoeM]

Yep, it looks like the VBA Module itself became corrupted. We removed all the VBA code, copied the form to a new name, and then recreated the buttons, and it worked.

[Missinglinq]

...I tried adding a new command button somewhere else on the form that simply returns a Message Box with the phrase "Hi", and that returns the same error.

The fact that another button returned the same error is proof that the corruption is more widespread than the one Control. But the best approach is to start checking out the easiest to replace first and then move out to Form and then the database itself!

Glad you got it working again!

Linq ;0)>