Then I bow deeply to your suggestions, and accept the simplest and most concrete route for data validfation:
I shall build an update query to obtain the data from the [addr1] field, and macro it to update the uppercase information in the Label_1 field as is needed.
I thank both of you...
Where/how would I build this query into the table itself so that it automatically updates the [Label_1] record when the input is done on the [Addr1] field?
ie: Input to form in textbox 'addr1': automatically updates [Label_1]
??
Thanks, man.
Hi Duane: Thanks again for your input.
OK: let's start this again.
I don't want to convert to a report, a query, or other. I would like a stored uppercase copy of the [Addr1] as another column in the SAME TABLE as is the column [Addr1], but named [LABEL_1].
Clean and simple, and this is...
Hi Duane. It needs to be stored in CAPS for an export and data-merge at my printers, and in a different column than the original text. Setting the Format to > displys it in CAPS but does not print it in Caps. Again: the column itself must be converted to caps, based on the other column. Thanks...
Hi Duane: Thanks for the response. This is the structure and formula that I have used before " =UCase([Addr1]) ".
I tried it in the Validation field of the record properties. It came back with error "invalid SQL syntax-cannot use multiple column-level CHECK constraint".
I tried various...
This should be a simple enough thing, but I can't get it to work: I have an area input on a form that goes in in mixed-case (caps and lower). This is an address line. I need to convert it to an upper-case format in another field, for mailings, and I want to use the same table.
This is on Access...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.