Change in database format in SCP 2.9

Introduction

Because of an update to one of the toolkits we are using in SCP, we took the plunge to converting our entire code to compile to x64 (64 bit code). This doesn't really affect the use of the software, but it had one massive knock-on effect - we had to completely change the database format we are using to store materials and spring designs.

What has actually changed?

We are now using SQLite databases instead of Access MDB databases. This should be a seamless "behind the scenes" change, but there are a couple of potential issues, described below.

What does this mean to me as a user of SCP?

Any existing spring design databases are automatically converted to the new format the first time you start up SCP v2.9 or later. You will see a popup message telling you that the old database has been updated.

There are two potential issues however that it is worth knowing about:

If you have one or more shared design databases

The first person to run the new version of SCP will create an updated database based on the old file. If a second user carried on running the old version of SCP, they could read and write to the old database file. After they in turn update, they would lose the changes in the converted database.

Best solution - update all copies of SCP at the same time!

If your design databases are backed up

Make sure that the newly converted database files are included in any regular backups that you perform. This may happen automatically if you simply back up the contents of certain folders rather than specific files. If you don't back these up, please start doing so!