* Last Occupation

[woods4thetrees]

Using FH 6, I have created a Standard Ancestor Chart and customised content in Diagram Options to show only Last Occupation. However, it appears to be showing first occupation instead. What am I doing wrong?! Thanks very much.

[tatewise]

First a little housekeeping to update your FH version in your Profile shown to the right of your posting.
Left-click your username woods4thetrees top right, choose Profile, and then Edit profile.
Select your Family Historian Version from drop-list, then scroll down to click Submit.

As usual it would help if you posted the Text Scheme item Template expression you are using.

See Diagram > Options > Text tab, Edit > Occupation > Edit

Every data ref should be using the special [last] index, whereas it sounds like it is using the [1] index.
e.g.
Occup: %INDI.OCCU[last]% %INDI.OCCU[last].DATE:COMPACT% in %INDI.OCCU[last].PLAC:TIDY%

Theoretically, that should be produced automatically if in the Edit Text Scheme dialogue you select Occupation from the left.
Then when added, the Add Item to Text Scheme dialogue Instance option should be set to Last.

[woods4thetrees]

Dear Mike,

Thank you so much for your reply. I have carried out the steps you posted.
The text template expression I am using is:
Occup: %INDI.OCCU[last]% %INDI.OCCU[last].DATE:COMPACT% in %INDI.OCCU[last].PLAC:TIDY%

I removed the Occupation line from the custom setting and replaced with a new Occupation line from the left of the Edit screen, making sure to select Last as the Instance. But it is still not picking up the last occupation.

Maybe I should run with it as is until I have populated the project a bit more to see exactly what it is doing!

Thanks again for all your help.

Steph

[tatewise]

Yes, that expression looks OK.

Does the problem apply to EVERY person in the Diagram or just a few? How many have you checked?

May be the Facts are not in chronological order, so the last Occupation fact is not always the one with the latest Date.
Do not be fooled by them being listed in Date order in the Property Box as that is not always the internal database order.
This problem will often arise if you have been entering a lot of new data that usually won't be in Date order, or if imported from another product.

Try using Tools > Re-order Out-of-Sequence Data to sort your database chronologically.

[woods4thetrees]

Thanks MIke,

I will give that a go and report back!

Thanks again & best,

Steph

[woods4thetrees]

Hi Mike,

Thanks for your advice.
That has done the trick. I imagine it was because I was entering alot of new data!

Best wishes,
Steph