Family Historian User Group

I can't wait

tatewise wrote: ↑

01 Apr 2022 20:03

I can't wait

Hello Mike

Yesterday, I imported nine further Generations datasets into FH, comprising of tens of thousands of individuals.

After the usual use of plugins, I completely cleared all of my UDF lists, and I was left with a total of 27 stray notes, which I felt was a very acceptable outcome. I have resolved those by cutting and pasting the notes into their proper place.

Hence, it is all looking good, with a visual check of the datasets in Generations and FH the next step in the process.

Many thanks for all of your help in reaching this point.

Paul

There are a few more tidying up steps that can be usefully performed:

• Delete any unused records, such as Note records with no Links
• Review Cause of Death facts
• Fixing Dates and Date Phrases
• Check Project Statistics & Exceptions

tatewise wrote: ↑

26 Mar 2022 20:28

Since there have been no UDF associated with Source Citations I suspect you don't have that problem, so let us assume you can bypass that advice. That is not surprising since none of your screenshots has shown any evidence of any Source Citations at all.

Hi Mike

That's another skeleton in the cupboard of having used an obsolete program for so long. In turn, that has involved literally running two PCs side by side, one XP and no internet access for Generations, and a Windows 10 PC for everything else.

Most sources and citations are contained in a series of Excel workbooks on the latter !

Integrating the sources and the citations into FH will be another job once I am confident that all of the Generations data has been retrieved.

Thanks.

Paul

tatewise wrote: ↑

03 Apr 2022 13:15

There are a few more tidying up steps that can be usefully performed:

• Delete any unused records, such as Note records with no Links
• Review Cause of Death facts
• Fixing Dates and Date Phrases
• Check Project Statistics & Exceptions

Hi Mike

You produced a new plugin at 1 April 2022 at 14.12 :-

"The new Generations Fact Fixes plugin Version 0.1 Date 01 Apr 2022 is attached below".

To what extent does that deal with these points please ?

Thanks.

Paul

It does not deal with any of them.

I had assumed you had run Generations Fact Fixes on each imported dataset after using Change Any Fact Set.

It performs the following fixes all together in one run, so the two old plugins are redundant:

1. The Generations Attribute Values Fix plugin that copes with Attributes with 'yyyy - text' values and moves the yyyy to the Attribute fact Date, leaving the text as the Attribute value.
2. The Generations Attribute Notes Fix plugin that copes with Attributes with '@N123@' values and moves the Note record text to the Attribute fact local Note.
3. Copes with Events such as Probate with a local Note '@N123@' value and moves the Note record date text to the Event fact Date and the remainder of the Note record text to the Event fact local Note.

Those three types of Fix are listed in the Result Set after running the plugin.

tatewise wrote: ↑

03 Apr 2022 14:05

I had assumed you had run Generations Fact Fixes on each imported dataset after using Change Any Fact Set.

Hi Mike

Yes, I had run it at that point !

Thanks.

Paul

Assuming that fixed all the cases it is designed to fix we are now onto the four tidying up steps.

So the first step is to open the Records Window and in the Notes tab review the Links column.
Are they mostly if not all 0?

Use Edit > Find..., enter Search For: @N and ensure only these three are ticked: Fact Values, Notes, Match case
Does Find Now find anything?

If it does then there are some unresolved links to those Note records.

tatewise wrote: ↑

03 Apr 2022 14:53

Assuming that fixed all the cases it is designed to fix we are now onto the four tidying up steps.

So the first step is to open the Records Window and in the Notes tab review the Links column.
Are they mostly if not all 0?

Use Edit > Find..., enter Search For: @N and ensure only these three are ticked: Fact Values, Notes, Match case
Does Find Now find anything?

If it does then there are some unresolved links to those Note records.

Hi Mike

I have ended up with 27 notes spread over four datasets. They are entirely "0" in the Links column.

Searching as described for @N does not find anything at all.

