if you are using fixed field sizes then you can easily tell where the 3rd row is.
If you are not, you need to establish a delimeter character, (in this case you are using comma which is ok if you are not allowing users to enter data) and read each byte until you encounter it.
Your next problem is reading in the string value (you need to know how long the string is), you can obviously do this by finding the distance from the first delimeter (or the beginning of the file) to then next and reset the stream postion to the start point, then read in the string.
*EDIT*
if each row is on a seperate line in the text file you can use the linefeed at the end of the line as a row delimiter, so in blitz you would look for "~n".
If you are not, you need to establish a delimeter character, (in this case you are using comma which is ok if you are not allowing users to enter data) and read each byte until you encounter it.
Your next problem is reading in the string value (you need to know how long the string is), you can obviously do this by finding the distance from the first delimeter (or the beginning of the file) to then next and reset the stream postion to the start point, then read in the string.
*EDIT*
if each row is on a seperate line in the text file you can use the linefeed at the end of the line as a row delimiter, so in blitz you would look for "~n".