The solution (well msft sql server anyway and assuming that is an
unfixable dbi issue) is using the isnull function.
Select isNull(FieldNameForNullField, 'Value you want it to be if it's
null')
>From randomtable
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Beha
I have a line of code that gives an error. This line of code:
my $dll = new Win32::OLE("Artwork.db.api");
Gives this error:
Win32::OLE(0.1403) error 0x800401f3: "Invalid class string" at (eval 34)
line 1
To me this indicates that the dll is not registered correctly with
windows. That is n
->How much did you copy and how did you go about it? It sounds like you
partially overwrote the ->second computer's copy of Win32::OLE with a
different version. Try using PPM to reinstall ->Win32::OLE.
I didn't copy any of the perl stuff. I installed a fresh copy of perl
and then used PPM to i
Here's the situation. I have some perl code running fine on one windows
box. I moved it to another box and installed all the appropriate
modules.
I am now getting the following message in my error log:
Win32::OLE object version 0.1702 does not match $Win32::OLE::VERSION
0.1403 at C:/Perl/lib/Dy
>I have a perl program that sends email via win32-ole cdo.
>I started having the 2 dialogs since "upgrading" :-( to outlook 2003.
>The dialogs read:
Here's the situation. If I remember correctly (and I probably don't)
there are three normal ways to use MAPI to send email.
1. Outlook object M
>There's no way that I'm going to take the name of every function I
>ever write and search the Perl docs to see if it's a reserved name.
But don't you just get that feeling that maybe reset might be a fxn of
note? You could always preface your functions w/ something...may be
something that indi
s an OLE String
reference initialized as ''
Now you just use your line of code
$step->GetExecutionErrorInfo($VT_ErrorCode, $VT_Source, $VT_Description);
after the execution you can look at the error by using the Value function of
the variant as in...
print $VT_Description->
