GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 
Error saving a .gno file on Dropbox


https://support.genopro.com/Topic40522.aspx
Print Topic | Close Window

By Jarmo - Saturday, May 30, 2020
Hello

I'm using version 3.1.0.0.  When I "Save" my gno-file (Saksi.gno) I'll get following error msg:



Two days ago I was able to "Save" normally with this same program version.  As far as I can understand I haven't changed anything in my computer.
Does somebody have an idea why this error?
I'm able to "Save as..." with a new name, but that is not what I want.

BR, Jarmo
By Jarmo - Sunday, May 31, 2020
Hello
I uncecked "Tools / Options / Create temporary backups when saving .gno files" and after that "Save" seems to work as expected
without error msg.  Problem solved!
BR, Jarmo
By GenoProSupport - Sunday, May 31, 2020
Good observation.  There is a potential danger however: if you save and there is a power failure or a crash, you may lose your original .gno file.

GenoPro saves its .gno file as follows:
1. Create a temporary file and save the family tree.
2. When the family tree is fully saved, then in erases the original .gno file.
3. GenoPro renames the temporary file to the original .gno file.

This way, if at any point there is a problem, there is a full copy of the family tree.  With the option to disable temporary backups, GenoPro does the following:
1. Erase the original file.
2. Save the family tree with the same file name as the original file.

If anything goes wrong in step #2, then the original file is lost.
By Jarmo - Monday, June 1, 2020
Hello

Thanks for your comments and guidance.

I would use, with pleasure,  "Tools / Options / Create temporary backups when saving .gno files" checked, but then I'm not able to save my file at all (without using "Save as..." command and giving a different filename) and I'll get the error msg I displayed in my previous message.

Is there something else I should do in order to avoid this error msg?

BR, Jarmo
By genome - Monday, June 1, 2020
This would appear to be a Dropbox issue see https://www.dropboxforum.com/t5/Dropbox-files-folders/Access-violation-error-on-xsl-table/td-p/382919/page/2

Maybe they will fix it one day🤔 

A workaround is to pause Dropbox sync, save your. Gno, then resume Dropbox sync. Another is to save as online backup to Genopro server instead.