As a reference to others, the Timeslips database had been moved to a one drive folder. This was not a "healthy" environment for Timeslips. We moved the database to a local drive and that resolved the issue. Also made some changes to help with performance. Timeslips data cannot reside on a cloud drive.
↧