R
Ronald R. Dodge, Jr.
Excel 2002, SP3
Based on the research I have done thus far, I don't like what I see as it
breaks away from good programming practices and it also relies on late
binding rather than early binding.
When declaring userform variables, it must be assigned to the "Object" type
to be able to use a few different things like the Show method. While using
"Object" is slightly better, it's still almost as bad as using "Variant"
cause it doesn't specify the "TYPE" of object.
Why does the VBA UserForm Object not match up to the UserForm that's created
within Excel VBA. If it's cause the actual UserForm is only for Excel, then
why does the Excel codes not have a UserForm object that can be used
programmatically?
--
Thanks,
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
Based on the research I have done thus far, I don't like what I see as it
breaks away from good programming practices and it also relies on late
binding rather than early binding.
When declaring userform variables, it must be assigned to the "Object" type
to be able to use a few different things like the Show method. While using
"Object" is slightly better, it's still almost as bad as using "Variant"
cause it doesn't specify the "TYPE" of object.
Why does the VBA UserForm Object not match up to the UserForm that's created
within Excel VBA. If it's cause the actual UserForm is only for Excel, then
why does the Excel codes not have a UserForm object that can be used
programmatically?
--
Thanks,
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000