My next step is to try it on a PC with windows 10 to see if that clears up the issue.
For the time being I will address the issue of research trips some other way. I can have access to a windows laptop and can run RM TO GO that might solve the issue of access to data but not the issue of a website from RM.
Now I am very curious to find out just what has changed even if I have workarounds.
I just ran a test and it is correct that RM on re-import the description field is going into the note and it is also truncated. I thought I had tested that but it looks like the long desc field is not put back into the description field.
Legacyfamilytree 8 does put the extended data into the description field. Familytreemaker 2014 also retains the full description in the description field.
I was wondering if I was the only one interested in this. It appears that the description field has been thought of by several others.
This being a wish list is this something that it would be nice for RM to consider or would I be the only one desiring this change?
I think that some parts of this would be very doable but there are ramifications like the GEDCOM standard and this affecting many other functions within RM. If there are enough users that would use this then it would make sense for RM to at least analyze the impact of this type of change.
Coming from TMG we had so more options for sentence variables and I would welcome a note variable.
It would be interesting to understand how RM uses the SQLite locking mechanism. SQLite is embedded in the RM application and according to the SQLite documentation there is a "pager module" that handles the locking of the database. If you are running all the applications on the same PC then maybe there is only one copy of the pager module running and that all requests are funneled through the single SQLite module.
I tried to open two instance of RM and was unable to do so. I did open several copies of the same database within the same instance of RM. RM would only allow one to open a screen where updating might take place thus enforcing the single threaded approach.
It will be interesting to see what RM does, if anything, on concurrent database access. I don't think I will have need for concurrent access, I have enough trouble just managing me.