Solved!
Thank you for the reply.
After running an ODBC debugger and closely examining the ODBC logs, it appears that there is a part of 'their' driver that doesn't like mapped drives. Frankly, Neither do I.
How I managed to not notice that this ODBC DSN was set up using a mapped drive is beyond me. I know better.. must have been a slip in sanity.
Thank you for pointing me in the right direction!
Regards
Victor
In reply to Re^2: Result too large using DBI::ODBC
by vshortt
in thread Result too large using DBI::ODBC
by vshortt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |