Total Office Manager Update

Release Notes for Version 26.1.1500
Release Date: 01/15/2026 (rolling release)

Thank you for trusting Aptora Corporation with your business management software. We appreciate your feedback and support.

Database Update

This update requires an update to your database. This will require that all users log out of the software program so that the update can run. Once the update has run and the first user logs in, other users will be able to log back into the program in prior versions without being required to update. This update will take anywhere from 15 seconds to 5 minutes depending on the database size.

Enhancements/Modifications

The following contains feature requests submitted by users like you:

The following contains feature requests submitted by users like you:

1. Smart Lists: We made general improvements to the Smart List feature including speed and stability enhancements. Error handling was improved to provide more meaningful messages and user information.
2. Payroll Setup Wizard: We removed the Payroll Setup Wizard. This was not being used and fees up space. After removing this and the old schedule board, we are now about 7MB smaller (5%).
3. This build also includes some additional work to try avoid, fix, or surface a new bug or issues that cannot be reproduced. This is the user filter bug in the custom data viewer.
4. We fixed a long-standing issue in frmWorkOrderList where “Add to Existing Smart Lists” could appear to succeed but no work orders were actually added. Root cause: both the Work Order list and the Smart List “Add to List” dialog were treating TDBGrid bookmarks as numeric row indexes, which is unreliable. That caused the code to read the wrong record IDs (often the same one repeatedly) and the insert logic would then skip everything as “already exists,” with no error shown. We changed the implementation to use bookmark-safe selection handling (set the grid’s Bookmark to each selected bookmark and read the id column value directly), simplified the insert to a direct INSERT … WHERE NOT EXISTS, and added a small results summary message (Added/Skipped/Bad IDs) to make outcomes visible. This eliminates silent failures and makes troubleshooting much easier.
5. We also tightened up SQL/filter reliability and error handling around list queries. Quick-filter logic was updated to avoid ambiguous AND/OR precedence issues by ensuring OR-style conditions are bracketed correctly before being passed into the SQL builder. We also reduced “hidden failures” by removing/avoiding patterns that masked runtime errors (especially Error 9 scenarios) and by adding safer bounds checks where UI bookmarks and arrays interact. The goal was to prevent malformed SQL and “check your filter” dead-ends that were hard to diagnose.
6. Finally, we updated the “Data View” filter builder and its related query forms (the Data View query editor and its sister filter editor) with the same safe patterns: bounds-checking bookmarks before indexing arrays, preventing UI control overruns when DB data contains more filter rows than the UI supports, and improving performance by reusing recordsets instead of re-opening them inside loops. Net effect: fewer intermittent “subscript out of range” issues, faster save/load of filter criteria, and more predictable behavior when users build and reuse saved filters.