>>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.
>
>VFP COM object do implement IDispatch. FWIW, this is required for all scripting languages that don't support early binding.
>
>>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.
>
>Unfortunately, all parameters in VFP COM objects are listed in the tlb as Variant. This will change in VFP7.
>
>I have no idea if ColdFusion can deal with VFP's variant data types, but it shouldn't be a problem.

Thanks Erik.

We are trying to get a simple VFP COM object to work, and Cold Fusion is failing. The base has gone to cold fusion so must we, but it does not seem to be as straight forward as the Cold Fusion help shows. The error that Cold Fusion gives me back is that my method calls are not Cold Fusion functions. So my guess is that it is not instantiating my VFP COM object in its CFOBJECT tag and assigning it to the variable I declared.