What's next please ?

Many thanks.

Paul

The 0 Links means nothing is linked to them.
Since there are no @N anywhere, we have not overlooked any 'broken' links.
So those 27 Note records can be deleted, unless they contain anything you need to keep.
See FHUG Knowledge Base Delete One or Many Records for how to delete them.

tatewise wrote: ↑

03 Apr 2022 20:48

The 0 Links means nothing is linked to them.
Since there are no @N anywhere, we have not overlooked any 'broken' links.
So those 27 Note records can be deleted, unless they contain anything you need to keep.
See FHUG Knowledge Base Delete One or Many Records for how to delete them.

Good morning Mike

OK, I have completed that step.

What is next please ?

Many thanks.

Paul

Review Cause of Death facts.

Rather than having a separate Fact, conventionally the Cause of Death is recorded in the Death event in its Cause field.
If you only have a handful of Cause of Death facts then each text value can be manually moved to the Death event Cause field and the Cause of Death facts deleted.
If there are too many for that then I will write a Plugin to perform the text move and delete.

tatewise wrote: ↑

04 Apr 2022 10:25

Review Cause of Death facts.

Rather than having a separate Fact, conventionally the Cause of Death is recorded in the Death event in its Cause field.
If you only have a handful of Cause of Death facts then each text value can be manually moved to the Death event Cause field and the Cause of Death facts deleted.
If there are too many for that then I will write a Plugin to perform the text move and delete.

Hello Mike

I have got around two-hundred (200) Cause of Death facts, so a plugin would be very useful if you can produce one without too much trouble please. It would be quite onerous, albeit not impossible, to amend those manually, so a plugin would be a huge bonus.

Can you also please tell me what step three of the four tidying-up steps is please ?

Many thanks.

Paul

The remaining two steps are:

FHUG Knowledge Base Fixing Dates and Date Phrases which repairs malformed Date fields in Facts.
Just run the Find Date Phrases plugin, and the Fix Date Fields plugin, then review what is still malformed if anything.

FHUG Knowledge Base Check Project Statistics & Exceptions which looks for inconsistent or incomplete data.
Run both the All Empty Facts Query, and the Show Project Statistics plugin, then review outstanding issues.

tatewise wrote: ↑

04 Apr 2022 17:44

The remaining two steps are:

FHUG Knowledge Base Fixing Dates and Date Phrases which repairs malformed Date fields in Facts.
Just run the Find Date Phrases plugin, and the Fix Date Fields plugin, then review what is still malformed if anything.

FHUG Knowledge Base Check Project Statistics & Exceptions which looks for inconsistent or incomplete data.
Run both the All Empty Facts Query, and the Show Project Statistics plugin, then review outstanding issues.

Hi Mike

That's great, plenty to get on with, I'll post as and when I hit problems !

Thanks.

Paul

Paul Wigan wrote: ↑

04 Apr 2022 17:33

tatewise wrote: ↑

04 Apr 2022 10:25

Review Cause of Death facts.

Rather than having a separate Fact, conventionally the Cause of Death is recorded in the Death event in its Cause field.
If you only have a handful of Cause of Death facts then each text value can be manually moved to the Death event Cause field and the Cause of Death facts deleted.
If there are too many for that then I will write a Plugin to perform the text move and delete.

Hello Mike

I have got around two-hundred (200) Cause of Death facts, so a plugin would be very useful if you can produce one without too much trouble please. It would be quite onerous, albeit not impossible, to amend those manually, so a plugin would be a huge bonus.

Can you also please tell me what step three of the four tidying-up steps is please ?

Many thanks.

Paul

Hello Mike

Have you decided whether or not you will be writing a plugin to deal with this Cause of Death fact issue ?

There's no rush, but if you could confirm your intentions please, I will know whether or not to start correcting them manually.

Many thanks.

Paul

