Export refused because of unsaved work
Symptom: export, import, status, sync or commit is refused and names objects that are not saved, or a
dialog that is open in Access.
Environment
All versions of the WKL Office SDK, when the database is open in Access.
Cause
The SDK works in the Access that has the database open. SaveAsText writes the saved state of an object, so an export would miss an unsaved change, and an import would replace work that exists only in Access. While Access shows a dialog, it cannot be automated.
Resolution
Save or discard the named objects in Access (also code changed in the VBA editor), close the dialog, and run the command again. Access keeps running; the SDK never quits an Access a developer opened.
en/wiki/msaccess/sdk/troubleshooting/export-refused-unsaved-work.txt · Zuletzt geändert: von Wolfgang van der Stille