I understand why eM Client enforces mandatory database checks after unclean shutdowns, and I’m not asking to bypass those safeguards.
What would be extremely useful is read-only or user-triggered database verification tooling, for example:
- A visible database “health” status
- A manual “verify integrity” option that does not block startup
- A way to run checks at a time that suits the user
At present, users have no way to confirm database health except by observing whether a forced check occurs, which makes troubleshooting and planning difficult — especially on laptops prone to unexpected shutdowns.
This would improve transparency without reducing safety.