I'm sure there's some sort of a datatype issue. Both vbscript and cfml use variants,
but I'm sure there's some
differences in how they are passed. Have you tried
<CFSET strWDDX_Retval = objContact.Add("#strWDDX_Input#")>
or in your vb code, CStr() your method params.
Other than that, it's probably something extra you'll need to do in your vb code, and
while it's a CF-related
issue, I'm sure people will start throwing their kitchen garbage at yoiu when you
start posting VB code to the
list : - )
--
Billy Cravens
HR Web Development, Sabre
[EMAIL PROTECTED]
zCF Talk wrote:
> I have a com object that I have created and tested on Windows 2000 using CF
> v5b3. It works great. Awesome.
>
> So I recompile the object on a Windows NT box, and install it on the Windows
> NT server. ASP can access the object without a hitch, but in the following
> code snippit, the 'CFSET' fails with the very intuitive "Object variable or
> With block variable not set".
>
> How do I go about debugging this application? I know that the object is
> instantiated, because if I try accessing a method that doesn't exist, I get
> the following COM error: "COM error 0x80020006. Unknown name"
>
> So how do go about debug this component? It takes and is supposed to return
> a WDDX packet.
>
> <CFFILE ACTION="READ" FILE="e:\inetpub\sites\membdb\source.xml"
> VARIABLE="strWDDX_Input">
> <CFOBJECT TYPE="COM" NAME="objContact" CLASS="UDB_Contact.Business"
> ACTION="CREATE">
> <CFSET strWDDX_Retval = objContact.Add(strWDDX_Input)>
> <CFFILE ACTION="WRITE" FILE="e:\inetpub\sites\membdb\result.xml"
> OUTPUT="#strWDDX_Retval#" ADDNEWLINE="Yes">
>
> ---
> Daniel Dewey |"Tell me, and I'll forget.
> Systems Developer | Show me, and I may not remember.
> MCP (NT srvr/wkstn/eprise) | Involve me, and I'll understand."
> [EMAIL PROTECTED] | - Native American Proverb
> http://www.pobox.com/~dewey | 610-868-1421, x115
> The National Association of Colleges and Employers
>
> These opinions are mine, and may not be the same as my employer
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 11:00 AM
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> You can use either ysntax but you have to add a reference to the ado or dao
> library in the project in the sam way as you do for a vb project. Go to
> tools references and choose one or both.
>
> -----Original Message-----
> From: Will Swain [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 15:41
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> Well, thats what I thought too, to be honest, but a more experienced VBA
> developer than me said the errors were due to this difference between DAO
> and ADO.
>
> I will try using ADO syntax and see if that works.
>
> Thanks for all your input Andy
>
> Will
>
> -----Original Message-----
> From: Andy Ewings [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 15:15
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> If you are using VBA you should be able to choose which connection method
> you use without any problem. As far as I can remember the code in the
> module/class you are creating is separate from the mdb.....I'm not sure what
> you mean when you say "in an ADO database". The database is just a database
> - ADO is purely used as a method of interogating it. As I said earlier -
> it's been a while since I used Access/VBA so may be way off!
>
> ------------------------------------------------------------------
> Andrew Ewings
> Project Manager
> Thoughtbubble Ltd
> http://www.thoughtbubble.net
> ------------------------------------------------------------------
> United Kingdom
> http://www.thoughtbubble.co.uk/
> Tel: +44 (0) 20 7387 8890
> ------------------------------------------------------------------
> New Zealand
> http://www.thoughtbubble.co.nz/
> Tel: +64 (0) 9 488 9131
> ------------------------------------------------------------------
> The information in this email and in any attachments is confidential and
> intended solely for the attention and use of the named addressee(s). Any
> views or opinions presented are solely those of the author and do not
> necessarily represent those of Thoughtbubble. This information may be
> subject to legal, professional or other privilege and further distribution
> of it is strictly prohibited without our authority. If you are not the
> intended recipient, you are not authorised to disclose, copy, distribute, or
> retain this message. Please notify us on +44 (0)207 387 8890.
>
> -----Original Message-----
> From: Will Swain [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 15:10
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> Cheers Andy,
>
> Its just I'm writing some VBA and gettings errors which I think are caused
> by using DAO syntax in a ADO database, but that doesn't make too much sense
> to me??
>
> Cheers
>
> Will
>
> -----Original Message-----
> From: Andy Ewings [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 14:41
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> Yeh I think so. My use of DAO/ADO/RDO was through VB. Just used each to
> create connection and query objects and run them against the db. I'm not
> sure if you can choose which you want to use directly in Access although I
> haven't used Access for a While and things may have changed in 2000!)
>
> ------------------------------------------------------------------
> Andrew Ewings
> Project Manager
> Thoughtbubble Ltd
> http://www.thoughtbubble.net
> ------------------------------------------------------------------
> United Kingdom
> http://www.thoughtbubble.co.uk/
> Tel: +44 (0) 20 7387 8890
> ------------------------------------------------------------------
> New Zealand
> http://www.thoughtbubble.co.nz/
> Tel: +64 (0) 9 488 9131
> ------------------------------------------------------------------
> The information in this email and in any attachments is confidential and
> intended solely for the attention and use of the named addressee(s). Any
> views or opinions presented are solely those of the author and do not
> necessarily represent those of Thoughtbubble. This information may be
> subject to legal, professional or other privilege and further distribution
> of it is strictly prohibited without our authority. If you are not the
> intended recipient, you are not authorised to disclose, copy, distribute, or
> retain this message. Please notify us on +44 (0)207 387 8890.
>
> -----Original Message-----
> From: Will Swain [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 14:30
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> Thats how I saw it too.
>
> As I'm new to this side of things, can you tell me, is it possible to use
> both in an Access DB?
>
> Cheers
>
> Will
>
> -----Original Message-----
> From: Andy Ewings [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 11:03
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> Nick has got a point that there is no guarantee of support for DAO (or RDO
> come to that) but I can't see MS dropping uspport for something that ties in
> so closely with a db that is so widely used
>
> ------------------------------------------------------------------
> Andrew Ewings
> Project Manager
> Thoughtbubble Ltd
> http://www.thoughtbubble.net
> ------------------------------------------------------------------
> United Kingdom
> http://www.thoughtbubble.co.uk/
> Tel: +44 (0) 20 7387 8890
> ------------------------------------------------------------------
> New Zealand
> http://www.thoughtbubble.co.nz/
> Tel: +64 (0) 9 488 9131
> ------------------------------------------------------------------
> The information in this email and in any attachments is confidential and
> intended solely for the attention and use of the named addressee(s). Any
> views or opinions presented are solely those of the author and do not
> necessarily represent those of Thoughtbubble. This information may be
> subject to legal, professional or other privilege and further distribution
> of it is strictly prohibited without our authority. If you are not the
> intended recipient, you are not authorised to disclose, copy, distribute, or
> retain this message. Please notify us on +44 (0)207 387 8890.
>
> -----Original Message-----
> From: DeVoil, Nick [mailto:[EMAIL PROTECTED]]
> Sent: 26 April 2001 10:58
> To: CF-Talk
> Subject: RE: slightly OT ADO vs DAO
>
> DAO is a dead-end. ADO is more future-proof.
>
> Nick
>
> -----Original Message-----
> From: Will Swain [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 10:51 AM
> To: CF-Talk
> Subject: slightly OT ADO vs DAO
>
> Hi all,
>
> I know this is slightly OT, but I wanted to get peoples opinions about ADO
> vs DAO in ACCESS2000. It's not something I'd looked at before to be honest,
> so was looking for general feedback, info on each etc,
>
> TIA
>
> Will
>
> **********************************************************************
> Information in this email is confidential and may be privileged.
> It is intended for the addressee only. If you have received it in error,
> please notify the sender immediately and delete it from your system.
> You should not otherwise copy it, retransmit it or use or disclose its
> contents to anyone.
> Thank you for your co-operation.
> **********************************************************************
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
