>Hi
>
>I have some questions about the use of COM objects:
>
>- What's the CONTROL SOURCE my controls will have on my form? I have to create a cursor (probabilly, returned by the COM object)? (normally, i use remote views, since i'm working with SQL Server!);
>- I've read once, and i agree with creating methods for Create, Add, ... but for example: the ADD method should accept the fields of my table as parameters (i read, once, some people use properties of COM objects to hold each field of the table)? If so, i'll a lot of work. I'm used to save a record only use TABLEUPDATE!!!
>- Every COM objects i create, i should have them on another project (makes sense...)?
>- It's difficult the process of installing the application and components on our final customers?
>- I can have DLL's without Microsoft Transaction Server, isn't it? If so, i can have connections problems, because each component creates one; and, if i have a transaction i can use 5 or 6 components at a time. Must i have to use Message Queuing?
>
>Thanks

Usually it is best if you create one thread per question, and give a little more explanation.

There's some good info on VFP & distributed COM in msdn.microsoft.com/vfoxpro.