Sounds like something is locked. There are multiple ways to find this the easiest is to try shutting down the old computer if it still exists. If that is the problem you should then be able to move forward. Other options are to close Timeslips and then search for pdoxusrs.lck, pdoxusrs.net or paradox.lck files on server and computer. Delete any found then open Timeslips and try again. If you can't delete you might reboot the server.

the computer I moved this from is shut off. But Timeslips is still on this old computer. I searched for these files on the new computer (assuming I know how to search for such files) and found nothing. I don't have a server. Can I pay you to fix this for me?

I would be happy to help you. I have sent you my contact information via the private messaging. Before we connect, you might try rebooting your computer if you have not already done so. I look forward to hearing from you.

I am in the office all day tomorrow unless you want to talk tonight. My number is 952-210-2212. I am on Mountain time.

Ken Ross

I've seen this sometimes when I bring a database in for conversion, and open it on my system. For some reason it will have a false positive login from the remote machine that I have to clear. Try this:

Exit Timeslips (including TSTimer, check Task Manager to see if it is running as a process).
Start, Programs, Timeslips, Station Administrator.
The very first screen will tell you if it "thinks" anyone is using the database. If you see anything there, clear it. It will put up a couple of 'warnings', you will have to click through.
After you have done that, try to open Timeslips and make a backup again.

If you still have trouble, Caren should be able to help you.

This was Timeslips 2015 so no TSTimer.
In this case the issue was the database had been created inside c:\Program files (x86). Not in a folder but directly inside. We moved the database folders into a separate folder and then the backup worked correctly.

Nice catch Caren! Thanks for posting the resolution.