To explain a little more
had only 1–let me repeat that ONLY 1 error with RM 8 UNTIL update RM 8.2.7.0– – then I had multiple types of errors with no idea why or how they were happening as they happened randomly…
There were many access violations and argument out of range as well as there was what I will call the phantom white page which @fahumm does an excellent job of explaining --which seems to have been happening since the testing of RM 8…
By the time RM 8.5.0.0 and RM 9 came along, it improved—meaning it took longer for a error to occur BUT they still occur a lot…
If you do a SEARCH in the box at the top of this page for Argument out of Range-- you will see there are 11 different Topics on here
If you do a search for Access Violations-- you will see there are over 50 different topics on here.
.I read thru all of them as they appeared on the list
and almost all seem to have a common factor-- AND THAT IS EDITING ( or deleting as in my case)-- to me editing means changing or deleting something BUT that may NOT be what others are talking abt…
Treeshare seems to have problems ( and therefore FamilySearch probably does too) - probably due to the many clicks it takes just to accept one change…
Other things listed in these posts were editing NOTES, editing FACTS, editing MEDIA, editing PLACES and editing CITATIONS-- WHICH REALLY SEEMS TO BE A BIG ONE! Except for one ( which was FS and citations), none of these violations seem to occur when just adding new info.
So is it the fact that we are making changes to the existing program or does it all boil down to that once you hit X amount of clicks ( 670-1000) while making changes to the file in one session, the error is going to occur?
Can’t speak for MAC users BUT believe anyone on Windows can repeat the error I listed in the first post above–to make it easier, you MIGHT install a mouse clicker but then you might not want to do that as you might be amazed by how many clicks it takes to get something done.
@rzamor1 would you please share this with the tech support working on my support ticket-- thanks