Follow the object chain
- Verify the DAO reference/type library expected by the compiled project.
- Capture errors from workspace and
OpenDatabaseinitialization. - Resolve relative/network paths in the application user’s context.
- Check lock-file creation, sharing mode and permissions.
- Inspect recordset type, saved query parameters and Jet-specific SQL.
| Reference missing | Build/runtime DAO version or registration problem. |
|---|---|
| Could not lock file | Directory write access, existing users or stale state. |
| Too few parameters | Misspelled field or unresolved query parameter. |
Repair or migrate
Keep DAO when the application is stable and its Jet behavior is understood. Moving to ADO is not a mechanical replacement: cursor, parameter, locking and SQL behavior require tests.
Use VB6 Access applications, MDB recovery, error 91 analysis and the pillar.
Provide exact DAO error, reference version, database path, locking context and failing code/query.