Family Historian User Group

I read the OP as referring to these dates:

Yes, 7.6.6 64 bit. Windows 10 Pro 64 bit - fully up to date - version 22H2, OS build 19045.2364. Windows Feature Experience Pack 120.2212.4190.0 I've tried it on the Sample project and it happens on there. I just selected the first census record, highlighted a couple of cells and hit CTRL+C. I can't...

Seems to be easily reproducible. All my sources are rich text and I was working through converting to make the individual links - I'm not sure if this is significant. I went back to a fully converted and linked source. It happens if complete cells are selected in the top grid and you then hit CTRL+C...

When editing details in the top grid, attempting to use CTRL+C instead of the buttons throws an exception.
Error details have been noted and subsequently removed by Nick Walker

If I add a female witness to a marriage who is an individual in file and the witness was married at the time of the wedding, should it insert their married name in the auto text? I can edit it, but I wondered if this was something it ought to do.

I use the File Description in the Header record to have a brief description of each project and have then modified the caption of all the property boxes to add " (%CUR_FILE_HEADER.NOTE2%)" to make it visible as much as possible.

OK. I'll apply the change to the new version myself before I use it when you let it loose.

I've done a number of syncs to two different RM databases with that change without seeing any consequences.

Will you be including the modification I suggested here?

viewtopic.php?p=129088#p129088

Odd! I'm using it with living individuals included without any issue.

I'd suggest it's not including living that is the issue, but something specific on one of the living individuals

Immediately after reading this topic I go to a 1921 census and find this:
According to the transcription it reads "Both Parents Alive"

but then I haven't really made use of them in family tree yet. Nor had I until recently. I had a male where I was trying to find his wife and had two candidates. Finding him with his wife in a 1948 electoral register gave me her given names and determined which one of the two was the wife which was...

I've just tried this and it's giving spurious errors. I've used Ancestral Sources to enter details from a 1948 electoral register which AS does using a census fact. FTA is saying 1948 isn't a supported census date.

I know that. I was referring to how Little.auk was reading the csv files created by saving queries. It would be very difficult (impossible?) to write a driver to allow updating GEDCOM files, but I wonder if it would be possible to create one that gave limited read only access? You'd have to have a w...

Excel can link to any column structured file for which you can define an ODBC link - CSV files are just a simple example. Most (all?) databases have ODBC drivers.

No, because if I am looking at 1C2R at some time in the future when I've forgotten all this, what is there to prompt me to look at the research note for the three possible descendants?

So without being able to verify the suggestion that Thrulines is presenting, how can you assert that the 2nd GGF is the MRCA between the two individuals? I agree with that. Even if I knew who OT and the other two linking individuals were it doesn't prove the 2xGGF is right. It only proves GGM and G...

I create the individual OT using whatever Information I can glean from Ancestry. Would you also create the intermediate 2C1R and 3C individuals to keep the relationships correct? In view of the previous comments I'm thinking of modifying this: I'm using two flags to put icons on diagrams, one flag ...

I am generally selective in recording DNA matches anyway. I don't investigate or record every match that crops up, seeking mainly to record just those that corroborate (or disprove) my paper based and other research. That is my main motive as well, proving the ancestors. If as a result I find more ...

I have a rule of thumb - I trust people to know their own grandparents, but beyond that... And in this case, the 1C2R is OT's G-GF - one step beyond. I can relate to that. Yesterday I was puzzling over another match for some time. It should have been fairly easy as it suggested a 2nd or 3rd cousin....

Adrian, I posted again while you were composing your reply. I am aware of the errors that others may make and seek to validate the connections suggested by other research (GRO, parish and census records). Is my conclusion that there is somebody who connects via the names in both our trees which vali...

What I should have added is that looking at the non-private parts of their tree they have the Great-grandaunt and 1st cousin 2x removed. Doesn't that mean that those two are validated as DNA related to me? I'm using two flags to put icons on diagrams, one flag and icon for people that are DNA matche...

I'd appreciate some thoughts on an issue I have: . Ancestry ThruLines.png All the red obscured names are individuals I already have in my project. I'm recording matches using a small modification of Jane's method with this note template on the DNAMatch fact: [[ Tested with: Name on Test Site: GedMat...

Thanks, that does the trick. I'd already reached the conclusion that, considering what the object of the query is, using EARLIEST and LATEST would be better. I've also increased the generations on the estimated functions to 5. For anybody following this my row filters are: Exclude if =EstimatedDeath...

Sorry I didn't express the issue correctly. The original I was referring to was this: There is a CensusMissingAges query downloadable from the knowledgebase, which I have modified and which gives a result similar to what you're after. For each census year, it gives the following entries for each ind...

Interesting! Why do you choose to use only explicit Birth Dates instead of Estimated, but do use Estimated Death Dates? Have you considered the following more compact function instead of the nested TextIf(...) function: CombineText( , %INDI.CENS[year=1841].AGE%, , " find " ) Also, by using DateAt(1...