Office Apps Crashing

Fix Microsoft Access Crashes When Opening Forms in 64-Bit Access

Tauseeq MagsiTauseeq Magsi Nov 14, 2026 870 views

Question details

Identify why an Access form crashes in 64-bit Access after an application is migrated from 32-bit Access.

Product
Microsoft Access
Device & OS
not provided
Scenario
A user opens a form in an existing Access application after moving from 32-bit to 64-bit Access.
Observed behavior
Access closes unexpectedly when the form is opened, although the same MDB file works in 32-bit Access.
Before you start

Confirm which Office architecture is installed in Access by selecting File > Account > About Access. Identify the affected form and any subforms so you can test their controls and code separately.

Solution 1Recommended

Isolate incompatible ActiveX controls and form events

Use this approach when a form works in 32-bit Access but closes 64-bit Access during opening.

The crash may occur while Access initializes a control, subform, or event, before execution reaches the next line after DoCmd.OpenForm.

1
Inspect the form in Design View

In the Navigation Pane, right-click the affected form and select Design View. Check the form and its subforms for ActiveX controls, including progress bars.

2
Test controls and subforms separately

Create a test copy of the form, then remove or replace one suspect ActiveX control or subform at a time in Design View. Open the test form after each change to identify the component associated with the crash.

3
Check form event code

In Design View, open the Property Sheet and select the Event tab. Review procedures attached to events such as On Open, On Load, and On Current, then test with suspect event procedures temporarily disabled in the test copy.

4
Replace or rebuild the affected component

Use a 64-bit-compatible version of the identified ActiveX control if one is available, or rebuild the affected control or form with a supported alternative. Open the form again in 64-bit Access.

Isolate incompatible ActiveX controls and form events
Check subforms too: A control or event in a subform can cause the main form to close Access while it is opening.
Free Microsoft Office alternative

Work with Office documents using WPS Office

WPS Office is a free, lightweight alternative for everyday documents, spreadsheets, and presentations. Its familiar interface and Office format compatibility help make the transition easier. It does not repair Microsoft Access or run Access forms and databases.

Use a familiar interface for everyday office tasksOpen and edit compatible Microsoft Office formats, including DOCX, XLSX, and PPTXWork with spreadsheet data as an alternative for suitable non-database tasksUse a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why does my form work in 32-bit Access but crash in 64-bit Access?

A control, API declaration, or form event may depend on 32-bit behavior. Open the form in Design View and check its ActiveX controls, subforms, and event procedures for compatibility.

Is adding PtrSafe enough to fix every API declaration?

No. In the VBA editor, review each Declare statement against the API documentation. Pointer and handle values may need LongPtr, while other parameters must retain their appropriate types.

How can I tell which control causes the crash?

In a test copy of the form, remove or replace one suspect ActiveX control at a time in Design View, then open the form after each change. Repeat the process for subforms if necessary.

Does a successful VBA compile prove the form will open?

No. Select Debug > Compile in the VBA editor to catch compilation errors, but also test the form and its controls in 64-bit Access. Runtime compatibility or form initialization can still cause a crash.