Using Microsoft Money from a network drive can potentially introduce issues that affect the accuracy of your reconciliations. Here are a few considerations:
- Network Drive Stability: If the network drive experiences latency or connectivity issues, it could lead to data corruption or incomplete transactions being recorded. This might cause discrepancies in your reconciliation.
- File Access Conflicts: If multiple instances of Microsoft Money are accessing the same data file simultaneously (even if not intended), it could lead to conflicts and data integrity issues.
- Batch File Execution: The way you are launching Microsoft Money through a batch file should not inherently cause errors, but ensure that the cleanup script does not interfere with the data file while Microsoft Money is still running. If the cleanup occurs while the application is accessing the file, it could lead to unexpected behavior.
- Backup and Restore Issues: If your cleanup script deletes backups that are still in use or if there are issues with how backups are managed, it could lead to problems when restoring or accessing previous data states.
- Data File Size and Performance: If your data file has grown significantly over time, performance issues could arise, leading to potential errors during reconciliation.
To troubleshoot:
- Consider running Microsoft Money directly from the local drive instead of the network drive to see if the issue persists.
- Ensure that no other processes are accessing the Money data file while you are reconciling.
- Review the cleanup script to ensure it only runs after Microsoft Money has completely closed.
If the problem continues, you may want to explore the possibility of migrating to a more modern financial management application that offers better support and stability.