developingprogrammer
asked on
0.004cm column width for value list combobox not working
hey guys,
i've got a combobox which is populated by a value list Credit;C;Debit;D
column count is 2
column width is 2cm;0.004cm
i'm trying to hide the 2nd column - but because it's a value list i must put column count 2 if not instead of 2 chooseable values in the dropdown it will become 4.
however even though i put 0.004cm, it still shows. in the table lookup field and also in a form combobox.
i can't solve the table lookup field scenario but i can solve the combobox in form scenario - set the column width to 6cm;0.004cm when the combobox width itself is 6cm.
is this a bug that yall face as well guys? thanks!! = )
i've got a combobox which is populated by a value list Credit;C;Debit;D
column count is 2
column width is 2cm;0.004cm
i'm trying to hide the 2nd column - but because it's a value list i must put column count 2 if not instead of 2 chooseable values in the dropdown it will become 4.
however even though i put 0.004cm, it still shows. in the table lookup field and also in a form combobox.
i can't solve the table lookup field scenario but i can solve the combobox in form scenario - set the column width to 6cm;0.004cm when the combobox width itself is 6cm.
is this a bug that yall face as well guys? thanks!! = )
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hrmm IrogSinta do you think there are any benefits of doing
column count = 2
column widths = 2cm;0cm
versus
column count = 1
column widths = 2cm
?
of course given that the row source is a table / query.
i'm thinking that there might be value always defining more columns and then manually setting it to invisible by using the column widths property.
what do you think?
i can't think now but will think tomorrow ha. goodnight
column count = 2
column widths = 2cm;0cm
versus
column count = 1
column widths = 2cm
?
of course given that the row source is a table / query.
i'm thinking that there might be value always defining more columns and then manually setting it to invisible by using the column widths property.
what do you think?
i can't think now but will think tomorrow ha. goodnight
ASKER
ya i think there is value in defining the max column count and then manually hiding it using column widths because it forces us to be aware of the columns that are available to us to use as bound columns. slightly more typing but more awareness is better i believe
Why would you put all the columns if you don't need to refer to them at all? If you find out that you need an additional column later on, then it's pretty simple to revise your column count & width properties at that point. If you think there's a chance that you may use a certain column, then just include it from the onset. Adding all the unused columns brings no benefit that I can see. To find out what columns are available, one simply looks at the RecordSource.
ASKER
ok great point. thanks so much IrogSinta!
ASKER
i kept thinking that to hide columns i need to be able to exclude it from the column count. that solved everything. thanks so much IrogSinta, so so sleepy again ha. thank you