VbProperCase Change

[wes9659]

I have created this After Update code to generate proper text formatting so when someone enters a name it capitalizes the first letter in each name. (i.e. jane smith it would be viewed as Jane Smith. Code does perfect for that; however when I add parentheses to show maiden name it throws it off. The current after update event code below leaves it as Jane (jones) Smith. I would like it to read Jane (Jones) Smith
This Is My Current Code:
Private Sub MothersNameMaiden_AfterUpdate()
MothersNameMaiden = StrConv(MothersNameMaiden, (vbProperCase)
End Sub

Thanks All For your help and consideration.

[June7]

I would not put maiden name in the same field. Name parts should be in separate fields anyway: FirstName, LastName, Middle

If you really want single field, then will probably need custom VBA function procedure.

[pbaldy]

And you have an extraneous parentheses. Take out the one in red:

MothersNameMaiden = StrConv(MothersNameMaiden, (vbProperCase)

[wes9659]

I agree with you June but in order for some things to eventually transfer I need it to read with maiden name on same line. It reverts back to how it appears on a death certificate. Do you know what VB code would look like to accomplish this task? As it stands now with current code even if I type it in as Jane (Jones) Smith it changes it to Jane (jones) Smith

Private Sub MothersNameMaiden_AfterUpdate()
MothersNameMaiden = StrConv(MothersNameMaiden, vbProperCase)
End Sub

[Missinglinq]

As I posted at the duplicate post located here

http://www.dbforums.com/microsoft-ac...sing-code.html

The problem, of course, is that Access is interpreting the opening parens as the first 'letter' and not the actual first letter of the maiden name. This does the job for me:

Private Sub MothersNameMaiden_AfterUpdate()

  Me.MothersNameMaiden = Replace(Me.MothersNameMaiden, "(", "( ")

  Me.MothersNameMaiden = StrConv(Me.MothersNameMaiden, vbProperCase)

  Me.MothersNameMaiden = Replace(Me.MothersNameMaiden, "( ", "(")

End Sub

Linq ;0)>

[June7]

I would store the data in separate fields then concatenate in query when needed. It is easier to combine fields than to manipulate strings. Linq's suggestion is very clever.

However, what do you want to do with something like: o'connor

[wes9659]

Private Sub MothersNameMaiden_AfterUpdate()

Me.MothersNameMaiden = Replace(Me.MothersNameMaiden, "(", "( ")

Me.MothersNameMaiden = StrConv(Me.MothersNameMaiden, vbProperCase)

Me.MothersNameMaiden = Replace(Me.MothersNameMaiden, "( ", "(")

End Sub


Works perfect!! Thank you I see now what you mean about code seeing ( as the first letter. Which then forced it to lower case.