Hello,
we have the following problem:
We have an application which uses an VB6 control on a .Net-Form. The VB6 control is included in the .Net application by a wrapper class created by aximp. This works fine on our Windows XP Systems.
When I install this application on a Windows 7 system I get the in the title mentioned error when i want to open the .Net form with the VB6 control on it. After clicking OK the application hangs up, without any further information, for exaple in the eventlog or so. On this system there is only the vb6 runtime environment, because ist only a normal client.
On my developing system on a windows 7 computer (logically with Visual Basic 6 and Visual Studio 10 installed) the application works fine, there are no problems starting the .Net form with the VB6 control on it. The deleveloping system and the clients are all x86 systems, and the target platform is for all .Net projects x86.
The used VB 6 control implements an interface and I suspect this to cause this error, but without knowing why this could be the reason. The control uses an mts proxy to get data from a database by vb6 classes on an mts server. This does not seem to be the problem. I have build a test control without the implementation of an interface which but also using the mts and it works in all environments well.
Thanks for help.
we have the following problem:
We have an application which uses an VB6 control on a .Net-Form. The VB6 control is included in the .Net application by a wrapper class created by aximp. This works fine on our Windows XP Systems.
When I install this application on a Windows 7 system I get the in the title mentioned error when i want to open the .Net form with the VB6 control on it. After clicking OK the application hangs up, without any further information, for exaple in the eventlog or so. On this system there is only the vb6 runtime environment, because ist only a normal client.
On my developing system on a windows 7 computer (logically with Visual Basic 6 and Visual Studio 10 installed) the application works fine, there are no problems starting the .Net form with the VB6 control on it. The deleveloping system and the clients are all x86 systems, and the target platform is for all .Net projects x86.
The used VB 6 control implements an interface and I suspect this to cause this error, but without knowing why this could be the reason. The control uses an mts proxy to get data from a database by vb6 classes on an mts server. This does not seem to be the problem. I have build a test control without the implementation of an interface which but also using the mts and it works in all environments well.
Thanks for help.