Enforcing server-constraints on the client

grebov

Member
I want to automatically enforce server-constraints on the client using TOracleDataSet on the field level.
(For example when user try to leave TDBEdit control without entering any value server constraint (NOT NULL) for that field will not let him do it.)
But this simply do not work. I correctly use named server constraints and I correctly set enforceConstraints property tu True!
I am using evaluating copy of DOA components
(demo) and this feature (server cons on client) is very important to me!
So, can you help me?
 
The EnforceConstraints feature does not check constraints when the field value is empty. Perhaps we can make an enhancement for the next release that allows you to control this behavior.

If you define your columns as not null instead of using a named constraint, Oracle will report these fields as required and TField.Required will become True. Normal TDataSet processing will now handle required field checks.

------------------
Marco Kalter
Allround Automations
 
Back
Top