Why am I not surprised, Peter?

>Barbara...
>
>This works but of course - more questions <grin>....
>
>- Why set the ROWSOURCE to ALIAS instead of FIELDS?
Umm.... Because I always do?


>- Does it matter if the BOUND TO is TRUE or FALSE? I can't seem to see any operational differences.

This only matters if you have a numeric field. Then you'd set it to TRUE. It's explained in the help. Try it with a small combo with both numeric and character data.

>- You said set the CONTROL SOURCE to TALLY.EVENTID... I don't have TALLY in the DE. Only: EVENT,
>BAR & VEVENTBAR (the view of the tally file). When I set the CONTROL SOURCE to anything, I get erratic
>behavior. The COMBO doesn't sort right, when I pick the records it picks a different record, etc. If I leave it blank
>it works EXCEPT (there always has to be one of those)... I can pick the event, pick the bar, and the requery in
>the interactive changes displays the records in the view. I can click in the view, no problem. I can also change
>the bar, again, no problem. BUT, if I click on the EVENT, I get an error VARIABLE "NAME" IS NOT FOUND.
>This is a never ending repeating error. I have to END TASK vfp to get out of it. I tried running the debugger, but
>it doesn't show me where this is coming from.

OK, I made the erroneous assumption that the data was linked to a single table record. No, you don't need to have Control Source set to anything, it can be blank. It sounds like there's some code in your EVENT combo that's running during updates. Have you tried deleting it and rebuilding it using the BAR combo as a model? Walk through the code with the debugger to see exactly where it is failing.

Barbara