I guess I understand it, Does that mean that every time I need to use one or more tables in a method call I have to open the tables at the beginning and close them at the end of the method?

Luis


>Nope, you can't do that. The COM+ component (even a standard COM component) does not have access to the memory space of the EXE.
>
>>Hello again Esparta. I printed and read the articles you pointed me to, they are very, very interesting and show how to setup a component along with security and all the necessary stuff. Well, now my question is...should I take additional considerations regarding VFP programming like open tables, indexes, variables, objects and so on? Should I treat my COM+ component like any other object in VFP? For example, can I reference an already-open table frmo within my component's method code, like this?
>>
>>

>>USE myTable
>>o1=CREATEOBJECT('myCOMComponent')
>>
>>** This method sums a given field column and returns the result.
>>myVar= o1.SumCursorColumn(;
>>   'myFieldColumn') && Name of a field of the 'myTable' table already open.
>>? myVar
>>USE in myTable
>>

>>