Re: Validation Rule for field
- From: Steve Schapel <schapel@xxxxxxxxxxx>
- Date: Sat, 18 Jun 2005 09:02:20 +1200
Klatuu,
Klatuu wrote:
I don't think it allows the control you need, for starters,
Yes it does. It provides precisely and simply the exact control you need if you have a field-level or table-level validation requirement.
and most important, should you ever have to upsize, it creates a problem. Not all database engines will recognize it.
Well, this applies to a lot of data types, properties, etc... Do you avoid them all for the same reason? Thereby denying yourself some of Access's most attractive bebefits. I can't believe anyone would consider this a valid design choice.
Also, if you are modifying or debugging it is not readily obvious.
Yes it is. It wouldn't be obvious to you, maybe, because you don't use it so therefore don't think of it.
I just think it is better to do all validation using VBA in the form.
No it's not. Certainly there are pleanty of scenarios where form-level validation is applicable... but not in the examples we have been discussing.
If it works for you and you like it, okay. I would not use it
Fair enough.
and I advise that it not be used.
In my opinion, you are doing a disservice to those you so advise.
-- Steve Schapel, Microsoft Access MVP .
- Follow-Ups:
- Re: Validation Rule for field
- From: Klatuu
- Re: Validation Rule for field
- References:
- Validation Rule for field
- From: Danny
- Re: Validation Rule for field
- From: Steve Schapel
- Re: Validation Rule for field
- From: Klatuu
- Re: Validation Rule for field
- From: Steve Schapel
- Re: Validation Rule for field
- From: Klatuu
- Validation Rule for field
- Prev by Date: Re: Moving items in a listbox up or down
- Next by Date: Re: DLookup
- Previous by thread: Re: Validation Rule for field
- Next by thread: Re: Validation Rule for field
- Index(es):
Relevant Pages
|