Quote Originally Posted by Schmidt View Post
I thought you found a workaround already (by showing these Forms modally)...

But anyways, there's no hacks required to make "Project-Private-UserControls" work with threaded Forms.
You just have to embrace and learn about:
- VB6-Classes
- how to implement and test them as "Private Classes" in an isolated Test-Project
- how to later move - and encapsulate them in Ax-Dlls (after they become stable)
- and how to load Ax-Classes from such Ax-Dlls regfree

The VB6-STA-based threading-model (which is all about "Public Classes on their own Threads"), works rock-solid -
whereas attempts at FreeThreading in VB6 will always be "fragile" at best.

So, the solution for your "Private UC on a threaded Form" is, to move the threaded Form out of the Ax-Exe-Project...
And into a separate ActiveX-Dll-Project (together with any Private UCs you want to use on these threaded Forms).

I've added a second example (which shows how to do that) to the AxExeThreading article here:
http://www.vbforums.com/showthread.p...-(simple-Demo)


HTH

Olaf
Maybe activex exe is a packaged rot model? If we first develop a rot program instead of activex.exe, then we can achieve perfect multithreading as we want, it is very convenient to support usercontrol。
chinese:也许 activex exe 是一种包装好的 rot 模型?假如我们单独先开发一个 rot 程序代替 activex.exe ,这样就可以随心所欲的实现完美的多线程了，很方便支持 usercontrol