Auer, Wolfgang wrote: > > Hello Peter, > > for cursor names > 64 characters SQL Studio throws the error > -2014 POS(6) Identifier too long. > If the cursor name is between 32 and 64 characters the kernel > does not throw an error. > The webpts error is > http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID > =1127676. > > Regards > Wolfgang > The kernel will throw an error during execution of the dbproc (with the newest kernel-versions). The webpts mentioned above will tell you when the check will be available even during preparation of the dbproc (earlier/better time for this check).
Elke SAP Labs Berlin > -----Original Message----- > From: Auer, Wolfgang > Sent: Freitag, 6. Februar 2004 15:34 > To: Mailingliste MaxDB (E-Mail) > Subject: FW: Error in SQLStudio by execution of invalid dbprogs?? > > > Hello, > > I cannot reproduce the error. When I choose a cursor name > like 'sp_rptOffeneAnfragen_ALL_Kunde_AAABBBCCCDDD' with len > 32 > SQL Studio throws the error as expected: > > ---- Error ------------------------------- > Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed > General error;-2014 POS(6) Identifier too long > call > sp_rptOffeneAnfragen_ALL_Kunde_AAABBBCCCDDD(38,'2003-01-01', > '2004-02-06', > 'D-%', 'DF%', 'DK%', 'S-%', 'SF%', 'SK%', '', 'MF%', 'MK%') > > > > Regards > Wolfgang > > > > -----Original Message----- > From: "H�bschen, Peter" [mailto:[EMAIL PROTECTED] > Sent: Freitag, 6. Februar 2004 10:42 > To: Mailingliste MaxDB (E-Mail) > Subject: Error in SQLStudio by execution of invalid dbprogs?? > > > Hello, > > I've created some dbprogs which return a cursor with > len(Cursorname) > 32 in > SQLStudio without any error. Now I know this length is > invalid, but I've run > into a strange problem. If I called such a dbprog from a > Pass-Through-Query > from Access I got 'Identifier too long' (that's the correct > error message, > even if the position didn't gave me any clue). So I called my > dbprog through > a SQL Dialog in SQLStudio and didn't get any error. Only a "Statement > successfully executed" and no resulttable. > After I find that my length of the Cursorname was invalid > everything worked > as expected. > > So for me this was/is an annoying bug. > > Here are my systemspecs: > - SQLStudio 7.4.3.28 on Windows 2000 > - SAPDB 7.4.3.30 on a RH9 Box. > - ODBC-Driver: 7.4.3.27 > > Kind regards > Peter > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
