I have created a query but I have three questions - if anyone can help!
Question 1 - Is there any way in which you can specify that text 'wraps' in a column? By this I mean that if the text is too long (as with a note) to fit in the space can it be made to go onto two lines?
Question 2 - Can a column be conditional? I have a column for a spouse but I only want this to show if the person is female.
Question 3 - Can you have a person appearing twice? By this i mean that if there are two of the same attributes for the person can they appear on two lines? I know that I can have them appear across the page but I want to have then down the page.
I have a strong suspicion that the answer to all three questions will be no - but I just thought that I would ask anyway.[lol]
ID:696
* Queries (again)
-
Jane
- Site Admin
- Posts: 8441
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Queries (again)
Two no's and a yes (sort of)
To only get the spouse surname where the person is female you can say
INDI.FAMS[1]>HUSB>NAME[1]:SURNAME
Then the column will always show the first marriages Husbands name so the man will have his surname in the column.
You can also say
INDI.FAMS[HUSB>NAME[1]:SURNAME
This will return the last known Husbands surname.
There is a wish list item to allow queries by events, but last time I looked few people had voted for it.
One way around the notes problem is to create a custom report rather than a query. This also handles the multiple events. Just base it on the Census Report so you get the idea.
To only get the spouse surname where the person is female you can say
INDI.FAMS[1]>HUSB>NAME[1]:SURNAME
Then the column will always show the first marriages Husbands name so the man will have his surname in the column.
You can also say
INDI.FAMS[HUSB>NAME[1]:SURNAME
This will return the last known Husbands surname.
There is a wish list item to allow queries by events, but last time I looked few people had voted for it.
One way around the notes problem is to create a custom report rather than a query. This also handles the multiple events. Just base it on the Census Report so you get the idea.