Mon Jan 24 18:18:29 2011: Request 65052 was acted upon.
Transaction: Correspondence added by j...@activestate.com
Queue: Win32-OLE
Subject: RE: [rt.cpan.org #65052] Cannot create ADODB.Connection object
under Cygwin
Broken in: 0.1709
Severity: Important
Owner: Nobody
Requestors: rkito...@cpan.org
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=65052 >
On Mon, 24 Jan 2011, rkito...@cpan.org via RT wrote:
> On 1/24/2011 3:59 PM, j...@activestate.com via RT wrote:
> > Could you try running Cygwin Perl from cmd.exe instead of bash? I've
> > found several references with Google that certain COM components (WMI,
> > ADODB) cannot be instantiated when the program is started from bash,
> > but work fine when started from cmd.exe.
[...]
> That is indeed the case.
>
> There are a whole bunch of warnings, but the object is returned:
Those warnings are normal. Dumping the whole connection object will
try to fetch several properties that aren't initialized in the closed
state of the object. You get the same warnings with regular Perl.
I'm going to close this bug, as it seems to be neither an issue with
Perl nor with Win32::OLE but just with the way the Cygwin bash shell
sets up the environment, and therefore should be fixed there.
Cheers,
-Jan
