ODBC vs ADO incorrectly defining fields

[mavrick5au]

Hello,

I have a crystal report written in v9 which I can upgrade to XI if necessary.

The report prints our delivery dockets, invoices, credit notes, etc, all formatted, company logos etc.

I now have the requirement to add a QR code to the delivery docket.

The delivery docket uses ODBC to connect to SQL which has been working successfully for over 20 years. The field containing the QR code is a blob field in a separated DB, but on the same server but with the same record key so I can link them together.

However, when I add in the new table to the docket via ODBC, the QR code field is showing as a string field in the definitions (in SQL, the field is a defined as varbinary). But if I add the table to the docket using ADO connection, then the field is showing as a blob in crystal and I can just add the field to the docket and it displays correctly.

But.... It is prompting me for login details for the ADO connection every time I run the report manually. We use trusted connections for both and the ODBC connection works fine. When I run the report through our application, it comes up with a "login failed" error.

How can I get this to work correctly without purchasing either a barcode font so I can convert the field showing as a string back to a QR Code or upgrading crystal reports. Alternatively, how can I make the ODBC connection recognise the field type correctly.

Any advice would be welcome. I have to have this up and running by the end of June.

Cheers,

Mark

 

[dgillz]

Click on database, verify database and see if it updates the field type.

 

[mavrick5au]

Click on database, verify database and see if it updates the field type.

Nope, still shows it as a string of 0 length.

 

[Kim296]

Can you place the QR code directly onto the report? Or, does the QR change based on the type of field?