Adding Parentheses around a field name

[clrockwell15]

What I want to do is add Parentheses around a field name in my access report, e.g., ([Wife]) with [Wife] being the field name.

[kd2017]

You're going to need to elaborate further. A field name shouldn't have special characters such as parantheses. Is this just for display purposes? Can you show some screen shots?

[Welshgasman]

Just use & in the source to concatenate whatever you want?

[Micron]

If this is really about the label in the report then no problem at all - it should work if you just enter (Wife) as the label caption. If the field name is Wife and it contains the value "Wife" then the field probably has the wrong name.

[clrockwell15]

You're going to need to elaborate further. A field name shouldn't have special characters such as parantheses. Is this just for display purposes? Can you show some screen shots?

The Profile is about the size of a business card for each member. It has an image of the member in upper left corner. The first line has the members name which is input with the following: =Trim([Last] & ", " & [First] & " " & [MI])

The second line has the members' spouse name: [Wife] is the official field name. What I want to do is using the & and the ", put the Wife's name in Parentheses.

Below is the layout I want


John Doe
(Jane Doe) This is what I want to do in the report
Street address
Email ID
Occupation

[Welshgasman]

In the source?, as I have already stated.

[Micron]

So you're not trying to add () around a field name. You're trying to surround the field values.
If done in the report design I think you'd have to hide the [Wife] control and add a calculated one wherein the controlsource property would be
="(" & NameOfWifeControl & ")"

However, I think the better approach is to calculate (concatenate) in the query behind the report and bind Wife control to the calculated field, which is what WGM is saying (I think). If your report is based on a table, then change it to a query. IMO all forms and reports should be based on queries and not tables anyway. You might want to use IIF to calculate that so you don't end up with () where there is no spouse.

EDIT - If you set the textbox to 0 height and use CanGrow property, you might be able to avoid a blank line where there is no spouse. Can't recall if that property works in print preview. Or have (no spouse) if there isn't one and you don't want a blank line in any case.

[June7]

Your members are all heterosexual men?

[Micron]

Your members are all heterosexual men?

I'd expect to see such a question about sexual preferences and gender posted at AWF by certain members there, but not here.

[kd2017]

return (wife) only if the value isn't null or spaces.

=IIf(Trim([Wife] & "")="","","(" & [Wife] & ")")

[Welshgasman]

Your members are all heterosexual men?

Women have wives as well?

[June7]

Women have wives as well?

Maybe. Or they have husbands.

The field name [Wives] is sexist and implies the organization is as well (only male membership?) and maybe even homophobic.

[Welshgasman]

Maybe. Or they have husbands.

The field name [Wives] is sexist and implies the organization is as well (only male membership?) and maybe even homophobic.

Well I heard a woman say on TV, that she and her wife wanted to get a dog, so that is good enough for me.

[June7]

And some men refer to significant other as "husband". A gender neutral field name would be "Spouse" or "SigOther". Latter removes any scent of bias about gender, orientation, marital status. Shall we get into situation of multiple "SigOther" - any polygamists in the gallery?

[Micron]

return (wife) only if the value isn't null or spaces.

=IIf(Trim([Wife] & "")="","","(" & [Wife] & ")")

I suspect Trim should be in the False part as well, assuming it is needed at all.