Thanks Gary. I'm happy to take advice from COM hackers as well as COM
experts.
Unfortunately it didn't help.
The problem seems to be that it can't find the method, rather than there
being a problem with the method parameter.
For instance, if I change the call from
<cfset oMsg = oMsgMan.CreateMessage(oMsgType)>
to
<cfset oMsg = oMsgMan.Connect(oMsgType)>
it then gives the following error, which I understand as that method does
not take any parameters.
An exception occurred when accessing a Com object field.
The problem seems to be related to the subgroups shown via OLEView.exe for
the AHC.Messenger object. The IDispatch ones are accessible (e.g. connect),
the IHCMessageManager methods (e.g. CreateMessage) seem to need some other
syntax to get to them.
Phil.
----- Original Message -----
From: "Gary Menzel" <[EMAIL PROTECTED]>
To: "CFAussie Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 25, 2003 2:59 PM
Subject: [cfaussie] Re: Converting VB com object calls to CF
> > Any com experts able to help me out?
>
> I'm not a COM "expert" (either of the VB kind or the CF kind) so I can't
> gaurantee this will work, but it may be related to how the COM method's
> parameter has been declared in that function.
>
> I seem to remember a comment somewhere in regard to using COM with CF
> that, if you have a method parameter that takes a REFERENCE, you have to
> pass over the NAME of the variable in quotes and not the variable itself.
> I am guessing the bridge uses some type of mechanism similar to
> Caller.objectname to pass things by reference to COM calls.
>
>
> Gary Menzel
> Web Development Manager
> IT Operations Brisbane -+- ABN AMRO Morgans Limited
> Level 29, 123 Eagle Street BRISBANE QLD 4000
> PH: 07 333 44 828 FX: 07 3834 0828
>
>
>
>
> If this communication is not intended for you and you are not an
authorised recipient of this email you are prohibited by law from dealing
with or relying on the email or any file attachments. This prohibition
includes reading, printing, copying, re-transmitting, disseminating, storing
or in any other way dealing or acting in reliance on the information. If
you have received this email in error, we request you contact ABN AMRO
Morgans Limited immediately by returning the email to
[EMAIL PROTECTED] and destroy the original. We will refund any
reasonable costs associated with notifying ABN AMRO Morgans. This email is
confidential and may contain privileged client information. ABN AMRO Morgans
has taken reasonable steps to ensure the accuracy and integrity of all its
communications, including electronic communications, but accepts no
liability for materials transmitted. Materials may also be transmitted
without the knowledge of ABN AMRO Morgans. ABN AMRO Morgans Limited its
directors and employees do not accept liability for the results of any
actions taken or not on the basis of the information in this report. ABN
AMRO Morgans Limited and its associates hold or may hold securities in the
companies/trusts mentioned herein. Any recommendation is made on the basis
of our research of the investment and may not suit the specific requirements
of clients. Assessments of suitability to an individual?s portfolio can
only be made after an examination of the particular client?s investments,
financial circumstances and requirements.
>
>
> ---
> You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to
[EMAIL PROTECTED]
>
> MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
> http://www.mxdu.com/ + 24-25 February, 2004
>
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004