You (and Mike Y) are correct. The next day when I tried it, the columns (having ControlSource equal to memvars) always showed the same value for each row in the grid :( So back to square 1 :) My next approach was to open another instance of my Products.dbf table in the form's DE, and aliased it as "Lookup". I now use Lookup for the ItemNo dropdown combo control. Lookup has no relations defined. But the InvDetail table has a relation defined into Products. So columns like ItemDesc can now be defined with ControlSource=Products.ItemDesc. The end result now works as I had wanted all along...

But seeing what a PITA working with grids can be, I went and bought a copy of Codemine... Wish me luck :)



>
>I'm still amazed that it works for multiple rows... may be some weird combination of sparse(ness) of those m. columns. Since the grid actually has only one row (the other rows are the images of the current row, saved during refresh, when each row becomes current for an instant), if your memvars were regularly updated for each row, or if they were used for current row only, this may work. Is the controlsource for the column set to the field in Products and the controlsource of its textbox to the memvar? That may do it, though I never tried.
>
>A possibly more stable workaround would be to separate the rowsource of the combo from the products table. You could just open the same table again under a different alias, and use that alias as the rowsource, then jump to the same record in it when leaving the combo.