Dropdown Disabled but enabled for new line items

[Lesg]

Hi Guys, I have an issue with a client who's raised concern over a sub form for line items in a invoice form. The problem is, all line item dropdowns on the subform are enabled allowing them to be edited, and additional line items be added if required.

However, it appears some users occasionally, in error, are changing the product in the dropdown, rather than adding a new item at the bottom. So what I thought about was a way to disable the current line items dropdown, and just make the new row enabled.



The normal use of this form, is to edit order line items that have been placed. i.e. the quantity of the item, or delete item, so need a way to show the dropdown disabled but with the option to add a new item if required, which should be disabled when the user tabs through the form onto next row.

Any suggestions appreciated.

[Welshgasman]

Test for NewRecord ?

[CJ_London]

use conditional formatting - something like this
expression is......not isnull([cboProduct])

and set the condition to disabled


alternatively in the control properties set disabled=true and in conditional formatting

expression is......isnull([cboProduct])

and set the condition to enabled

you might want to set exactly the same condition for the other editable controls so they cannot enter anything there until they have selected the product

[Welshgasman]

use conditional formatting - something like this
expression is......not isnull([cboProduct])

and set the condition to disabled



alternatively in the control properties set disabled=true and in conditional formatting

expression is......isnull([cboProduct])

and set the condition to enabled

you might want to set exactly the same condition for the other editable controls so they cannot enter anything there until they have selected the product

@CJ_London
For the first option, isn't that going to happen as soon as anything is entered (and possibly tabbed out of) ? When does CF take effect?

[CJ_London]

No - not sure whether it is the after update, lost focus or exit event but it doesn't take effect until the user moves to a new control

[Micron]

IMO unbound combos are ok for filtering, but if you present them as bound controls, expect that users will accidentally alter the field in records. If only looking at data, I'd open that form with the combo(s) locked and provide some other way of adding items to it. That might be a command button to add list items or perhaps dbl click event on the locked combo, either of which could open an add items form. Opening said form in data entry mode would be different.

[Lesg]

use conditional formatting - something like this
expression is......not isnull([cboProduct])

and set the condition to disabled


alternatively in the control properties set disabled=true and in conditional formatting

expression is......isnull([cboProduct])

and set the condition to enabled

you might want to set exactly the same condition for the other editable controls so they cannot enter anything there until they have selected the product

Thanks for that suggestion, will test it out and feedback, thank you

[CJ_London]

Don’t think we are talking about unbound combos? What makes you think we are?

[Micron]

Didn't say we were. I'm saying don't use bound combos as fields in records unless you either expect users to accidentally alter data or do something to prevent it.