Since Enviro Data stores your data in a backend database, what are the best practices for maintaining this database?

Question

Accepted Answer

Maintaining a backend Access database—especially in a split architecture like Enviro Data uses—requires a blend of vigilance, automation, and structural discipline. Here's a comprehensive rundown tailored to your environment:
Core Maintenance Best Practices
Compact & Repair Regularly
• From either the Editor or Viewer run Clear Temporary Tables, found under Maintain Database • Compact and Repair can be run from the Access Menu by clicking on Database Tools and then Compact & Repair. .• It must be run on the backend database and not from Enviro Data however, it can also be run in Enviro Data to fix any potential program issues. .• Prevents bloat and fragmentation.• Schedule it during off-hours and it cn also be run using a utility database or script.• Ensure no active connections (check that there are no .laccdb lock files present).
Backup Strategically
• Daily incremental backups + weekly full backups.• Automate backups with PowerShell or Task Scheduler.• Store backups offsite or in cloud storage with versioning.•You should also back up your Settings8.mdb file since it is also linked to Enviro Data. 
Monitor File Size & Growth
 • Access has a 2GB limit per .accdb file.• Track growth trends and archive old data if needed.
 Security & Access Control
Restrict Permissions
• Backend should reside on a secure network share with limited write access.• Use NTFS permissions to control who can read/write/delete.
Encrypt & Password-Protect
• Apply encryption via Access’s built-in password feature. It used to be true that if you enabled the Access security it would apply to all Access files. Maybe it works better now.• Consider encrypting the network share or using BitLocker for sensitive data.
Audit Access & Changes
• Use logging tables or external audit tools to track who accessed what and when.• Especially useful for regulatory compliance or client-facing systems.
Structural Integrity
Avoid Direct Access to the Backend Tables
• Use stored queries or pass-through SQL for complex operations.• Prevent users from interacting directly with backend tables.• DO NOT STORE YOUR DATABASE FILES IN ONEDRIVE, SHAREPOINT. OR DROPBOX. See here for more information.