Title: | SQL/Services Forum |
Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
Moderator: | SQLSRV::MAVRIS |
Created: | Thu Oct 13 1988 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2214 |
Total number of notes: | 8586 |
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2116.1 | M5::JHAYTER | Tue Dec 17 1996 14:02 | 12 | ||
2116.2 | -1 don't mean much | M5::JBALOGH | Tue Dec 17 1996 15:23 | 7 | |
2116.3 | ..all set... | BROKE::BASTINE | Wed Dec 18 1996 11:30 | 10 | |
2116.4 | Another one...this time SQLError not helping | BROKE::BASTINE | Thu Jan 23 1997 12:25 | 12 | |
2116.5 | client/driver logs hold the answer | M5::JBALOGH | Thu Jan 23 1997 17:03 | 9 | |
2116.6 | M5::JBALOGH | Thu Jan 23 1997 17:10 | 4 | ||
2116.7 | Some answers... | KREDIT::BASTINE | Thu Jan 23 1997 19:32 | 9 | |
2116.8 | M5::JBALOGH | Thu Jan 23 1997 19:49 | 5 | ||
2116.9 | thanks john.. | KREDIT::BASTINE | Thu Jan 23 1997 19:59 | 4 | |
2116.10 | User error using sqlerror call | BROKE::BASTINE | Mon Jan 27 1997 19:50 | 6 | |
Just to keep this documented, I'll need it again someday!! The customer found his problem with sqlerror calls, he was passing the wrong call to sqlerror. When he passed the right one, he received an informational error that helped them solve their problem!! Renee |