Hi Tamar,

But what do you do if you want the user to see an item in a list, but do not, for one reason or another, want the user to be able to select it?

We make what I think is very effective use of the ability to disable items in a list.

This occurs when the list is conditionally populated depending on elections the user has made in other controls on the form, primarily checkboxes and option button groups.

We tried just not showing the users the "disqualified" list items, but that proved unsatisfactory to the users who wanted to see the items they had not chosen as well as the chosen items to better determine whether they had selected the right combination of conditions.

By allowing the users to view disqualified items, but not permitting these items to be selected, we have accomplished our aims, and still aleviated the users' concerns.

In short, I think there is a place in the interface for disabled list items to indicate items in the list that are not valid choices under specific conditions, which is, I suspect, why the capability to disable list items has been included in VFP in the first place.

Regards,

JME

>The basic idea of a listbox or combobox is that all the items in it are valid choices. So you're not really supposed to be able to disable items. As you've learned, you can disable an item with certain RowSourceTypes by preceding it with a "\". However, you should really rethink this strategy from a user interface point of view. Users expect to be able to choose anything in a list.
>
>Okay, now that I've said that, you can disable the other columns in a listbox by using the "\" in front of the entry with the AddListItem method, which is what you need in order to populate those columns.
>
>Tamar