>No I have not used with a view. I take a different approach to table updates and do not bind the controls to the underlying table/cursor. I assign the controls the values and in the update I perform the SQL Update command in a TRY CATCH block with BEGIN/END TRANSACTION. The CATCH will perform the ROLLBACK in the event of a failure. But I do use the Assign and Access properties a lot particularly with container classes (generally I do not use the control class) to assign/query values of controls within the class.

I do almost exactly the same on all personal projects, and in most projects I've worked on previously. The model used by MereMortals is different. It's been a great source of many headaches over the years. We feel the MM pain a lot. :-) We even hired one of the MM developers I believe to come and look at our app and tell us what's wrong with our implementation and design because of issues we were having. That person didn't find anything.

My advice to everybody: Don't use value_assign() if you have edit controls which back directly into a field on a read-only view in MM. It will turn on you, and wound you deeply. :-)