I have not been happy with COM support under MX so far. It seems much slower for one thing. Also I found the following problems:
* I have a VB6 COM which sets a property with type currency. When I read the property in CF5 it works fine. When I read it with MX, the value is 1000 times to high. If I change the property to double, it works under MX. * I had to make all my variables explicitly pass By Value in my VB program. Otherwise, I had to use different syntax to pass in the variables - something I want to avoid at this point so my code will run in both environments. * I have some properties defined as string types. If I attempt to set the property to a blank (whether hard coded or through a variable), I get an error. All of this worked under CF5. Add to that, it is much slower loading the COM. > -----Original Message----- > From: Lewis Sellers [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 3:39 PM > To: CF-Talk > Subject: CFMX and COM > > > Can I say MX's COM support sucks? I'm going to anyway. Almost nothing > I have COM-wise that was developed for ASP and CF 3 - 5 works under > it. :) > > Grr. > > > --min > > ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
