Problem solved.

Just in case anybody else runs into this, the problem was my "quick
test" code in the KeyDown event. For one thing I wasn't telling the
grid that I handled the tab keydown event. So I added e.Handled = true
to my code. The second problem was that my first visible cell was not
cell 0, so that is why it didn't look like the cell was selected. To
fix this instead of using the cell index I am using the cell name.

Thanks for the efficiency tip. I'm just a few days into using the
Infragistics' controls so I'm still learning.

I modified my KeyDown event to the following but the tab key is still
navigating rows instead of cells.

if (e.KeyCode == Keys.Tab)
{
this.ultraGrid1.ActiveRow.Cells[0].Activate();
this.ultraGrid1.ActiveRow.Cells[0].Selected = true;
}

I'm getting the same tab key behavior even if I use the mouse to select
a cell.

So I decided to create a new window without any other code (except to
retrieve records) or any changes to the default settings for an
UltraGrid and the tab key does indeed navigate cells after I click the
first column. So I'm going need to spend some time figuring out what it
is that I changed that is causing the tab key to navigate rows instead
of cells in my original window.

Thanks again for your help.

> The easiest thing to do would be to handle the KeyDown event of the grid and handle this in code. There's no key action mapping for this.

Hi Mike,

Thanks for the quick reply.

For a quick test of your suggestion a put the following code in the
KeyDown event.


if (e.KeyCode == Keys.Tab)
{
this.ultraGrid1.Rows[ultraGrid1.ActiveRow.Index].Cells[0].Activate();
}

And it does indeed select the first cell. But the row seems to still be
selected, since subsequent presses of the Tab key navigate to the next
row. How do I get the ultragrid out of a "row state" and into a "cell
state" so that the Tab key will navigate to the next cell?

Thanks.