TD5.1SP6 runtime error calling SQL server stored procedures

[guptabroos]

Hi,
I'm bringing a large inhouse app from version 2.1 to 5.1. It compiles OK but calling stored procedures fails. The error generated says SQL parser doesn't agree with the syntax. The same happens with all proc calls.
Here's an example of the SQL string in the call to odrprepareproc -
StrProc = '{ call sp_smart_findstudent (91, null, 'l%', null, null, null, null, null, null, 'N', 'N' )}'

Here's the offending command -
{ call sp_smart_findstudent (91, null, 'l%', null, null, null, null, null, null, 'N', 'N' )} : ... bindvars as required
And the error details -
Error: Invalid character
Reason: The SQL parser has determined an invalid character while
searching for quoted strings, numbers, keywords, and
identifiers.
Remedy: Verify that the SQL statement is correctly stated and that no
invalid characters are present.
Position Unknown

The code has been running for ten years. The proc call runs fine in the database when the parentheses are removed.
Is this known behaviour? Is there a fix on the way? Would I be better off going to 4.2 for now?

[Ana Paula Bonani]

Hello,

Based on your description below I couldn't find any reported issues currently open in our internal system.

It would really help finding the cause if you could provide a small working application demonstrating the problem. The problem could be specific to datatypes or the string length therefore my request.

That's the only thing I can imagine for now and I'd appreciate the reprocase to help us work on it.

Thanks for your report, let us know please.

Regards,

[guptabroos]

Hi Ana,
Thanks for reply.

App attached which replicates the problem. All database logon details are in app startup. Using SQL server authentication to SQL7 ( a bit old yeah...)
The stored proc code is

Code: Select all

create procedure sp_Proctest_ContactType as
select contacttypeid, description from contacttype

Hope that's all you need


Cheers
Steve

[Ana Paula Bonani]

Thank you very much, Support will work on reproducing it and get back to you if we have any questions.

Best Regards,

[guptabroos]

Hi Ana,
SOLVED

Updated library from odbsal32.dll to odbsal32.apl after looking at sample app.

Cheers
Steve

[Ana Paula Bonani]

That's great news!

Glad it's solved and appreciate the feedback!

Regards,

[the]

What do you mean by upgrading odbsal32.dll to odbsal32.apl?