Voila.

Unhooking the lookup combo box from the control source has freed
up the pointer to go where it wants to. So your consulting and
your patience has resulted in some success. I think the combo box
builder set that control source in the first place, probably
assuming I wanted to update a field in the record by working the
combo box. Now, at the risk of asking for moreMoreMore, I do have
(I hope) one more question.

In fact, I do want to update some fields based on CBoxes. I have
a few fields where I want to control the input to certain choices,
and I'm now looking at how to disable them when I'm not in add or
edit mode. When the form starts up, most of the fields are not
enabled, but these CBo's are. If I can reset these so they won't
work, I can prevent users from even thinking they are updating the
file unless they click on either Add or Edit.

I've tried to begin this process by setting the form's init event to
disable these "Update CBo's", and I've set the cmdAdd and cmdEdit
click events to do

thisform.CBox2.enabled=.T.
thisform.CBox3.enabled=.T.
thisform.CBox3.enabled=.T.
DODEFAULT()

I was hoping to use either the Save or Revert button to turn
them back off again but they're not in the form's object list.
It looks like VFP is reusing the Add and Edit button to save
space. Should I be doing a CASE thing here? Or is there some
other more convenient place to turn these things back off?

I believe that if I can get this part of the thing to work, I'm
done with the hard part. Your help has been invaluable.

Bob