Receive 'Invalid Column Name' Message After Starting to Use Alphabetic Document Numbers
Version: 8.5 & Up
Q - I just started to use alphabetic order numbers in Elliott 8.5, and my FedEx shipping manifest machine is giving me a message :
The Following Errors Occured While Tring to Process a SQL Request
SHIPPING ERROR NUMBER: 1526
SHIPPING ERROR MESSAGE:
Connectivity error: [Pervasive][ODBC Client Interface][LNA][PSQ:][SQL Engine]Invalid column name: 'AA0238'.
ODBC ERROR MESSAGE:
[Pervasive][ODBC Client Interface][LNA][PSQ:][SQL Engine]Invalid column name: 'AA0238'.
ODBC SQL STATE: S0022
ODBC CONNECTION HANDLE: 1
A - This is because their applications treated Elliott’s order number as numeric in the past and used a SQL statement like the following to retrieve Elliott’s order data:
SELECT * FROM CPORDHDR WHERE ORDER_NO = AA0238If the order number is still numeric, then this would work. But since the ORDER_NO is alphabetic now, you will get an error message from PSQL like:
<<<<<<<<<<<<<<<<<<<<<<<<
SELECT * FROM CPORDHDR WHERE ORDER_NO = AA0238
[LNA][PSQL][SQL Engine]Error in expression: AA0238
[LNA][PSQL][SQL Engine]Invalid column name: 'AA0238'.
>>>>>>>>>>>>>>>>>>>>>>>>
To fix this error, you need to ask your FedEx technician to put the order number in single quotes like:
SELECT * FROM CPORDHDR WHERE ORDER_NO = ‘AA0238’
This type of integration with Elliott is at the third party’s discretion, and we can’t really predict if they will continue to work when you start using alphabetic order numbers in 8.5. The only way to find out ahead of time is to test in a sample environment before you convert.
SELECT * FROM CPORDHDR WHERE ORDER_NO = ‘AA0238’
This type of integration with Elliott is at the third party’s discretion, and we can’t really predict if they will continue to work when you start using alphabetic order numbers in 8.5. The only way to find out ahead of time is to test in a sample environment before you convert.
EMK