The DDT auto-generated sprocs, UPDATE specifically, expect all fields in the table to be passed as parameters and blow out if the BO's fill method that you call BO.save() against (causing an UPDATE) doesnt pull all the fields. I have some fields that I never want updated as they are only updated via triggers on the table itself defined on the SQL Server. Should I just override the definition of the SPROCS to not include these fields? or it is better to leave them and fill() all the fields even though they will never be updated or modified (which seems silly especially for a large table).

I see the collection of FieldstoExcludeFromUpdate on the BO's, I suspect these only work when NOT using CRUD sprocs, correct?

Still learning about using sprocs, appreciate the answers.

Keith Chisarik

That is what I thought I just wanted confirmation that it was "ok" since I hadnt run across it before.

Thanks

Keith Chisarik