In the world of conversion of Visual Basic 6 applications, little causes more concern than controls that just won't convert. Between in-project controls that you have the source code for, custom ActiveX controls that you bought back in 1997, and the built-in Microsoft controls that have no real conversion path, the task is not easy. There is hope, however. Code in Visual Basic 6 user controls convert fairly well to Visual Basic 2005. You can use some third party controls via interop. Tools are provided in Visual Studio 2005 to assist with OCX proxy creation. All is not lost.