Overview
Data Utilities contains the commands used to protect, restore, connect, and move company data. These actions can affect the entire company file, so they should be handled by an administrator or a trained support user.
Important: Always confirm the company name, database, and backup file before running a data utility. These commands are not normal daily transaction actions.
Where To Find It
Path: File > Data Utilities
The exact commands available can depend on whether QBM is connected to a company, the user permissions, and the current database state.
Recommended Workflow
- Confirm which company is open and whether other users are active.
- Create a backup before restore, attach, detach, import, repair, or update work.
- Use the specific utility needed for the support task rather than trying multiple commands at random.
- After the action, reopen the company and verify login, reports, and key transaction screens.
- Record what was changed so support and management can trace the action later.
Best Practice
- Keep recent backups before using restore, attach, detach, or open-from-file actions.
- Use restore on a test environment first when the business only wants to inspect older data.
- Do not detach a live company database unless the operational reason is clear.
- Use Save User Settings after a user's workstation is arranged correctly.
- Use Load User Settings carefully because it can replace the user's current layout and local preferences.
Troubleshooting
| Issue | What To Check |
|---|---|
| A command is disabled. | Check whether QBM is connected to a company, whether the user has access, and whether the command is allowed in the current database state. |
| Restore or open-from-file cannot continue. | Confirm the selected file is accessible and that QBM can close the current company connection safely. |
| Connection settings are wrong. | Review the server name, database name, and login information with the IT administrator or support team. |
| User settings did not restore as expected. | Confirm the settings were saved for the correct user and machine before loading them. |