|The stupid question is the question not asked|
Same Script different OSby Jonathan (Curate)
|on Nov 02, 2004 at 09:50 UTC||Need Help??|
Jonathan has asked for the wisdom of the Perl Monks concerning the following question:
This script runs fine on Solaris...
and as expected returns
However, running the same script on the WinXP cmd shell the script bombs with one of those annoying Windows popups about telling microsoft the problem.
How can I trap my SQL failure in WinXP? I've tried using eval but that makes no difference.
I downloaded the DBI and the Oracle DBD from here following their instructions and used their DBI version instead of the ActiveState one but still no joy.
Finally got it working.
As above the ActiveState DBI package is not compatible with the esoftmatic.com Oracle DBD build but by stumbling around in my usual chaotic manner I chanced upon the combo of DBI and DBD versions that work.
Apologies for wasting everyones time.