>>AHA, the filament of my light bulb finally 'fired'. Thanks for the clarification. I guess the other thing that I have learned through this process is that VFP COM methods cannot involve user interfaces, such as forms. I guess the way around that is to have another VB DLL that exposes the forms, calls the VFP DLL for the hard work and returns results through the form back upstream (if the external DLL is responsible for providing some independent user interface).
>>
>>Thks again,
>
>Not exactly. If you do it in VFP, you still can have your form in VFP client and call the VFP DLL with some parameters obtained from your form for some work and return some results. You are right, that VFP COM DLL methods cannot involve user interfaces directly but it does not mean that you cannot have a full visual interface with your VFP COM object if you want to. The key word here is directly . Note, that my DevCon session is called "Build Visual Interfaces with Visual FoxPro COM/DCOM Modules". http://www.advisor.com/CMF0109p.nsf/wSessionsSpeaker?OpenView&Start=1&Count=30&Expand=26#26


It's nice how timely some of these DevCon topics can be. . .either that or you are clairvoyant.:). You are guaranteed of at least one attendee.