Restoring from an old backup on purpose

There may be a time when you actually want to restore an older backup -- for instance if you made a bunch of major changes just for testing (or you goofed), and you want to restore the database to its previous state.  Normally when you restore the data, it asks if you want to re-apply the changes again from the log (or worse yet, it gets them automatically from the network).  

Here's how you can keep them from coming back (and keep if from asking to apply changes):

Since you're going backwards it normally assumes you want to get up to date (e.g. you restored from an older backup and so it wants to recover the changes since then also).  It's actually getting them from the log files, which are also on each computer if you're networked, but since each client also has a "newer" database than you want then you would have to wipe that out too.

The only way to go backwards with a restore is:

1. Delete all log files from *each* computer (the log files have a PRKLOG extension, and are located in the same folder as the database file -- so delete *.prklog).

2. Restore the old database using Maintenance / Restore.  If you're networking, restore to the Master workstation first.  It won't be able to refresh from the clients now that all of the logs are deleted.

3. Also if you're networking, go to *each* client and do Maintenance / Network Functions / Request a full database refresh  -- this copies the whole database from the server to each client, wiping out the "newer" version they had).