Message: Stopped because of warnings, v9.05

Hi, I'm running DbVisualizer 9.05 with Sybase/ASE 15.7. When I attempt to execute two consecutive batches of statements: PRINT @@version GO PRINT 'Yay!' GO ... The second batch is never executed. After the version is printed, the message I get is "Stopped because of warnings". See the attached image. I have allowed "go" as a statement delimiter (options config). I'm not sure what the warning is about; there's no error in these statements, since they execute fine with command line "isql". Any ideas? Scott.

Hi Scott, I cannot reproduce this. Please enable debugging of DbVisualizer in Tools->Debugging and post or email us the output. Also, please use right-click Copy in the Connection Message area for your connection and paste into your reply so we can see which JDBC driver version you use. Best Regards, Hans

Hi Hans, sorry for the response lag. Here's the info requested. Scott. ----------------- Connection message pane ----------------- Adaptive Server Enterprise Adaptive Server Enterprise/15.7.0/EBF 20805 SMP ESD#04 /P/RS6000/AIX 6.1/ase157x/3245/64-bit/FBO/Fri Jan 4 02:55:35 2013 jConnect (TM) for JDBC (TM) jConnect (TM) for JDBC(TM)/7.07 ESD #4 (Build 26792)/P/EBF20144/JDK 1.6.0/jdbcmain/OPT/Thu Jun 7 23:57:39 PDT 2012 ----------------- Log Window ----------------- 10:26:44 [PRINT - 0 row(s), 0.053 secs] Command processed. No rows were affected Code: 0 --- Adaptive Server Enterprise/15.7.0/EBF 20805 SMP ESD#04 /P/RS6000/AIX 6.1/ase157x/3245/64-bit/FBO/Fri Jan 4 02:55:35 2013 ... Stopped because of warnings ... 1 statement(s) executed, 0 row(s) affected, exec/fetch time: 0.053/0.000 sec [0 successful, 1 warnings, 0 errors] ----------------- Debug Window ----------------- 10:26:44 [DEBUG pool-5-thread-5 E.?] DefaultEditor76: SybDatabaseMetaData.getUserName() 10:26:44 [DEBUG ExecutorRunner-pool-4-thread-6 J.execute] Executing... 10:26:44 [DEBUG ExecutorRunner-pool-4-thread-6 J.setCurrentCatalog] DbConnection='BF.nax401cd771' Catalog='HST' Schema='null' NewCatalog='HST' 10:26:44 [DEBUG pool-5-thread-5 E.?] DefaultEditor76: SybDatabaseMetaData.getUserName() 10:26:44 [DEBUG ExecutorRunner-pool-4-thread-6 J.setCurrentSchema] DbConnection='BF.nax401cd771' Catalog='null' Schema='dbo' NewSchema='jonahdev' 10:26:44 [DEBUG pool-5-thread-5 C.?] DefaultEditor76: SybConnection.createStatement()

Hi Scott, Thanks for the information. I should have spotted this earlier. Both PRINT statements result in warnings (due to "No rows were affected"), and you apparently have enabled Stop on Warning in Tool Properties, in the SQL Commander category under the General tab. If you don't want this behavior, please disable Stop on Warning. Best Regards, Hans

Yes, that solved it! Thanks so much. Scott.