You receive an error message when you start Visual Basic for Applications code in an Access database
This article has been archived. It is offered "as is" and will no longer be updated.
When you start Microsoft Visual Basic for Applications (VBA) code in a Microsoft Access database, you may receive an error message that resembles the following:
The expression On Click 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.
This issue may occur if the following conditions are true:
- You create an event handler, a function, or a subroutine to start the VBA code in an Access form or report.
- You run the VBA code on a computer that uses different non-Unicode language settings than the computer on which you created the event handler, the function, or the subroutine.
To resolve this issue, use the appropriate method.
Method 1: Verify the non-Unicode languageIf you are running the VBA code on a Microsoft Windows XP-based computer or on a Windows 2000-based computer, you may be able to resolve this issue by changing the non-Unicode language setting on the computer where you are running the VBA code. To verify and to change the non-Unicode language setting, follow these steps.
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, click Run, type Intl.cpl, and then click OK.
- Under Language for non-Unicode programs on the Advanced tab, verify that the language matches the language on the computer on which you created the event handler, the function, or the subroutine. If the language differs, click the language that you want, and then click OK.
- Restart the computer.
Method 2: Remove accented characters or special characters from the VBA code and from database objectsTo resolve this issue, remove any accented characters or special characters that appear in the VBA code or in database objects. For example, form sections and report sections that were created in localized versions of Access may contain accented characters or special characters.
To rename an Access object, or a section in an Access object, that contains accented characters or special characters, follow these steps:
- Start Access, and then open the database that you want.
- Right-click the form or report that you want, and then click Design view.
- Right-click the object that you want, and then click Properties.
- On the All tab in the Name box, type a name that does not contain accented characters or special characters.
- After you rename the objects, open Visual Basic Editor to determine whether your changes appear in the VBA code. The objects may retain the original names. If this behavior occurs, you must manually rename the objects in the VBA code.
Steps to reproduce the issue
- Start Access on a computer where the Russian versions of Windows XP and Microsoft Office 2003 are installed.
- Create a new Access database.
- Add a form to the database. By default, a form that is named Form1 is created.
- In Design view, add a command button to the form.
- Right-click the command button that you added in step 4, and then add the following code example to the Click event for the command button.
On Error GoTo Err_cmdMsgBox_ClickMsgBox "Hello World"Exit_cmdMsgBox_Click:Exit SubErr_cmdMsgBox_Click:MsgBox Err.DescriptionResume Exit_cmdMsgBox_Click
- Compile the Access database.
- Close the Visual Basic code window, and then close the Access database.
- On a computer where the English versions of Windows XP and Office 2003 are installed, verify that the non-Unicode language is set to English (United States).
- Copy the Access database that you created in step 2 to the computer in step 8.
- Open the Access database, open the form that contains the command button, and then click the command button to run the VBA code.
Article ID: 907337 - Last Review: 12/09/2015 03:14:35 - Revision: 1.2
Microsoft Office Access 2003, Microsoft Access 2002 Standard Edition, Microsoft Access 2000 Standard Edition
- kbnosurvey kbarchive kbtshoot kbbug kbprb KB907337