formating text in a table design

[Guest]

what does > mean?

Thanks.

 

[Guest]

Hi Nancy

Not really sure what your question is but if you are asking what > will do
to text when used in an Input Mask - it will make the text after the > upper
case

so if you enter wayne-i-m into a field that has > at the start of the input
mask you will store WAYNE-I-M in your table.

The > can by use within a mask like this

Mask = >L<?????????????? this will give Wayne-i-m
or
Mask = >L<????->L<->L< will give Wayne-I-M

etc
etc
etc

If this was not your question please repost as I may have missunderstood

--
Wayne
Manchester, England.
Enjoy whatever it is you do
Scusate,ma il mio Inglese fa schiffo
Percio se non ci siamo capiti, mi mandate un
messagio e provero di spiegarmi meglio.

 

[Van T. Dinh]

causes all characters that follow to be converted to upper case.

Check Access Help on "Input Mask" for valid masking characters / options /
usage.

 

[Guest]

Just read my own reply - it is not correct -
Mask = >L<?????????????? this will give Wayne-i-m

It should be >L<???-?-??????????
or

L<CCCCCCCCCCCCC (the C allows any digit or space)

As the ? only allow the insertion of text letters (from a to z)

This would also work

Sorry

--
Wayne
Manchester, England.
Enjoy whatever it is you do
Scusate,ma il mio Inglese fa schiffo
Percio se non ci siamo capiti, mi mandate un
messagio e provero di spiegarmi meglio.

 

[Guest]

Many thanks to you both. I have seen and used > used in input masks but
never as a stand alone so was a bit confused since it was in the format
rather than the input mask option. Anyway, thanks.

 

[JK]

Nancy,

As far as I am concerned *nothing* in case of *text* other that control the
way data is entered *directly* into table (Not recommended) . It serves as
the default format (and mask, if any) in the form(s) that are based on such
table, on any data type

If this is important to you, use Wayne's and Van's suggestion, otherwise
leave both the Format and Mask blank in the table and use it in the form as
required, if at all.

Regards
JK

 

[Guest]

I JK

I tend to put (where possible) input masks on a table field - unless there
is a reason not. EG. I don't use input mask on date fields as they are
sometime needed in different formats in diiference sections of the DB. BUT
some field I always do use masks in the table such as Names (1st letter
capital) - Order Numbers when not concencations - (is that a real word ??)

I agree this is mostly due to me being lazy as the masks are copied accoss
the DB and so don't need to be re-entered each time you use a field. As an
example I have one DB that has 7 diff forms where a new account can be
created and each time would have to design an input mask for the order number
- placeing the mask in the table saves me doing this.


--
Wayne
Manchester, England.
Enjoy whatever it is you do
Scusate,ma il mio Inglese fa schiffo
Percio se non ci siamo capiti, mi mandate un
messagio e provero di spiegarmi meglio.

 

[JK]

Hi Wayne,

I agree that this is a matter of approach/habit.

I *always* put date/time format and mask in the table but this is mainly to
brut-correct programming stuff ups. I rarely change the mask in the form,
although often the format does change. Similarly, I do put format for
numbers (no mask) which rarely changes. I try to keep consistency with the
DB as much as possible.

As to names fields, I control the Proper Case in form itself, usually by a
public function which also take care of McDonald, O'Leary, de Amato (for
those Spanish names with no tomorrow , hyphenated names etc.

Regards
Jacob