Question Validation Rules

[dillon_gator]

I need a validation rule to convert data entered to the ProperCase no matter how it is entered. I've tried all sorts of things, but nothing is working yet. Thanks, momalynda

 

[boblarson]

Validation rules don't do conversion. They only stop people from putting incorrect data in. Data should not be accessed at the table level, so if you have a form for input then you can format the data the way you want in the Before Update event of the form.

 

[dillon_gator]

Thanks, Bob, I'm sure it's obvious I'm a real novice. I took classes a couple of years ago, set up a database with forms but have been doing the data entry all myself. Now I want to turn it over to someone else. Basically, all I want to do is make sure the text in some fields is entered in Proper Case. To use BeforeUpdate condition, it appears I need to create a macro. I have played with it since your last post, but again am getting nowhere. I'm not sure what should be my condition, action and argument. Basically I want to say, if [FieldName] is not in [ProperCase], do not update and display some little message to remind the data entry person it should be in proper case.

 

[boblarson]

You would use (this is VBA code and goes in the VBA window - let me know if you don't know how to get there).

Me.YourTextBoxName = StrConv(Me.YourTextBoxName, 3)

 

[Kryst51]

Basically I want to say, if [FieldName] is not in [ProperCase], do not update and display some little message to remind the data entry person it should be in proper case.

Could an input mask achieve what you want?

 

[boblarson]

Could an input mask achieve what you want?

Nope, an input mask is not the way to go. Your example shows the limitation of such a mask.

 

[Kryst51]

Nope, an input mask is not the way to go. Your example shows the limitation of such a mask.

How so? Actually just popped into my head, is it because you have to define how many characters are entered?

Edit: Sorry dillon for the wrong idea.

 

[boblarson]

How so? Actually just popped into my head, is it because you have to define how many characters are entered?

Yep, and how do you know where to put the > for each word?

Input masks are not very friendly, nor are they really that great for doing things that are "unknown" at the time (in this case how long the text will be, how many words, etc.).

 

[DCrake]

Why is it so critical for the user to type in the words in proper case? Why not let Access do for you.

David