I've used a validation rule that enforces at least minimal compliance:
Like "?*@?*.??*"
This requires one or more characters, followed by the @, one or more
characters, followed by the ., followed by two or more characters (as far as
I know there aren't any single-character domain types).
You can't make a useful input mask because the number of characters in each
position varies. Input masks are only helpful if the input format is always
the same, or perhaps a few options like you can see in the samples for zip
code and phone number.
"Sue in IL" <Sue in
(E-Mail Removed)> wrote in message
news:22282F63-7CC7-43F6-8A0E-(E-Mail Removed)...
> John
> if you've already written this VBA code would you consider sharing it? I'm
> just temping here to create a dbase (& based on what I've seen so far, the
> more input masks I can build in the better!)
> thanks much, Sue
>
> "John Vinson" wrote:
>
>> On Tue, 28 Nov 2006 20:20:00 -0800, Abilash Sanam <Abilash
>> (E-Mail Removed)> wrote:
>>
>> It's considered polite to use the big white text area to post your
>> questions.
>>
>> An EMail field is simply too variable and too complex for the very
>> limited Input Mask tool to manage. You'll need to use some non-trivial
>> VBA code in the BeforeUpdate event of the textbox on your Form to
>> validate it, or just trust your users.
>>
>> John W. Vinson[MVP]