Is there a limit to the number of rows you can call in a single test?
My test always fails after 64 rows of data have been called and it does exactly the same thing each time. Could this be down to memory? If so, is there a function or a tool I can use that will flush out the memory?
Also I have a different test that calls data from a spreadsheet that has around 80 different excel worksheets within it. This test fails when I call data from about the 64th worksheet. Is this also a known problem with Test Complete? And how do I get around this? [img]/images/graemlins/confused.gif[/img]
We replied to a similar question that you asked in the following thread:
Do our suggestions help you?
Yes you did thanks, I used the script you gave me to close the connection, but I found I could not reopen it again once it was closed, but I've left that test to one side for the minute.
For now though I still need to know if there is there a function or a tool I can use that will flush out memory?
Unfortunately, there is no such function in TestComplete. As for external tools that would do this, I'm not sure whether there is any.
If you are having memory problems when running tests, most probably, the log is too large. In this case, you can try disabling events by using the Log.LockEvents method (see the "Log.LockEvents" help topic).
BTW, there's no way to re-open a closed connection - you can only create a new one.