I just upgraded my computer to Win 11. Although the RM installer was moved from the old to the new computer, it wants to install the 32 bit version. If I want to install the 64 bit version, can I just download and run the 64-bit installer and use the key I got when I purchased RM10?
Yes, the key works for both versions.
Thanks, Bob. I thought it might, but wanted to check with the online expersts before I pulled the trigger.
Phil
Keep in mind I do not believe that database created or update by the 64 bit version is able to be opened in the 32bit
I didn’t have any problems opening a database created/ updated by the 64 bit version in the 32 bit version on Windows–can’t say abt a MAC…
Haven’t tried that
Maybe someone can comment on that
That is incorrect! The database is the database regardless of the OS bit rate. There is apparently some difference involved when opening a DB create in Windows on a Mac or vice versa if I recall what I read here.
so you can switch back and forth 32 bit program vs 64 bit program without issue?
Yes I agree database is database.
That would seem to be about what i said, yes.
It does not matter what OS a SQLite database is created in. As long as the file format can be opened in another OS, it can be used by SQLite on that system.
The published differences for RM are:
- Legacy Family Tree database files cannot be imported by 64-bit RM because the Legacy code required to interpret the data cannot be included in the 64-bit applications for either Windows or Mac, only in the 32-bit Windows app. That has nothing to do with SQLite and may be the only reason there still is a 32-bit version.
- The incompatibility between 64-bit Windows and Mac shareable drives or RM2Go must be at the OS level. If the other OS can see the .RM tree file, its RM can open it.
- There is a difference between Mac and Windows in the custom collation sequence created by RM that affects indexes (sorting and searching) for names of people, places et al. A database created on one fails the Integrity Check on the other but is easily resolved by the Rebuild Indexes database tool.
Thank you Tom for providing an detailed explanation