Run Time Error
Posted: 28 Oct 2009 17:53
I am using Gedcom Census 6.0.6; FH 4.02; Win XP.
I have experienced a run time error referring to modal and non-modal issues on several occasions.
This has occurred when - while using Gedcom Census - I have entered data into FH (e.g. while using GedCom Census I have just come across a name which I had not previously included in FH) and returned to Gedcom Census.
I have found that the auto-updating of Gedcom Census by FH with the new name may not take place immediately and, if I have moved on to another stage (e.g. entering a place of birth if prompted) then the run time modal error is triggered by the auto-update of Gedcom Census with the name I have just entered in FH.
This then closes Gedcom Census and all the data I have entered for that Census is lost. I have to start again.
I understand what is happening but wonder of there is anyway of triggering the update of Gedcom Census (like a refresh mode) which will then force it to update with the new data rather than me having to wait for it or, as I am doing, moving on and experiencing the run time data loss.
ID:4107
I have experienced a run time error referring to modal and non-modal issues on several occasions.
This has occurred when - while using Gedcom Census - I have entered data into FH (e.g. while using GedCom Census I have just come across a name which I had not previously included in FH) and returned to Gedcom Census.
I have found that the auto-updating of Gedcom Census by FH with the new name may not take place immediately and, if I have moved on to another stage (e.g. entering a place of birth if prompted) then the run time modal error is triggered by the auto-update of Gedcom Census with the name I have just entered in FH.
This then closes Gedcom Census and all the data I have entered for that Census is lost. I have to start again.
I understand what is happening but wonder of there is anyway of triggering the update of Gedcom Census (like a refresh mode) which will then force it to update with the new data rather than me having to wait for it or, as I am doing, moving on and experiencing the run time data loss.
ID:4107