Derived columns don't inherit windows control settings

I’m trying to use the derived feature to add a new column to lots of tables. I want it to use a drop list control but even though I have it set to that in the parent column in the pool, when I create the derived column in the tables it has the Option control selected. I thought I read in the HELP that it inherits the controls too but it’s not for me. Am I wrong on this?

Yes, I believe it only copies part of the field definition? I remember trying it once and didn’t find it all that useful except for the odd local variable that I wanted the same size as the original field definition.

Oh well, yes that does limit its usefulness.

It does give you a list of all the derived columns so you can click on them and update them manually. That’s a bit of a help at least.

Have you tried defining the field once and then using copy/paste to duplicate that entry in your other tables? Not exactly deriving but probably simpler than entering the same definitions repeatedly.

I’ve use copy/paste sometimes, but using the derive feature gives the small advantage of showing the list of derived columns so you can step through them one at a time to make manual updates.

I’m making an attempt to set more parameters in the dictionary but am finding that some of them don’t carry through anyway.