>>>
>>>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.
>>
>>You might want to holler at Rod Paddock regarding this. I know that at some point, he was (is?) using Cold Fusion, and probably has some insight into your problems.
>
>I have emailed Rod and have gotten no response yet. I did get a response from a guy who posted the same question on Cold Fusion's site. He indicated that Cold Fusion cannot handle VFP COM objects well. In order to make it work I need to have methods that have no parameters and the methods deal with nothing but properties of the COM (This affects state I think). I have not tested this to see if it would work, but I will. My guess is that Cold Fusion is having a problem with variant parameter types (SWAG). The guy also indicated that he worked on this problem too long and eventually went to something else. The base here is pushing cold fusion, but this little snag kind of kills the concept of N-Tier.

Bret,

I wouldn't give up so quickly..

What about a VB-based COM object in between a VFP-based COM object and the other tier (UI? Data?) that manages the data into the proper format?