The major drawback with this approach is that any errant application can
break the validation rules for the database.
If you are using Jet as the backend you should try to use as many field and
table validations as you can as these will always be enforced against your
data.
If you are using DB2 (or SQL Server 2000) or any other Client Server RDBMS
then you have a vastly richer environment than field and table validation.
Application validation is also useful, however the fundamental rules should
be enforced at the database engine.
In the OPs case they would need to use a Table validation rule to compare
the values of two fields in the same table.
--
Slainte
Craig Alexander Morrison
Crawbridge Data (Scotland) Limited
Rainbow01 said:
from Rainbow01 Hong Kong
from my experience, i never make Validation in Table
all Validation was made in Forms with using VBA may better
"an" ??:
Hello!
In Table, I would like to make a next "Validation Rule":
[Date1]>[Date2]
But return the next error message:
One or more values are prohibited by the validation... and don't save.
Why?
Thanks in advance.
an