Quote Originally Posted by Elroy View Post
And TomCatChina, you really should read through that link I gave you.
Yes,I have read your post carefully and clearly understand your point of view.

Quote Originally Posted by Elroy View Post
Even after you get the address of a procedure in an object, you can't just call it like a procedure in a BAS module.
I realize that all of vb's class procedures follow the COM standard with THIS pointer, implied return parameters, and HRESULT return values, and that with clever THUNK code, these side effects can be eliminated for other code to call in STDCALL fashion.

Quote Originally Posted by Elroy View Post
The only way to avoid this is to declare them as Public and then use that Vb6ComCodeObjectAddressOf function in the link I gave you above.
Yes, this is the most robust way to do it, and the source code is easy to maintain, at the cost of using a public process.

Thank you for your enthusiastic reply, and thank LaVolpe for his work.