To be honest, I was expecting feedback & questions for Fixing Dates and Date Phrases and Check Project Statistics & Exceptions, so did not want to muddy the waters with the plugin for Cause of Death.

I have added the Cause of Death conversion to the Generations Fact Fixes plugin Version 0.2 Date 09 Apr 2022 attached.

So it still performs all the corrections it did before and now also corrects the Cause of Death fact.
( The other corrections should do nothing since they have already been fixed. )
It relies on your FH custom attribute being called literally "Cause of death" and that there exists a Death Event for each person to receive the Cause of death reason.
If your custom attribute has a different name, or the Death Event may be missing for some people and you would like the Plugin to create such Death Events, then it will need a change.

tatewise wrote: ↑

09 Apr 2022 21:03

To be honest, I was expecting feedback & questions for Fixing Dates and Date Phrases and Check Project Statistics & Exceptions, so did not want to muddy the waters with the plugin for Cause of Death.

I have added the Cause of Death conversion to the Generations Fact Fixes plugin Version 0.2 Date 09 Apr 2022 attached.

So it still performs all the corrections it did before and now also corrects the Cause of Death fact.
( The other corrections should do nothing since they have already been fixed. )
It relies on your FH custom attribute being called literally "Cause of death" and that there exists a Death Event for each person to receive the Cause of death reason.
If your custom attribute has a different name, or the Death Event may be missing for some people and you would like the Plugin to create such Death Events, then it will need a change.

Hello Mike

Thanks for that plugin - feedback to follow once I've used it a couple of times.

As far as the other plugins are concerned, Fixing Dates and Date Phrases appears to have worked OK, whilst I haven't really tested Check Project Statistics and Exceptions. I have started off with my very smallest datasets, and these plugins will come into their own as I move into my larger datasets. But I do have one Cause of Death on a very small dataset that I have been working on today, so I will test the latest plugin on that.

One interesting feature of the work that I have done so far is how FH treats ampersands (&). Within the Notes tab on Generations, I might have :-

Occupation : 1881 and 1891 Coal Miner

Occupation : 1881 to 1891 Coal Miner

Occupation : 1881 - 1891 Coal Miner

Those would all import into FH without a problem. However, I might have :-

Occupation : 1881 & 1891 Coal Miner

The latter would import as :-

Occupation : 1891 Coal Miner

Hence, the ampersand and the text to the left of it would be lost.

I have dealt with this by creating a working copy of my Gedcom ; doing a Find and Replace therein to replace the ampersands with the word and ; and then re-importing the amended file into FH.

Thanks again for the plugin and I'll keep you informed of progress.

Best wishes.

Paul

That problem with importing & is unexpected.
Please post a sample snippet of Generations GEDCOM as exported from Generations and used as import to FH after the Generations Pre-Load Source Clean plugin showing the Occupation : 1881 & 1891 Coal Miner text.

tatewise wrote: ↑

11 Apr 2022 16:24

That problem with importing & is unexpected.
Please post a sample snippet of Generations GEDCOM as exported from Generations and used as import to FH after the Generations Pre-Load Source Clean plugin showing the Occupation : 1881 & 1891 Coal Miner text.

Hi Mike

"Coal Miner" was an example - it is actually "Coachmaker".

Original Gedcom :-

1 ADDR William Banfield Gallway FRIFT
2 CONT (1841) - Manuden Street
2 CONT Manuden
2 CONT Essex
1 BIRT
2 DATE 1817
2 PLAC Falmouth Cornwall
1 BAPM
2 DATE 15 JUN 1817
2 PLAC Falmouth Cornwall
1 DEAT
2 DATE 12 JAN 1873
2 PLAC Brentford Middlesex District
1 RESI
2 DATE 1851
2 PLAC 12 Villiers Street St Martin in the Fields Westminster Middlesex
1 RESI
2 DATE 1861
2 PLAC Harrow Heath Middlesex
1 RESI
2 DATE 1862 & 1865
2 PLAC Grove Hill Cottages Grove Hill Lane Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1866 & 1867
2 PLAC Grove Hill Cottages Grove Hill Lane Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1869 & 1870
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1871
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1871
2 PLAC Lowland's Road Grove Cottage Harrow Middlesex
1 RESI
2 DATE 1872
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1873
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
1 RESI
2 DATE 1873
2 PLAC 7 South Street Isleworth
2 NOTE Place of death
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright
1 NOTE @N6@
1 PROB @N10@
1 FAMC @F2@
1 CHAN
2 DATE 15 DEC 2012
0 @I8@ INDI

