Fix Access Error 2683: No Object in This Control
Question details
Resolve Access runtime error 2683 when code refers to an ActiveX control whose underlying object is unavailable.

- Product
- Microsoft Access
- Device & OS
- Windows; version not provided
- Scenario
- A form uses a legacy ActiveX control, and VBA code attempts to access that control.
- Observed behavior
- The debugger stops at the control reference, and Access reports that there is no object in the control. Adding an ActiveX control may also report that its OLE server is not registered.
In Access, open File > Account > About Access to check whether Office is 32-bit or 64-bit. Identify the affected control and its component before installing or registering anything.
Check and register the affected ActiveX control
Use this approach when the control is missing, unregistered, or incompatible with the installed Access bitness.
An ActiveX control must be installed and registered for the same bitness as Access. A 32-bit control cannot load in 64-bit Access, even on 64-bit Windows.
Open the form in Design View, select the affected control, and check its Property Sheet. Review the form's VBA code and the application's installation documentation to identify the control and its OCX or other component.
Obtain the control's installer from its vendor or the application's original installation package. Check that it supports your Access bitness, then run the installer according to the vendor's instructions.
If the vendor instructs you to register an OCX manually, open Command Prompt as administrator. On 64-bit Windows, use C:\Windows\SysWOW64\regsvr32.exe "C:\path\control.ocx" for a 32-bit control or C:\Windows\System32\regsvr32.exe "C:\path\control.ocx" for a 64-bit control. On 32-bit Windows, use regsvr32 "C:\path\control.ocx". Replace the example path with the actual trusted file path.
Close and reopen Access, open the form, and repeat the action that caused error 2683. If the control still fails, check its vendor's compatibility and installation requirements.

Replace an unsupported legacy control
Use this approach if the control is no longer supported or cannot run with your version of Access.
Work with exported Access data in WPS Spreadsheets
WPS Office is a free, lightweight alternative with a familiar interface for working with Office files. Export Access data to Excel format to move tabular work into WPS Spreadsheets. WPS does not repair Access ActiveX controls or replace Access forms and VBA applications.

Frequently Asked Questions
What does Access error 2683 mean?
It can occur when VBA refers to an ActiveX control but Access cannot access the underlying object. A missing, unregistered, incompatible, or unsupported control is one possible cause.
How do I check whether Access is 32-bit or 64-bit?
In Access, select File > Account > About Access. The About window identifies the Office version and bitness.
Can I use a 32-bit ActiveX control in 64-bit Access?
No. The control must match the bitness of Access. Look for a supported 64-bit version or replace the control with a compatible alternative.
Why does Access say the OLE server is not registered?
The component behind the control may not be installed or correctly registered, or it may be incompatible with Access. Check the control's vendor installation instructions and bitness before attempting manual registration.
Can WPS Office fix the Access control error?
No. WPS Office does not repair Microsoft Access ActiveX controls. For spreadsheet work, you can export Access data through External Data > Export > Excel and open the resulting file in WPS Spreadsheets; forms and VBA applications do not transfer as spreadsheet features.




