Quote Originally Posted by RobDog888 View Post
VB6 needs to be run as admin just as any of the other development IDEs. Its a fact that we have come to live with and accept over the years. Have you tried installing VB6 as Admin? Maybe the DataControl error will resolve?
The datacontrol issue has been fixed. I did talk about it post #2, but it could easily have been lost in the post's stuffiness.

Other similar issues have been resolved too. It goes like this:

Running VB6 on Win 10 in non-administrator mode and non-compatibility mode works perfectly except but for one issue. The IDE has problem with components and references when you add them for the first time from the IDE. Only then you need to switch to compatibility and VB6.EXE will register the problematic component or reference just fine. Once this is done, you can kick off compatibility mode and do without it.

I never installed VB6 on either Win 7 or 8 but I have come across the topic many times on the net and it seems to me, that VB6 looks less problematic on 10 that it does on either 7 or 8.

There's a lot of stuff that I don't use in VB6, I tend wo write all my code and depend the less as possible on external dependencies as possible. For that reason, I am not going to try every tiny bit and resolve every single issue.

I can only conclude : so far so good. Win 10 is still ugly. About this I have little hope. But all things considered, I am now pretty much convinced that MS is committed to making Win 10 a success and that includes being able to run on somewhat older and less stuffed machines, and also provide a very high level of compatibility with legacy software products such as VB6.