Data Import & Export

Why ACE OLEDB Renames an Excel Worksheet from A1 to _a1

Khadija KhanKhadija Khan Nov 13, 2026 868 views

Question details

The user wants to understand why ACE OLEDB creates a worksheet named _a1 when an export specifies a1, even though Excel accepts A1 as a manually entered sheet name.

Why ACE OLEDB Renames an Excel Worksheet from A1 to _a1
Product
Microsoft ACE OLEDB, Microsoft Access 2016, and Microsoft Excel workbooks
Device & OS
Windows
Scenario
Exporting an Access table or CSV data to an .xlsx workbook using an ACE OLEDB SELECT INTO query.
Observed behavior
The export creates a worksheet named _a1 instead of a1. The reported behavior occurs through both Access 2016 and PowerShell.
Before you start

Locate the destination name immediately after SELECT INTO in your Access query or PowerShell command. Use a new output workbook for testing so an existing destination sheet does not interfere with the export.

Solution 1Recommended

Use a destination worksheet name that does not resemble a cell reference

Choose a descriptive name such as Data_A1 or Sheet_A1 to avoid the reported ACE OLEDB naming change.

A1 is both a possible worksheet name and an Excel cell reference. Excel's worksheet-tab naming rules are not the same as the identifier handling used by ACE OLEDB when it creates an Excel destination through SQL.

In the reported export, ACE changes a1 to _a1, consistent with provider-side name normalization for a cell-reference-like identifier. This does not mean that A1 is an invalid worksheet name in Excel. The reproduction establishes the behavior, but it does not establish a complete, documented list of ACE naming rules.

1
Open the export query

In Access 2016, open the export query in Design View, then select View > SQL View. For the PowerShell reproduction, open the script and locate the assignment to $strQuery.

2
Replace the destination identifier

Change SELECT * INTO [a1] to SELECT * INTO [Data_A1] or SELECT * INTO [Sheet_A1]. Leave the IN destination path, Excel connection properties, and FROM source unchanged.

3
Run a fresh export

Set the destination path to a new .xlsx file, then click Run in Access or execute the edited PowerShell script. Open the resulting workbook and check the worksheet tab name.

4
Update dependent references

If another query or script reads the exported worksheet, replace its old worksheet reference with the new name. Where the reader uses Excel worksheet table syntax, use a reference such as [Data_A1$].

Use a destination worksheet name that does not resemble a cell reference
Square brackets do not prevent this behavior: The reported query already uses [a1], yet ACE still creates _a1. Bracketing the SQL identifier alone is therefore not a solution for this reproduction.
Free Microsoft Office alternative

Review and Rename Exported Excel Worksheets with WPS Spreadsheet

WPS Office is a free, lightweight alternative with a familiar spreadsheet interface and Excel format compatibility for easy migration. Open your exported workbook in WPS Spreadsheet to inspect or rename its worksheet tabs; WPS does not change or repair ACE OLEDB's export behavior.

Open and edit Microsoft Excel .xlsx and .xls workbooks.Inspect exported worksheet names and rename tabs after export.Use familiar spreadsheet controls without changing your workbook format.Move everyday workbook review and editing to a free, lightweight Office alternative.
microsoft office alternative - wps office

Frequently Asked Questions

Why can I name a sheet A1 in Excel, but ACE OLEDB changes it?

Excel permits A1 as a worksheet-tab name. ACE OLEDB processes the destination as a SQL identifier during export and applies its own naming behavior. In the reported SELECT INTO example, the cell-reference-like identifier a1 becomes _a1.

Will writing [a1] in square brackets keep the sheet name unchanged?

No, not in this reproduction. The original SELECT INTO query already uses [a1] and still creates _a1. Change the destination identifier to [Data_A1] or [Sheet_A1] instead.

Are all short worksheet names unsuitable for ACE OLEDB?

The issue is not simply name length. A1 resembles an Excel cell reference. Use a descriptive destination identifier such as Data_A1 rather than assuming every short name will be changed.

Is there a confirmed Microsoft rule documenting this exact rename?

The supplied record does not identify a Microsoft document that specifies the exact a1-to-_a1 transformation. Excel worksheet naming rules alone do not explain ACE's SQL export behavior. Test your chosen destination name with the ACE provider version used by your workflow.

Can WPS Office stop ACE OLEDB from adding the underscore?

No. ACE OLEDB controls the sheet name when it creates the export. WPS Spreadsheet can open the resulting .xlsx workbook so you can inspect the sheet or right-click its tab and select Rename, but it does not modify ACE's naming rules.