RE: CF + COM

2002-11-21 Thread Adrocknaphobia Jones
Chris, I haven't found much on the topics of CF and COM outside of cfComet. I agree though, cfComet is pretty scarce on helpful information if you aren't working with Office or PDF. I do know that the general sentiment is NOT to use COM in CFMX. Functionally I've gotten a number of COM objects

RE: CF + COM

2002-11-21 Thread Chris Alvarado
. -chris.alvarado [ application developer ] 4 Guys Interactive, Inc. http://www.4guys.com We create websites that make you a hero. -Original Message- From: Adrocknaphobia Jones [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 10:11 AM To: CF-Talk Subject: RE: CF + COM Chris, I

Re: CF + COM

2002-11-21 Thread jon hall
Why not use their new XML API? The ShipAPI stuff is really nasty imho. -- jon mailto:[EMAIL PROTECTED] Thursday, November 21, 2002, 11:59:32 AM, you wrote: CA Im not using FedEX's Java API because CA 1) We are not using CFMX as of yet and 2) because my knowledge of Java CA is extremely

RE: CF + COM

2002-11-21 Thread Chris Alvarado
Guys Interactive, Inc. http://www.4guys.com We create websites that make you a hero. -Original Message- From: jon hall [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 3:21 PM To: CF-Talk Subject: Re: CF + COM Why not use their new XML API? The ShipAPI stuff is really nasty

RE: CF COM

2000-07-14 Thread Campbell Morton
Steve Bernard wrote: I'm not sure exactly what you mean by registering the component with NT's Scheduler but, if you mean that you have the component started by the Scheduler Service be aware that the component will be running under the System Account. This will give the component, and thereby

RE: CF COM

2000-07-13 Thread Zachary Bedell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To the best of my knowledge (and COM is my friend, so I think this is accurate), you can't possibly have a .exe component run inproc. Under Windoze, ALL EXEs run as their own process and ALL DLLs run in somebody else's process. As far as I

RE: CF COM

2000-07-13 Thread Steve Bernard
I'm not sure exactly what you mean by registering the component with NT's Scheduler but, if you mean that you have the component started by the Scheduler Service be aware that the component will be running under the System Account. This will give the component, and thereby and script calling it,