RM, you may want to consider adding an AUTOSAVE feature to your software. Great software and 9.0 book.
Thanks, Rick.
RM, you may want to consider adding an AUTOSAVE feature to your software. Great software and 9.0 book.
Thanks, Rick.
Why? It already saves as you enter data.
Virtually all relational database programs save as changes to a record are made. Most also include a journaling feature so you can undo or rollback transactions to recover from entry errors. Unfortunately, RM does not have a rollback feature.
RM4 and up use the SQLite 3 database engine which has journaling for the duration of a transaction and will rollback to its beginning if disrupted. But a transaction might be an update of only a few fields of 1 record in 1 table lasting milliseconds. Journal file is deleted on successful completion of a transaction.
The RM software includes no Undo feature unlike other family tree apps which use the same database engine.
You are correct, my error
Good information, thanks
@TomH
You are a wealth of usefull information.
I would be happy to have just one allowed undo for the last transaction I performed. (messed up)
My mistake is realized after I push a button and see my unwanted result.
Instead of reloading a backup this (last action only) undo would be really handy. I find it interesting as you noted: βThe RM software includes no Undo feature unlike other family tree apps which use the same database engine.β