Error System Level exception

[capblans]

Hi!

I found, I think, the reason of the error. It's because TestStan recopy in the cache memory the information of the table between the beginning and the current index. So when the informations are too important there is an error.

The table, which TestStand access, have 3 column. Two are string and one is a number.

TestStand access to two string column.

I attached the loop I made.

[Scott_Richardson]

capblans -
I could not use your sequence because you have a custom do/while step types. I tried a similar testcase to what you are doing and it did not fail.  I fetched 30 values from a table in a loop.  I ran this sequence in a loop 100 times.  No error or failure. The accessing to the database that you are doing is basic access and we and other customers do this all the time. Can you be more specific about why you think the error is occurring?

[capblans]

I also did 30 occurences but with an other type of column. When the type is VARCHAR with more than 20 characters, I can't do more than 30 occurences.

I hope I answered your question.

capblans

[Scott_Richardson]

capblans -
I still cannot duplicate the problem.  I ran 300 plus loops where each loop fetch 30 records from the database. For each record I fetched data from a CHAR(255), VARCHAR(255) and an INT column. The values in the character fields were at least 50 characters.  Based on the exception that you are seeing, I feel that it is either caused by memory getting corrupt, or there is a bug in the version of MYSQL that you are using.  If you use a simple goto instead of your while step type, does the problem still occur? What version of MYSQL ODBC and server are you using?

[capblans]

I find a solution to do not have the error. It's using a property loader instead of the GET values step.

Even if I use a goto step at the end of my sequence it doesn't work.

I use the last version of driver MyODBC  (version 3.51).

I use the version 2.0.53 of Apache server.

[dug9000]

I don't know much about databases, but is it possible that the database char and varchar sizes that you were using were too small and thus memory was getting corrupted when you wrote or read too much data from these entries? Maybe this is not possible, but just a thought. Anyway, glad you found a workaround for the problem.

-Doug