• Replies 4 replies
  • Subscribers 338 subscribers
  • Views 236 views
  • Users 0 members are here
Related

V15.0.5 issues with new ODBC in Master.ini

Troy Nelson
$organization

Hello everyone,

I'm having a heck of a time with our custom headers in V15.0.5. When using OLEDB in the master ini, everything is coming through correctly including customer 0 for ticketing. When moving away from OLEDB into ODBC (Driver 13.1), customer 0 will refuse to load and kill the header. All of the customer 0 fields have been accounted for according to infomaker field types. 

I get a restricted attribute violation warning or a cast error relating to empty customer 0 fields. Has anyone encountered this? For now, I reverted back to OLEDB and things are good to go. 

Parents
  • $organization

    This is most likely to a NULL value that is not typed in the SQL.  The most notable culprit is datetime.  If you have a resultset like the following below for customer_no 0 in the custom header procedure (most likely an old derivative of AP_DONOR_HEADER1):

    SELECT null, null, null

    If this is the case, and say column three is a date or datetime, try changing that column to:

    CONVERT(datetime, NULL)

    instead of just

    NULL

    This allows the ODBC driver to properly type the value.  It may seem trivial, but the ODBC connection is a little more restrictive in that manner.

Reply
  • $organization

    This is most likely to a NULL value that is not typed in the SQL.  The most notable culprit is datetime.  If you have a resultset like the following below for customer_no 0 in the custom header procedure (most likely an old derivative of AP_DONOR_HEADER1):

    SELECT null, null, null

    If this is the case, and say column three is a date or datetime, try changing that column to:

    CONVERT(datetime, NULL)

    instead of just

    NULL

    This allows the ODBC driver to properly type the value.  It may seem trivial, but the ODBC connection is a little more restrictive in that manner.

Children