Opening older Base files after an update, and why it's safe

Software changes, and files have to keep up. When Base gains new features, the file has to make room for them, and the question is what happens to the databases you made last year. Base by Zaweba answers it carefully, so updating the app never puts your records at risk.

Older .obase files open as before. The first time you open one in a newer Base, it moves the file up to the current format, and before it does, it saves a backup copy of the file exactly as it was.

What the update does

Moving a file up adds whatever the newer version needs to keep its features. Your tables, records, queries, forms and reports stay as they were, and you carry on working. Most of the time you won't notice anything except that the newer features are now available in that database.

The backup copy is the safety net. If anything about the update surprised you, the original file is in the Backups folder under Documents\Base by Zaweba, and File > Backup copies lists it alongside the daily copies.

Opening a newer file in an older Base

The other direction is just as important. If someone with a newer Base sends you a file and you open it in an older version, the older Base refuses it with a clear message, rather than opening it and possibly damaging the parts it doesn't understand.

That might seem unhelpful at first, but it protects the file. An older version could otherwise save over new design information it can't read, and the person who sent it would lose work. The fix is simple: update Base, then open the file.

Sharing databases between PCs

Because each database is one file, it is easy to pass around, and this is where format updates matter most. If several people use the same database, try to keep them all on the same version of Base. Once one person opens the file in a newer version, it is moved up and the people still on an older version will see the refusal message.

For a club or a small office, a simple rule works: update everyone's Base at the same time, and let one person open the shared file first so its update and backup happen once, on purpose.

The Mac and Linux version

Base also runs on macOS and Linux and opens the same .obase files, so the same care applies there. A file updated on one system opens on the others, as long as each is running a Base new enough to read it.

Good habits around updates

Before updating Base, take a manual backup of any database you care about with File > Back up now, especially if you haven't opened it for a while. After updating, open each database once and check a form and a report. If all looks well, carry on as normal.

Keep the backup copies until you are sure. There is no rush to delete them, and Base already limits how many automatic copies it keeps.

These are small steps, and Base does most of the work. The point is that you can take each new version as it comes without worrying about the files you already rely on.