Fix STG_S_CONVERTED (0x00030200) Compound File Error

You're opening an old Access database (or an Excel file with embedded OLE objects) and instead of seeing your data, you get STG_S_CONVERTED (0x00030200) - The underlying file was converted to compound file format. This usually happens when someone migrated a database from an older format (like Access 97 or 2000) to a newer one, but the internal structure didn't update cleanly. I've seen it most often with .mdb files opened in Access 2016 or later, and with Excel files that contain embedded Word documents or Visio diagrams that were created in Office 2003 or earlier.

What's Actually Going On?

Under the hood, this error means the file's storage format got partially converted. Think of it like a file that started as a plain text document but was then half-saved as a Word .docx. The operating system sees the new container (compound file format) but the content inside still has old metadata or pointers that don't match. The error is a warning, not a full crash—it's telling you the conversion happened but might be incomplete.

In plain English: the file got caught mid-transition between two file formats. It's not necessarily corrupted, but it's not fully usable either.

The Fix: Compact and Repair (Access) or Re-Save (Excel)

For Access Databases

1. Make a backup first. Copy the .mdb or .accdb file to another folder. I've seen compact-and-repair fail on rare occasions, so don't skip this.
2. Open Access. Go to File > Open and browse to the problematic file. Don't double-click it—that might trigger the error again.
3. In the Open dialog, click the dropdown arrow on the Open button and select Open Exclusive.
4. Once the database opens (it might show the error again, but that's okay), go to File > Info > Compact & Repair Database.
5. Access will scan the file, fix the conversion issues, and compress the data. This almost always clears the STG_S_CONVERTED error.
6. Save and close. Reopen normally.

For Excel Files with OLE Objects

1. Open Excel, go to File > Open and select the file.
2. When the error appears, click OK to dismiss it. The file should open in a limited state.
3. Right-click each embedded object (e.g., a Word document embedded in a cell) and choose Document Object > Convert.
4. In the Convert dialog, pick the current format (e.g., Word Document) and check Display as icon if needed. Click OK.
5. Save the file as a new name under File > Save As, choosing the current Excel format (.xlsx).
6. Close and reopen the new file—error should be gone.

Still Getting the Error?

If the fix above doesn't work, the file might have deeper structural damage. Try these in order:

• Open in Safe Mode: Hold Ctrl while launching Access or Excel. This disables add-ins that might interfere with the conversion.
• Export data, not the file: For Access, create a new blank database, then import all objects (tables, queries, forms) from the broken one. For Excel, copy all sheets to a new workbook.
• Check file permissions: If the file is on a network share, the conversion might fail halfway due to write restrictions. Move it to your local desktop first.

Had a client last month whose entire print queue died because of this—well, not the queue itself, but the database driving their label printer. One compact-and-repair later, they were back in business. It's usually that simple.