>Hi Nancy:
>
>I think I'm doing pretty much as you outlined already...
>
>>1. Do you mean "BoundTo" ?
>** Yes, BoundTo = .F.
>
>>4. I don't understand your implementation. What does the combo box do with regards to recycling a deleted record? Do you mean that the cbo shows the deleted records that user can pick to recall?
>
>** Basically, I am trying to use the combobox as a picklist with no editing/adding items to the picklist allowed at the screen in question. Sorry for the confusion on recycled records -- the answer to the original question is: YES, I do add a record to the master table prior to calling the CBO. The fact that I use Recycled records is really irrevalent, I hope. As for Item-1, I can try to set BoundTo = .T., but that seems counterintuitive to me... I'll try it & let you know.
>
>>Notes: don't use PRIVATE variables (generally, and specifically here). Use form properties instead.
>
>** If you look again at the squished-up code, you'll see that the only private is for the return code for the valid -- which I think is an okay approach... Otherwise, absent the change to BoundTo, I'm at a loss...
>
>Anyhow, thanx so far... If you have any other thoughts, I'd be grateful.
>
>TIA
>
>ROB

I don't know what you're actually doing with combo, but there are some things which might help you. When you drop combo and move through list portion items, you actually move record pointer in combo.rowsource, and it may harm other parts of your application/form which may use the same work area/alias, especially if you use bound controls and/or temp relationships. The safer method is to populate combo either from cursor or even using AddItem (if you have few items).