Kurt
0
Ever since I installed VB 6.0 on a machine that already had VS .NET installed (I did this to use an old ActiveX control shipped with VB 6.0, mscomm32.ocx), I dont get information about run time errors in applications written in VB.NET. If for example I want to open a database table that doesnt exist, the application doesnt go to the source code line where the error occurs. When step line for line through the code using a break point , the function in which I try to open the table is left (just as like an exit function statement) as soon as the line with the open statement is reached... and the application keeps running without any error message.
This has probably something to do with JIT debuggin. Maybe the installation of VB 6.0 disabled some debugging facilities? But as far as I could check JIT debugging is enabled on my machine... And database calls are not the only non-reported errors. Anyone knows a solution for this anoying problem?
This has probably something to do with JIT debuggin. Maybe the installation of VB 6.0 disabled some debugging facilities? But as far as I could check JIT debugging is enabled on my machine... And database calls are not the only non-reported errors. Anyone knows a solution for this anoying problem?