Easy ones first <g>

>PS: OTOH triggers don't fire till tableupdate(). Some fields' valid value might be dependant on other fields. So thinking would it be better to check for validations during tableupdate (mark those failed and a single messagebox for all?).

I would like at field.valid() time, I want to send a clean update. I had tried without .valid() and when a silly thing failed the whole thing reverted as per the framework, lost a whole data entry.


>Base table has no validation expression or matches yours.

Yes that should be the case 99.9%


>Consider this scenario :
>In base table you set a field's rule expression as IsDigit(Field)
>From your metadata you set field in view with an expression !IsDigit(Field).
>When your view submits the change base table would reject it and set to empty/null.
>IOW if you're carefull enough not to make such errors than you should be OK.

I will be, but the plan right now and what the framework wants, is nothing in the table, either in the BO (framework wants it that way) and this special table (My Way - Elvis Presley, then it will always be the view)


>If you're setting these with dbsetprop() and controlsource is directly bound to view.fieldname (most likely will be)

yes

>, your validation would execute as soon as you hit a key to leave the field and ValidationText from DBC would popup.

My way yes, but not so in practice. It failed only when I saved the framework way.