Re: VB 6 debugging on Vista

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Jeff Morgan" <JeffMorgan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:8839CCA6-3E75-4F23-970B-5DB329EC4537@xxxxxxxxxxxxxxxx

I have ran into a problem that I am looking for a solution for.
I have several older apps in VB6 that I am still working with.
I find that when I debug, if I am stuck in a loop, Vista will not
respond to ctrl-break command. Vista tells me that app is not
responding. If the loop ends, Vista will respond eventually.
Anyone have any ideas how to get VB6 to react immediately
or am I just out of luck?

I'm not sure what you mean? If you're running in the IDE then as far as I know VB is effectively behaving like an old fashioned interpreted Basic program and the "interpreter" is watching for debug input (but not standard user input) in between executing each statement, even if your code is in a tight loop. I've just run a very long time double For Next loop in the VB6 IDE (in Vista) and when I hit Ctrl Break the app breaks immediately and displays the code window with the current line highlighted and it does not continue until I tell it to do so. Is that not what happens on your own Vista system? Or are you perhaps expecting VB to halt immediately on Ctrl Break even if a single VB statement itself takes a long time to execute, for example scaling an extremely large jpg from disk into a small Picture Box or perhaps waiting in some other way for a single statement to finish executing? I don't normally use the debug stuff in the IDE [as you might have guessed from some of the code I sometimes post ;-) ] but I think that VB cannot check for debug input (Ctrl Break or anything else) while a single statement is executing. As far as I know it checks only after a statement has completed and before it starts to execute the next statement. Does it not work as I have described on your own Vista system? If not then can you explain your problem in a bit more detail?

Mike




.

Relevant Pages

  • Re: Walkthrough Instruction Error
    ... behave the same as if run from outside of the IDE ??? ... working in VB6, I really wasn't expecting it to be that very very bad. ... It's cute, but hardly practical given you can't run it from the IDE, can't debug it etc, etc. ... folks in .NET groups first what they think about this idea. ...
    (microsoft.public.vb.general.discussion)
  • Re: Breakpoints and Visual Studio 2005
    ... When executing, Visual Studio displays a mostly transparent dot with an exclamation mark saying that the breakpoint is not valid. ... Visual Studio's options, Tools - Options - Debug, don't do anything to prevent debugging. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Debug stored procedures with VB6
    ... I can't see in the sql server analyser a tool to debug a stored procedure. ... VB6 English and MSDE English ...
    (microsoft.public.vb.database.ado)
  • Re: VC6 ATL DLL interop with VB.NET
    ... I have already upgraded the VB6 project to VB.NET, but I still use it as a ... I know how to debug the C++ code, I actually launch VS 2005 from the VS 6 ... I know that your solution worked in VB6, because we can upgrade VB6 ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Cant debug VB6 component from Visual Studio.NEt
    ... > I am trying to debug a VB6 com plus component from Asp.NET but I can't ... > step through the VB6 code. ... > can debug both types of pages. ...
    (microsoft.public.vsnet.debugging)