First- thanks for taking the time to continue this thread. In reading through the forum, I see that you have been repeating this message with regular consistency… I assume that means it is important. I get it. I do not however get the meaning of your message regarding “Typed DataSet” –vs- “UnTyped DataSet”. I have read thru more than half of Rod Stephens’ Visual Basic 2005 Programmer’s Guide and there is no mention in this book about “Typed" or "Un-Typed" DataSets. (As a side comment I have not really gotten so much from this book anyway).

So, I know this is off topic, but can you (will you) recommend a reference book that will help me with VB programming? I learn best from examples.

Back on topic: I tried the DataSet reference as you suggested and found that I can better explain what it is that I am having trouble with. If I use:
vb Code:
  1. MyDataSet.MyTable(RowNumber).ColName = NewVal
Then I will have to hard code every reference to the dataset and for my program that will take several hundred lines of code. If I can point to DataRow DataColumn property with a code built string (or to a code built column number) then my code reduces to about 50 lines. It seams more efficient. But this gets me back to doing what I think you are indicating is not the best method.
vb Code:
  1. MyDataSet.MyTable(RowNumber).item(str_ColName) = NewVal
The location of where the data needs to be written in the DataSet is dependant on several independent variables. Is there a way to stick with “Typed DataSets” and use a variable for the DataRow DataColumn property?

PS- If from my question it sounds like I just do not get it… there is probably a reason for that. But I am trying.

Thanks for your help.