General information
Category:
COM/DCOM and OLE Automation
>>>I am new to COM technology as it relates to using it outside of VFP. Maybe a simple question will give me a clearer insight to the flexibility of VFP7 and COM. If I am writing a custom DLL in VFP7 for a Visual C++ client that speaks to a MSSQL backend and has been using VB DLL's to answer calls from the VC++ client to perform various functions, will I have the same functionality if the VB DLL (using ADO) is written in VFP7? If I don't, why not?
>>>
>>>Thanks for your input.
>>
>>You should have the same functionality. ADO 2.x is a COM server and VFP can use (almost) any COM server, and be one itself. It used to be that raising events was the limitation but with VFP7 I understand that limitation is gone.
>>
>>HTH
>
>No, VFP 7 still cannot raise events by itself, but if you use my EventRaiser COM you will have no problems with that even in VFP 5 :)
My mistake, I think the word "raising" is the confusion here. You're right, it can't "raise" events but it does have the ability to bind to a COM server's events.
Here I was thinking about the events raised by ADO, which used to be the difference pre-VFPCOM.
Thanks for the point of clarification.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only