Cold Fusion requires this to be able to use a COM object. My question for all you COM folks is does VFP meet these requirements.

ColdFusion is an automation (late-binding) COM client. This implies that the COM object has to support the IDispacth interface, and that arguments for methods and properties be standard automation types. Since ColdFusion is a typeless language, it uses the object's type information to correctly set up the arguments on call invocations. Any ambiguity in the object's data-types could lead to unexpected behavior.

It is important to use server-side COM objects in ColdFusion, that is, they should not have a graphical user interface. If you invoke an object with a graphical interface in your ColdFusion application, a window for the component might appear on the Web server desktop, not on the user's desktop. This could tie up ColdFusion server threads and result in further Web server requests not being serviced.

ColdFusion can call Inproc, Local, or remote COM objects. The attributes specified in the CFOBJECT tag determine which type of object is called.

Requirements for COM
To make use of COM components in your ColdFusion application, you need at least the following items:

The Microsoft OLE/COM Object Viewer, available from Microsoft. It is a handy tool for viewing registered COM objects.
The COM objects you want to use in your ColdFusion application pages. These are typically DLL or EXE files. These components should allow late binding, that is, they implement the IDispatch interface. Object Viewer allows you to view the object's class information so that you can properly define the CLASS attribute for the CFOBJECT tag. It also displays the object's supported interfaces, which allows you to discover the properties and methods (for the IDispatch interface) of the object.


***
Does any of the above disqualify a VFP COM from being used by Cold Fusion?