I'm using PB 7.0.2 build(8017) and Jaguar 3.5 with EBF1.
I have personally reportet this bug to sybase support before:
When my app submit incorrect syntax to ASE or call stored procedure/triggers
errors, the SQLCA.Sqlcode and SQLCA.sqldbcode are still valued to 0. Error
messages are logged into the srv.log file of Jaguar correctly but I can't
the error in the code.
Support told me that the problem should be fixed by uppgrading to
Jaguar 3.5 with EBF1 and PB 7.02 build 8011 or higher.
We have uppgraded and know the PB-klient "crashed" and we recieve the
PB-runtime error: invalid reference at line 1 (R 0002).....(Tried using
both native interface and ODBC)
We are using PB-NVO on Jaguar CTS.
My company is starting systemtest on monday 13.3.2000 and if we not have the
solution to this problem by tomorrow we are stuck with PB 7.0.1 and EAS 3.01
using ODBC to connect to an SYBASE ADAPTIVE SERVER ENTERPRISE DATABASE
Because EAS 3.01 and ODBC have no problem with detecting errors from
Can anyone help us with this problem! I willl also contact support tomorrow,
but because of short time left i hope that somebody else have expirenced
this problem and know the solution to the problem.
Because og all the problems we have experienced with jaguar and dynamo, we
will not risking uppgrading EAS 3.01 after starting the system test.
From: "Andre Solstrand" <firstname.lastname@example.org>
Subject: Urgent! - SYJ native interface and SQL return codes
Date: Thu, 9 Mar 2000 23:02:23 +0100
X-Newsreader: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
NNTP-Posting-Host: ti01a68-0045.dialup.online.no 220.127.116.11
Xref: forums-1-dub sybase.public.easerver:26745
Article PK: 157734
From: "Ashish Mahajan" <ash@NOSPAM.com>
Subject: Re: Urgent! - SYJ native interface and SQL return codes
Date: Fri, 10 Mar 2000 10:04:57 -0500
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: pikachu.sybase.com 18.104.22.168
Xref: forums-1-dub sybase.public.easerver:26688
Article PK: 157687
The problem with SQLCA not reporting errors has been fixed recently. I
assume that support gave you the correct build no.s
With the upgrade you are facing new problems... To me it looks like the
client proxies need to be regenerated... See if that works