Pre-Load Source Clean Gedcom :-

1 NAME William Banfield Gallway /FRIFT/
1 SEX M
1 BIRT
2 DATE 1817
2 PLAC Falmouth Cornwall
1 BAPM
2 DATE 15 JUN 1817
2 PLAC Falmouth Cornwall
1 OCCU Coach Maker
2 DATE 1841
1 RESI
2 DATE 1851
2 PLAC 12 Villiers Street St Martin in the Fields Westminster Middlesex
1 OCCU Coachbody Maker
2 DATE 1851
1 RESI
2 DATE 1861
2 PLAC Harrow Heath Middlesex
1 RESI
2 DATE (1862 & 1865)
2 PLAC Grove Hill Cottages Grove Hill Lane Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE (1866 & 1867)
2 PLAC Grove Hill Cottages Grove Hill Lane Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE (1869 & 1870)
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 OCCU Coachmaker
2 DATE 1861
1 RESI
2 DATE 1871
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1871
2 PLAC Lowland's Road Grove Cottage Harrow Middlesex
1 OCCU Coachbody Maker
2 DATE 1871
1 RESI
2 DATE 1872
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1873
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
1 RESI
2 DATE 1873
2 PLAC 7 South Street Isleworth
2 NOTE Place of death
1 OCCU Coachmaker
2 DATE 1873
1 OCCU Wheelwright
2 DATE 1873
1 RESI
2 NOTE William Banfield Gallway FRIFT (1841) - Manuden Street Manuden Essex
1 DEAT
2 DATE 12 JAN 1873
2 PLAC Brentford Middlesex District
1 PROB
2 DATE 27 FEB 1873
2 NOTE Administration of the effects of William BanfieldGallway Frift was granted to George Love Frift. Brother and oneof the next of kin.Effects under £1,000
1 FAMC @F2@
1 NOTE 1841 - living with the Moss family
1 CHAN
2 DATE 10 APR 2022
3 TIME 11:49:30
0 @I8@ INDI

As I mentioned, I have sorted this out manually in this dataset. But if I have done anything wrong or if an updated plugin is the outcome, please let me know as I am now graduating onto progressively larger datasets.

Please let me know if there is anything else you need.

Many thanks.

Paul

I'm confused (again)!

Your relevant snippets show:

Original Gedcom :-
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright

Pre-Load Source Clean Gedcom (showing just the OCCU facts derived from above) :-
1 OCCU Coach Maker
2 DATE 1841
1 OCCU Coachbody Maker
2 DATE 1851
1 OCCU Coachmaker
2 DATE 1861
1 OCCU Coachbody Maker
2 DATE 1871
1 OCCU Coachmaker
2 DATE 1873
1 OCCU Wheelwright
2 DATE 1873

Surprisingly, that has perfectly created an Occupation for each Date in the original Gedcom.
(Are you sure you posted the correct Gedcom?)
My experiments suggest that the Generations Pre-Load Source Clean plugin makes no such changes.
I wonder if you've posted the current Project Gedcom after importing, running corrective plugins, and manual edits?

You complained that
Occupation: 1881 & 1891 Coal Miner

would import as only one fact and discard the '& 1891' data:-
Occupation: 1891 Coal Miner

