Hi Russell;

   Have you tried this feature while connecting to ASE using PB's "native" client instead?

IE: SQLCA.dbms = "ASE"

Regards ... Chris

Thanks for your reply, Chris.

I ran a trace - below is portion of the log I determined to be associated with the syntaxFromSql() call. It doesn't really give me any clues, but I don't speak whatever language this is. Maybe you or someone out there will have some amazing insight.

Next I might try the lower-level trace.

(08BD3048): PREPARE:
(08BD3048): select moniker from pending_trade where 1=2(DBI_PREPARE) (3.136 MS / 775.584 MS)
(08BD3048): DESCRIBE:(DBI_DESCRIBE) (0.021 MS / 775.605 MS)
(08BD3048): name=moniker,dsntype=char,len=7,type=CHAR,pbt=1,dbt=1,ct=0,prec=6,scale=0
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_GET_FROM_BEFORE) (0.000 MS / 775.605 MS)
(08BD3048): (DBI_VALIDATE_IDENT) (0.000 MS / 775.605 MS)
(08BD3048): GET EXTENDED ATTRIBUTES: TABLE=pending_trade OWNER=dbo(DBI_COMPLETE_TABLE_INFO) (9.980 MS / 785.585 MS)
(08BD3048): (DBI_PARSE_COLLIST) (0.000 MS / 785.585 MS)
(08BD3048): (DBI_VALIDATE_IDENT) (0.000 MS / 785.585 MS)
(08BD3048): (DBI_VALIDATE_HASH) (6.214 MS / 791.799 MS)
(08BD3048): (DBI_FORMAT_HASH) (6.370 MS / 798.169 MS)
(08BD3048): (DBI_EDITSTYLE_HASH) (6.635 MS / 804.804 MS)
(08BD3048): (DBI_DESCRIBE_OPTIMIZED) (0.000 MS / 804.804 MS)
(08BD3048): (DBI_CASE_SENSITIVE) (0.000 MS / 804.804 MS)
(08BD3048): (DBI_DW_COL_DICT) (6.566 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_TERMINATOR) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_GET_FROM_BEFORE) (0.000 MS / 811.370 MS)
(08BD3048): (DBI_VALIDATE_IDENT) (0.000 MS / 811.370 MS)
(08BD3048):  UNIQUE KEY CHECK: TABLE=pending_trade OWNER=dbo USER=dbo(DBI_UNIQUE_KEY) (11.892 MS / 823.262 MS)
(08BD3048): YES, unique key found

Here's some important information:
    https://docs.microsoft.com/en-us/sql/t-sql/statements/set-ansi-nulls-transact-sql?view=sql-server-2017

   "In a future version of SQL Server, ANSI_NULLS will be ON and any applications that explicitly set the option to OFF will generate an error. Avoid using this feature in new development work, and plan to modify applications that currently use this feature."


   https://knowledgebase.progress.com/articles/Article/6334

   In your application, you can restore the default Sybase behavior for a connection in the following ways:

Use the Initialization String option to specify the SQL command set ANSINULL off. For example, the following
connection string ensures that the handling of NULL values is restored to the Sybase default for the current connection:

DSN=SYB TABLES;DB=PAYROLL;IS=set ANSINULL off

Explicitly execute the following statement after the connection is established:

SET ANSINULL OFF

Hope this helps,

Olan

Hi Russ;

   Hmmmm .. not much to go on in that trace - unfortunately.

   I wonder if the best workaround is to just turn off the setting after each "SyntaxFromSQL" command is executed? From what I have read thus far, its the Sybase-ODBC driver that is the one that sets this option ON at connect time? The other option of course, is to use the native ASE driver.

FYI:  EXECUTE IMMEDIATE "Set ANSI_NULLS OFF" 

  Another thought: What about using a 2nd Transaction Object connected to ASE just for the SyntaxFromSQL command's use?

HTH

Regards ... Chris

Thanks for your replies Chris & Olan,

Just to clarify, I am using the Sybase ODBC driver, not the MS driver.

I have tried explicitly setting ansinull off (execute immediate "set ansinull off";), but sqlFromSyntax resets it to on.

Of course I am considering issuing the command after each sqlFromSyntax, but there are over 60 instances of it our application. (Or I'll convince the programmers around here to stop using "=null"!)

Anyway, thanks for your assistance. I am several weeks into trying to get this application to work with ODBC, and I'm hitting one roadblock after another. If anyone has any general advice for using ODBC with PB, I'd be grateful to hear about it.

Thanks,

Russell