Family Historian User Group

I've just downloaded version 3.0.0 of AS and am having a problem loading my gedcom file. I go into File > Open GEDCOM File and locate my gedcom file. When I click on the file to load it, I get an unhandled exception message box with the following message:

'Unhandled exception…
Length cannot be less than zero.
Parameter name: length.'

If I click on Continue, the file doesn't load. If I click on Quit, AS closes without having loaded my gedcom file.



Can anyone offer me some guidance on this please? I've tried loading different gedcom files but all result in the same problem. I don't use FH projects, so am unable to see if they load OK.

I was using the old GEDCOM Census up until fairly recently. Then I replaced it with AS but never used it or did anything with it until I installed the latest update this morning. Initially, I was able to load my gedcom file but when I clicked on File > Current File is Default, I started getting the unhandled exception message. I closed all open applications prior to installing the update, and then did a reboot. No joy.

Thanks

Ed

ID:6017

I've recently had this issue reported and it will be fixed in the next update of Ancestral Sources (very easily fixed too). I think what you'll find to be the problem is that you've resized the screen so that the Repository title isn't showing. This issue didn't crop up in the recent beta testing for v3 and has only been reported by one other user so far because it really does need the main screen to be very narrow.

So make sure that where it says Repository: that you can see at least some of the text of ''. If the screen is resized or the main panel resized so that this repository name isn't shown then that error occurs.

Hope that makes sense and solves the problem.

Best wishes

Nick

P.S. Thanks for posting the error details which helped me to see the issue. I've taken the liberty of editing your post now to remove the error details (having made a note of them) to make this thread more readable for future reference by other users.

Thanks very much Nick, that's done the job.

The problem was, as you correctly identified, with resizing the panels. I'd been playing around with the layout prior to getting the error message. I can also replicate it by doing the same.

Thanks again.

Ed