Notice that your 'problem' description 'Occupation : 1881 & 1891 Coal Miner' has no hyphen (-) between years and occupation, whereas the original Gedcom snippet does have hyphens!

So your description of the problem does not agree with your posted snippets. Do you see my dilemma?

After some more experiments, this is what I found.
The original post-Generations Pre-Load Source Clean plugin Gedcom imports into FH Project as:-
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright

After running the Generations Fact Fixes plugin those become:
1 OCCU Coach Maker
2 DATE 1841
1 OCCU Coachbody Maker
2 DATE 1871
1 OCCU Coachmaker
2 DATE 1873
1 OCCU Wheelwright
2 DATE 1873
i.e. the years 1851 and 1861 have been omitted by my plugin because it does not expect two years before the hyphen.
You never mentioned that was a possibility, so I will need to amend the plugin to cope with that format.

Most of your earlier examples have no hyphen (-) at all, so will be completely unaffected by the import & plugins.
Occupation : 1881 and 1891 Coal Miner
Occupation : 1881 to 1891 Coal Miner
Occupation : 1881 & 1891 Coal Miner

So I can find no consistency between your stated '&' problem, the posted Gedcom snippets, and my experiments.

tatewise wrote: ↑

13 Apr 2022 19:54

I'm confused (again)!

Your relevant snippets show:

Original Gedcom :-
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright

Pre-Load Source Clean Gedcom (showing just the OCCU facts derived from above) :-
1 OCCU Coach Maker
2 DATE 1841
1 OCCU Coachbody Maker
2 DATE 1851
1 OCCU Coachmaker
2 DATE 1861
1 OCCU Coachbody Maker
2 DATE 1871
1 OCCU Coachmaker
2 DATE 1873
1 OCCU Wheelwright
2 DATE 1873

Surprisingly, that has perfectly created an Occupation for each Date in the original Gedcom.
(Are you sure you posted the correct Gedcom?)
My experiments suggest that the Generations Pre-Load Source Clean plugin makes no such changes.
I wonder if you've posted the current Project Gedcom after importing, running corrective plugins, and manual edits?

You complained that
Occupation: 1881 & 1891 Coal Miner

would import as only one fact and discard the '& 1891' data:-
Occupation: 1891 Coal Miner

Notice that your 'problem' description 'Occupation : 1881 & 1891 Coal Miner' has no hyphen (-) between years and occupation, whereas the original Gedcom snippet does have hyphens!

So your description of the problem does not agree with your posted snippets. Do you see my dilemma?

After some more experiments, this is what I found.
The original post-Generations Pre-Load Source Clean plugin Gedcom imports into FH Project as:-
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright

After running the Generations Fact Fixes plugin those become:
1 OCCU Coach Maker
2 DATE 1841
1 OCCU Coachbody Maker
2 DATE 1871
1 OCCU Coachmaker
2 DATE 1873
1 OCCU Wheelwright
2 DATE 1873
i.e. the years 1851 and 1861 have been omitted by my plugin because it does not expect two years before the hyphen.
You never mentioned that was a possibility, so I will need to amend the plugin to cope with that format.

Most of your earlier examples have no hyphen (-) at all, so will be completely unaffected by the import & plugins.
Occupation : 1881 and 1891 Coal Miner
Occupation : 1881 to 1891 Coal Miner
Occupation : 1881 & 1891 Coal Miner

So I can find no consistency between your stated '&' problem, the posted Gedcom snippets, and my experiments.

Hi Mike and thanks for the reply.

I am certain that the original Gedcom is the correct file ; as for the Pre-Load Source Clean file, I will address this on Saturday morning.

Best wishes.

Paul

Hi Mike

I am fairly sure that this is the Pre-Load Source Clean file that you require.

Thanks.

Paul

