We started using ODBC18 driver with crystal reports runtime and memo fields are cut down to 255 chars. Designer works fine but runtime truncates. Is this a known issue and is ODBC18 supported by crystal runtime?
Your Options are to set database location to OLE DB or use ODBC 17 client.
I recall discussing this with R&D but I don't recall the reasons why ODBC can't be made to work. Often there are differences between ODBC and OLE DB clients, sometimes ODBC work and sometimes OLE DB work... sometimes they both work, it appears ODBC 18 is not 100% compatible...
In CR 9 when R&D rewrote a huge chunk of the code they separated CR's database component into a separate dll because CR had so many "hacks" to "fix" client bugs they decided it's no longer a CR issue, if there are bugs in the Clients the makers had to fix them, it's not a CR issue.
SP 37 will not likely fix the issue but still recommend you upgrade to take advantage of the security updates etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.