Others

Fix Microsoft Access Error: Create Report Control Requires Design View

Rana GarciaRana Garcia Oct 12, 2026 869 views

Question details

The user needs a way to resolve or work around an error preventing the programmatic creation or deletion of report controls during runtime in Microsoft Access.

Product
Microsoft Access
Device & OS
not provided
Scenario
Executing VBA code to dynamically add, remove, or modify controls on a Microsoft Access report while the report is actively running.
Observed behavior
Microsoft Access throws a runtime error stating that the application must be in Design or Layout View to create or delete report controls.
Before you start

Before modifying your VBA code, identify all report sections where dynamic text or elements are needed, and check if your database is currently compiled as an ACCDE file, as this strictly restricts runtime design changes.

Solution 1Recommended

Toggle the Visible Property of Pre-Created Controls

Instead of creating new controls dynamically at runtime, add them during the design phase and toggle their visibility using VBA when the report runs.

This is the safest and most reliable workaround. Microsoft Access locks the report structure during runtime for performance and security. By pre-creating the maximum number of controls you might need and hiding them, you bypass the need for runtime structural changes.

1
Add controls in Design View

Right-click your report in the Navigation Pane and select 'Design View'. Add all the text boxes, labels, or images you might require during runtime.

2
Set default visibility to hidden

Select the newly added controls. Press F4 to open the Property Sheet, navigate to the 'Format' tab, and change the 'Visible' property to 'No'.

3
Toggle visibility in VBA

Open the VBA editor and locate your report's formatting event (e.g., On Format for a specific section). Use code like `Me.YourControlName.Visible = True` to display the control only when your specific conditions are met.

Toggle the Visible Property of Pre-Created Controls
Best Practice: Using the Visible property ensures your database can still be compiled and deployed safely as an ACCDE file.
Free Microsoft Office alternative

Looking for a Lightweight and Free Office Suite?

While Microsoft Access is a powerful tool for complex database management, for your daily document processing, spreadsheet data analysis, and presentations, WPS Office provides a highly compatible, free, and lightweight alternative to Microsoft Office.

  1. 1. Download the installer: Visit the official WPS Office website and download the free installer tailored for your Windows, Mac, or Linux operating system.
  2. 2. Install the software: Run the downloaded file and follow the straightforward on-screen instructions to complete the setup process in minutes.
  3. 3. Open your documents: Launch WPS Office and easily open, edit, and save your existing Microsoft Office documents without formatting loss.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation with low system resource consumption.Familiar user interface for a seamless migration with zero learning curve.Built-in advanced PDF editing, conversion, and splitting tools.
QA img-9

Frequently Asked Questions

Why does Access prevent me from creating report controls in Report View?

Microsoft Access locks the structural design of forms and reports during runtime (Report View or Print Preview) to maintain security, ensure stability, and optimize rendering performance. Structural changes, such as adding or deleting controls, strictly require the object to be opened in Design View or Layout View.

Can I deploy an Access database as an ACCDE if my VBA creates controls?

No. If your VBA code relies on opening objects in Design View to create or modify controls, the code will fail in an ACCDE file. ACCDE files are pre-compiled and have their design modes permanently locked. You must either use an ACCDB file or switch to alternative methods like toggling the Visible property of existing controls.

How do I ensure all my VBA variables are properly declared to prevent errors?

Open the VBA Editor by pressing Alt + F11, click on 'Tools' in the top menu, and select 'Options'. Check the box for 'Require Variable Declaration'. This setting automatically inserts 'Option Explicit' at the top of all new modules, forcing you to declare variables and helping catch typos or compile errors before runtime.