CF5 to MX7 Problem: Sybase Stored Proc's dont work right

[DaveF67]

Has anyone else had this problem?
Stored procedures that worked with CF5 work differently in MX7.

Some work part of the time, others not at all.

We are using Solaris.

[sdupre]

Get the 3.4 drivers from /support/coldfusion and see if those solve your
problem. If not, email me an example. This is the only one I know of that's
blatant. None that are intermittent as you describe.

Sybase

* 57539 - Qualifying stored proc name with DB name throws error

Stephen Dupre
Macromedia QA

[DaveF67]

Thanks.
Here is the quick link to the 3.4 Drivers [url]http://www.macromedia.com/go/1a3c2ad0[/url]

[DaveF67]

DAMIT... I spoke too soon.....

Still Get an Error....
Both CF5 and MX7 point to the same database...

On the CF5 Server, this works great:

awards_list (Records=60, Time=416ms)
SQL =
exec awards_search 'ACTIVE', 'Chemistry', null, null, null, null

on the MX7 Server, when we would run the query above (WITH THE ORIG DRIVERS)
we would get ALL THE RECORDS BACK.

Now with the 3.4 drivers the stored proc throws an error... (BTW. the error
now being thrown is identical to the error with the original drivers if the
user entered two search terms i.e. 'ACTIVE' 'Chemistry Division',
null,null,null

Error Executing Database Query.
[Macromedia][Sybase JDBC Driver][Sybase]Invalid column name '%CHEMISTRY%'.

exec awards_search 'ACTIVE', 'chemistry', null, null, null, null

BTW...
This stored Procedure DOES WORK as follows:

exec awards_search 'ACTIVE', null, null, null, 91, null

It just will not take a search term as the second parameter :(


DAMIT!