>>>Or specify the same default value in the view definition, and the view takes care of itself.
>>
>>That's a maintenance headache (as all duplication tends to be).
>
>If you maintain your views in code, and have a routine that generates them, you can have the same routine copy extended field properties from the table to the view. Only a maintenance headache if you do everything manually. :)

Hey, this is computers... they're supposed to be used for automation :)

I think GenDbc should have an option to copy these things for views (default values, trigger code references, long names etc) from original tables _before_ generating any code.