Hi J.C,

Thanks for the answer.

>1.- As long as your variable doesn't go out of scope or you explicitly release it, it should be accessable.

In MSDN library I found:

An out-of-process component written with Visual Basic will shut down when:

The component has no forms loaded.
A loaded form will keep your component running past the point at which all references have been released. Forms should be unloaded when the object that created them terminates.

No out-of-process client applications are holding references to the component’s public objects.
Internal references to public objects will not keep a component running if clients have released all their references. Neither will references held by an in-process component the out-of-process component is using.

No code in the component’s modules is currently executing, or in the calls list waiting to be executed.

This last one - does it mean that if the component does not start to do things right away after creating it it will be released?
I am trying to understand what creates the wait state in this VB COM, something similar to VFP READ EVENTS.

>2.- On the development machine that is taken care of when creating the exe. If registering in other PC's then /regserver should do it.

That's what I read in the docs, however it still can't find it.

>Now, don't try the coffee monitor with callbacks example!! :)

I won't :)