The firm is running Timeslips 2018 with 9 users. They get this error frequently (typically at least once a day). If we delete the LOCKS and LOGIN files listed below, that fixes it. We've made sure that all users have rights to the network location for Timeslips (G:\timeslips).

G:\timeslips\DBFiles\Server_Main\Locks.db
G:\timeslips\DBFiles\Server_Main\Login.db"

Any ideas on how to prevent this from occurring?

--
Neil Quateman