Thank you! The AllowNavigate=False fixed it. Now when you tab off the last field on a row it moves to the first field of the next row, like it should. I added that site to my growing collection of .NET resource Favorites. I need to organize them some day. :)

BTW, if you ever do any ASP.NET development, I recently ran across this site that is the best ASP.NET Primer/Tutorial/Resource I've found.

http://authors.aspalliance.com/aspxtreme/

-----
Lee


>Lee,
>
>Here's what I did to make it work (I use C# and not VB.NET, though this should be pretty easy to convert...
>
>DsTest.Relations.Add("TableRelation", DsTest.Tables["Table1"].Columns ["ssn"], DsTest.Tables["Table2"].Columns["ssn"]); // similar to what you had
>
>dataGrid1.DataSource = DsTest.Tables[0]; // I don't use setdatabinding
>dataGrid1.AllowNavigation = false; // should fix the navigation issue
>
>dataGrid2.DataSource = DsTest.Tables[0];
>dataGrid2.DataMember = "TableRelation";
>
>(Because I had to create some data, I just created two simple datatables, related by SSN).
>
>I could not get SetDataBinding to work on the 2nd grid...the relation wouldn't refresh correctly. Not sure why, but when I switched to datasource and datamember, it worked fine.
>
>The 'allownavigation' should take care of the navigation issue on the top grid.
>
>Also....here's a site that might be helpful for you...this one has saved my bacon a million times...
>
>http://www.syncfusion.com/FAQ/WinForms
>
>There is a ton of sample code up there.
>
>Hope this helps!
>Kevin