I have a editable business base that has editable child objects of three different types.
Parent
ChildTypeOneCollection
ChildTypeOne
ChildTypeTwoCollection
ChildTypeTwo
etc
They are all editable together on a single WinForm.
The base object uses standard controls (text boxes, combo boxes, check boxes, etc.). The children are edtiable within a datagridviews on separate tab pages on the same form.
I am overriding the CanWriteProperty for some parent and child object properties that are only editable at certain times (based on data).
I'm using the read/write authorization control to update the controls automatically based on those overrides.
The contols for the parent properties that are not editable are disabled and don't allow the user to believe they can edit the field.
However, the datagridview that is bound to the child object DOES NOT disable the column in the grid (and doesn't even appear to "check" the editability of the child properties until AFTER the user enters data; at which point the business object returns the security exception that the field is read-only).
I realize that datagridviews need instantiated on all the tabpages before binding and I've done that. Regardless, the initial tabpage that displays doesn't even appear to work properly.
Does anybody know what I'm missing as to why the datagridviews don't check the child property editability and disable them so the user isn't inclined to think they can edit the data?
Do I need separate read/write authorization controls for each child? Does it have something to do with object and control instantiation timing?
Any help would be GREATLY appreciated!
Copyright (c) Marimer LLC