I have an embedded database in which counsellors record their client data. Each counsellor has their own version of the base file. If/when I modify the front end, I must upgrade each user’s version, while preserving their individual data. Perhaps this would be better achieved in a split database - advice welcome. How simple is it in each case to copy the old tables into a fresh version of the base file?
Ubuntu 16.04, LO 6.3.0.4 (with firebird)
Hello,
All the data for Firebird is is one file within the .odb.
Open the .odb with an archive manager - may need to change extension to .zip.
Double click on database folder
File is firebird.fbk - can copy & paste into different .odb
Remember - always have a backup copy before performing operations where something can go wrong.
Another option to consider - using Base with a connection to a Firebird File. Here the data is external to the .odb but now when changing the front end you would need to change the connection string back to where the the external Firebird file is located.
Hard to say which is the method to use. Have done both and also a portable split - see → How can I create a portable split embedded/local firebird database in the manner that is done with HSQLDB?
Thanks, as always, Ratslinger. The .fbk is just what I needed.