Thanks. I had already tried the following:
- OLE::Warn is set to 3
- ran with -w
I tried the Initialize(OLEINITIALIZE) as you suggested but it didn't change
the behavior. Given your explanation in the notes I didn't expect it to (you
suggested that the program would hang, in this case it just exits without
nary a word).
FWIW this class object does use IDispatch (I assume that's required).
Regards,
Charlie
-----Original Message-----
From: Jan Dubois [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 15, 2000 8:32 PM
To: Charlie Fineman
Cc: Perl-Win32-Users Mailing List
Subject: Re: Win32::OLE->new silently killing perl process
On Mon, 15 May 2000 18:46:37, "Charlie Fineman" <[EMAIL PROTECTED]>
wrote:
>I'm trying to integrate to an ISV's COM interface. When I do a
>"GetActiveObject" it returns undef as expected. When I try to do a
>"new" on the class, perl churns for a moment then exits! Not a word... it
>just exits. Now if I pass a bogus name to the new method, it fails with
>the expected message. I've also succesfully interacted with the COM
>interface via a VB script.
>
>Is there any way to get more information from PERL about what is going on?
Run your program with "perl -w" and see if you get an OLE error message.
It is also possible that the object in question needs "full" OLE support,
like th4e MAPI.Session object. Look up the documentation for
Win32::OLE->Initialize() and try that too.
-Jan
>The version I'm running is:
>
>Binary build 518 provided by ActiveState Tool Corp.
>http://www.ActiveState.com
>Built 13:14:00 Jun 24 1999
>
>and it's not got debugging compiled in.
>
>Any ideas?
>
>---
>You are currently subscribed to perl-win32-users as: [EMAIL PROTECTED]
>To unsubscribe, forward this message to
> [EMAIL PROTECTED]
>For non-automated Mailing List support, send email to
> [EMAIL PROTECTED]
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
