Synametrics Technologies

After winsql has been connected for a while, I cannot submit any more queries or even try and disconnect/reconnect, I get the following error: List index out of bounds (1) I usually am connected to oracle and sybase at the same time, and to get things working again, you have to exit the application. Any ideas? This is still happening even with 5.5.59.566

Hi, Could you please send us the steps to reproduce this problem. Regards, Synametrics Support >After winsql has been connected for a while, I cannot submit any more queries or even >try and disconnect/reconnect, I get the following error: > >List index out of bounds (1) > >I usually am connected to oracle and sybase at the same time, and to get things working >again, you have to exit the application. > >Any ideas? > >This is still happening even with 5.5.59.566

This just happened again -- I had 2 winsql windows open for at least a few days - one to oracle, one to sybase... I had about 10 query pages in each connection, but when I just switched over to winsql and tried to drop down the "available query pages" box, it was blank.... thankfully, I was able to save workbook, close, and then reopen the workbook, but for some reason it seems after a long period of inactivity, the available query pages goes blank and displays the "list index out of bounds (xx)" -- today it was 10 -- I presume because I was on the 10th query page. Hopefully this will help you guys track down the issue. Let me know if there any anything else you need from me. >Hi, > >Could you please send us the steps to reproduce this problem. > >Regards, >Synametrics Support

I'm able to connect to the DB2 database successfully. When I execute any SQL "Select count(*) from dbowner.table name" I get the pop up window with the message "List Index Out of Bounds"

>After winsql has been connected for a while, I cannot submit any more queries or even >try and disconnect/reconnect, I get the following error: > >List index out of bounds (1) > >I usually am connected to oracle and sybase at the same time, and to get things working >again, you have to exit the application. > >Any ideas? > >This is still happening even with 5.5.59.566