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.
I would check your stored procedure and make sure that isnull(@customer_no, 0) = 0 is handled. Also remember to make sure all client pcs have ODBC driver installed as well as servers (I believe on newer servers it comes pre-installed).
Thanks Lou Ann
It's there. All clients including my own that were tested recently installed ODBC 13.1. Something in the ODBC layer is having issues.