I have noticed while working with standard controller.vb code:  GetNull(NameInfo.DataField1.ToString), GetNull(NameInfo.DataField2.ToString)
...that this code's interaction together with .ascx is currently limited to having all the <asp:BoundField> columns present, in order for the update to correctly store all the fields updated / un-modified data.  Makes sense, but not always logical.
It seems to be a question of the values having the ability to be null, or retain the existing value, even without the column present for UPDATES.
All the table columns within table (other than id,moduleid, portalid, userid) allow nulls, but in this case, columns not present would retain the existing value.

1.)  How would the values be updated, while all of the asp:Bound Columns are not visible and/or keep the existing value?  (Simple visible=false within ascx.  causes classic: Target of Invocation)

Feedback Appreciated