Fix 0x00000650: Record field does not exist

What triggers 0x00000650

You'll see this error when an application tries to read a record field that's missing — either in a database table, a COM object, or a registry key. I've mostly seen it with legacy apps (think VB6, old Access databases, or custom ERP software) running on Windows 10 or 11. The culprit is almost always a corrupt registry entry or a broken COM registration.

30-second fix: Reboot and re-run the app

Don't roll your eyes — this works more often than you'd think. Temporary glitches in the COM subsystem or registry cache can cause a field to 'vanish' momentarily. A full restart flushes that crap out.

1. Save your work.
2. Restart the PC. Not shut down + boot — actually restart so Windows clears the session state.
3. Open the same application and reproduce the action that caused the error.
4. If it's gone, you're done. If not, move to the next step.

5-minute fix: Clean the registry and re-register COM components

When the reboot doesn't cut it, the issue is often a corrupt registry key pointing to a missing field definition. Here's how I've fixed this dozens of times:

Step 1: Identify the source program

Check the Event Viewer (Event ID 1000 or 1001 under Windows Logs > Application). Look for the faulting module name. If it's an old Access .mdb or a custom .exe, you've got your target.

Step 2: Re-register the COM DLLs

Open Command Prompt as admin (right-click Start > Command Prompt (Admin)). Run these commands in order:

regsvr32 /u %windir%\system32\mscomctl.ocx
regsvr32 %windir%\system32\mscomctl.ocx
regsvr32 /u %windir%\system32\comctl32.dll
regsvr32 %windir%\system32\comctl32.dll

This re-registers the most common COM controls that cause field-record errors. If you know the specific .ocx or .dll your app uses, substitute that.

Step 3: Check for orphaned registry keys

If the app is from an old installer, it may have left a broken CLSID in the registry. Fire up Regedit (again, as admin). Go to:

HKEY_CLASSES_ROOT\CLSID\{00000000-0000-0000-0000-000000000000}

But replace that GUID with the one from the error message (if you have one). If the key exists but points to a missing DLL, delete the InprocServer32 subkey and re-register the DLL fresh. I've seen this happen with old Visual FoxPro apps — their GUIDs linger after an uninstall.

15+ minute fix: System file integrity and database repair

If the above didn't work, the problem might be deeper — corrupt system files or a damaged database file. This is the nuclear option.

Run SFC and DISM

Corrupt Windows system files can break COM registration. Run these commands in an admin command prompt:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

SFC will replace any corrupted files. DISM fixes the component store. Both take about 15 minutes. Reboot after they finish and test the app.

Repair the database file (if applicable)

If your app uses a local database file (like an .mdb, .accdb, or SQLite .db), the field error could mean a corrupt table structure. For Access:

1. Close the app.
2. Open Access (or the Database Manager if it's a different engine).
3. Run Compact and Repair (Database Tools > Compact and Repair Database).
4. For SQL Server, run DBCC CHECKDB('YourDatabaseName') in SSMS.

I've seen this resolve the error when it's tied to a specific record — like clicking on a row with a missing column value.

Final resort: Reinstall the application

Uninstall the app completely, reboot, then reinstall from a fresh copy of the installer. Avoid using backups of the registry or DLLs — get clean files. This rules out any corruption in the app's own components.

When to call it quits

If you've gone through all three stages and still see 0x00000650, the app likely has a hard-coded reference to a field that never existed — or it's incompatible with your Windows version. Try running the app in compatibility mode for Windows 7 or XP SP3. Right-click the .exe > Properties > Compatibility tab. If that still fails, contact the vendor. Sometimes the 'field does not exist' error is actually a licensing bug or a broken update — I've seen that with old Autodesk and Sage apps.