Type mismatch when using dat adriven testing.

Hello. The control doesn't seem to be the problem. Definitely something to do with the reading of the data. Yesterday evening off the back of you suggesting trying to type a problem value without data driving, I managed to come up with a work around for this problem. As the problem occurs if the driving data within a given column switches from numbers to letters I have performed a global replace on my driving data swapping all letters for a previously unused number e.g. replace all R values with 88. I have then used the "if then" command to call a second keyword script when the value 88 in encountered.The second script is short and simple script which uses the wtext command to type R within the control. This seems to work pretty good. I know its not ideal but until we can get to the bottom of this its a fix.