1 NAME William Banfield Gallway /FRIFT/
1 SEX M
1 ADDR William Banfield Gallway FRIFT
2 CONT (1841) - Manuden Street
2 CONT Manuden
2 CONT Essex
1 BIRT
2 DATE 1817
2 PLAC Falmouth Cornwall
1 BAPM
2 DATE 15 JUN 1817
2 PLAC Falmouth Cornwall
1 DEAT
2 DATE 12 JAN 1873
2 PLAC Brentford Middlesex District
1 RESI
2 DATE 1851
2 PLAC 12 Villiers Street St Martin in the Fields Westminster Middlesex
1 RESI
2 DATE 1861
2 PLAC Harrow Heath Middlesex
1 RESI
2 DATE 1862 & 1865
2 PLAC Grove Hill Cottages Grove Hill Lane Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1866 & 1867
2 PLAC Grove Hill Cottages Grove Hill Lane Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1869 & 1870
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1871
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1871
2 PLAC Lowland's Road Grove Cottage Harrow Middlesex
1 RESI
2 DATE 1872
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
2 NOTE Freehold cottages and land
1 RESI
2 DATE 1873
2 PLAC Grove Hill Cottage Harrow on the Hill Middlesex
1 RESI
2 DATE 1873
2 PLAC 7 South Street Isleworth
2 NOTE Place of death
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright
1 NOTE @N6@
1 PROB @N10@
1 FAMC @F2@
1 CHAN
2 DATE 15 DEC 2012
0 @I8@ INDI

That looks the same as what you posted Wednesday and suffers all the same inconsistencies with your problem description.

The only relevant facts are:
1 OCCU 1841 - Coach Maker
1 OCCU 1851 & 1871 - Coachbody Maker
1 OCCU 1861 & 1873 - Coachmaker
1 OCCU 1873 - Wheelwright

As far as I can tell, they import to FH unadulterated as follows (which disagrees with your problem description):
Occupation: 1841 - Coach Maker
Occupation: 1851 & 1871 - Coachbody Maker
Occupation: 1861 & 1873 - Coachmaker
Occupation: 1873 - Wheelwright

None of those match your Sunday problem facts that have no hyphens ( - ) between the years and the job name:
Occupation: 1881 and 1891 Coal Miner
Occupation: 1881 to 1891 Coal Miner
Occupation: 1881 - 1891 Coal Miner
Occupation: 1881 & 1891 Coal Miner

You say that last fact imports as Occupation: 1891 Coal Miner discarding the lefthand year, but the others are unaltered.

I cannot reproduce that import to FH problem description. Until I have a GEDCOM that exhibits your problem I'm stuck.

What I have found is that my Generations Fact Fixes Plugin when faced with double years such as:
Occupation: 1881 and 1891 - Coal Miner
Occupation: 1881 to 1891 - Coal Miner
Occupation: 1881 & 1891 - Coal Miner
Occupation: 1851 & 1871 - Coachbody Maker
Occupation: 1861 & 1873 - Coachmaker
converts them all to an Occupation fact with only the righthand year as a Date and discards the lefthand year.
i.e.
Occupation: Coal Miner Date: 1891
Occupation: Coal Miner Date: 1891
Occupation: Coal Miner Date: 1891
Occupation: Coachbody Maker Date: 1871
Occupation: Coachmaker Date: 1873

My impression is that you are confusing importing to FH with running my Plugin, and you are omitting hyphens.
Untill the entire process and the symptoms you describe are repeatable no solution can be devised.

tatewise wrote: ↑

15 Apr 2022 20:06

Untill the entire process and the symptoms you describe are repeatable no solution can be devised.

Hi Mike

Let's put this problem to one side for the moment. There were only the handful of instances of the problem in the dataset, so I have amended those manually.

I have now moved on to checking far larger datasets, and have created a template to document the exporting and importing process, when files were created, in what location they are stored and the like.

I should be able to give a far better chronological description of the problem next time I encounter it. In turn, that should facilitate a smoother analysis from your viewpoint.

Have a good Easter Sunday.

Thanks.

Paul