Rex,

Back in March, we were discussing your approach to getting "defaults" formally into the framework, that seemed to solve most of the issues with setfldstate, "Save Changes", and allowing the defaulted fields to be saved. It didn't show up in the latest version of the framework, so I guess your still the "Guru of Defaults" concerning the framework.

What have you evolved the implimentation to be at this stage?

I am once again having to incorporate something into the my base subclass to handle defaults, application wide and wanted to benefit from your well thought-out approach. From you eariler code you sent me, I can see how it would all hang together, but my "Cancel" does trigger the "Save Changes" when nothing was edited other than the setting of the default values.

Where each method call is placed would also help.

Thanks for sharing you great ideas with the rest of us.


Gary Pike.