VBA & Macro Problems

Fix Access Runtime Errors in a Citrix ACCDB Database

Kushani NimanthikaKushani Nimanthika Nov 18, 2026 869 views

Question details

Identify and fix runtime errors in an Access 2013 database application running through Citrix.

Product
Microsoft Access 2013 Runtime
Device & OS
not provided
Scenario
Users open forms in an ACCDB application deployed through Citrix.
Observed behavior
Access reports that execution has stopped due to a run-time error, potentially because of VBA compile errors or invalid object references.
Before you start

Open the editable front-end ACCDB in a full version of Access, since Access Runtime does not provide the VBA editing tools needed for debugging. Note which form or action triggers the error and check whether the required linked tables and referenced objects are available.

Solution 1Recommended

Compile and debug the front-end VBA code

Use this approach to identify compile errors and expose the error hidden by suppressed error handling.

1
Open the VBA editor

Open the front-end ACCDB in full Access and press Alt+F11 to open the Visual Basic editor.

2
Compile the project

Select Debug > Compile in the VBA editor. Fix each reported error and repeat the command until the project compiles without errors.

3
Check missing references

In the VBA editor, select Tools > References and look for entries marked MISSING. Correct any missing references required by the application, then compile again.

4
Expose the runtime error

Find the procedure triggered by the affected form and temporarily remove or comment out On Error Resume Next. Run the affected action in full Access and inspect the error message and highlighted line.

5
Check object references

At the failing line, verify that the named form or report is open and that the referenced subform, subreport, or control exists before calling Requery or another method. For a reference such as Reports![nav_EquipRfsTask]![taskList].Report.Requery, confirm that taskList is the correct subreport control.

6
Restore appropriate error handling

After correcting the cause, add or restore targeted error handling in the affected procedure and test the form action again.

Compile and debug the front-end VBA code
Free Microsoft Office alternative

Use WPS Office for everyday documents and spreadsheets

WPS Office is a free, lightweight alternative for working with Office documents in a familiar interface. It supports common Microsoft Office formats for an easier transition, but it cannot repair or run an Access ACCDB application.

Work with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTX.Use a familiar interface for documents, spreadsheets, and presentations.Install a lightweight office suite for everyday work.Keep using Microsoft Access to maintain and troubleshoot ACCDB databases and VBA code.
microsoft office alternative - wps office

Frequently Asked Questions

Can I debug VBA code in Access Runtime?

Access Runtime does not provide the full VBA editing tools. Open the editable front-end ACCDB in a full version of Access, press Alt+F11, and use the VBA editor to compile and debug it.

Why should I remove On Error Resume Next while debugging?

On Error Resume Next can suppress the error that identifies the failing operation. Temporarily remove or comment it out in the affected procedure, reproduce the issue in full Access, and inspect the reported error and highlighted line.

Does creating an ACCDE automatically fix runtime errors?

No. An ACCDE compiles the front-end project for deployment, but code can still encounter runtime errors. Use Debug > Compile, fix the reported issues, and test the affected actions before and after creating the ACCDE.

Should I convert the back-end database to ACCDE?

No. Create the ACCDE from the front-end application, not the back end. Keep the back end in its database format so the linked tables remain available.

What should I check if a Requery line fails?

Confirm that the referenced form or report is open and that the named control exists. If the expression uses .Report or .Form, check that the control is the intended subreport or subform control.