ADM2 validation code where???

lord_icon

Member
Greetings,
I am developing using Progress OpenEdge 10 on a Windows box.
In V8 ADM(1) I would have a validation criteria block in local-assign however I am developing using OE 10 & ADM2.
Where is the appropriate place to have my block? When the record is written back to the db / assigned I get a flag however, all the widgets are disabled. Where should I have my code so the widgets do not become assigned back to the db then become disabled?
TIA
 
ADM2 Validation

I'm not doing any ADM2 OE10 coding yet but assume they are using the same as 9.1D. I say that because there is a possibility that they moved to DLP's.

I put all validation in the sdo so that it is in 1 place and will be applied if all updating is done via the SDO regardless of the interface.

Client side validation goes in rowObjectValidate and server side in preTransactionValidate, beginTransactionValidate, endTransactionValidate, or postTransactionValidate.

To stop processing either return "some error string" or use addMessage.

Miles
 
I found the procedure I require. There is a (local) validate internal procedure in the SmartDataViewer that I can over ride.
Thank you.
 
Viewer Validation

The downside of validation in the viewer is that if you have another viewer or other object or web interface then that validation is not performed. You may not have another interface at the moment but who knows the future.

Also it's good to keep validation together in the one object the sdo or a dlp (attached to the sdo).

I assume the validation need no db connection. Never place validation that refers to the db in the viewer.

Miles
 
You must consider several changes for that kind of migration. I am suffering the same, I recommend you to read the whole documentation before.
 
I assume the validation need no db connection

I assume the validation need no db connection. Never place validation that refers to the db in the viewer.

Indeed, that is correct. I am already aware that db validation WOULD NOT go in the SDO (viewer). I only required validation for the widgets at user-interface level.
Problem resolved, as I mentioned. Thanks for the help.
 
Back
Top