|
That's kind of weird behaviour. But you'll get used to it with VB. I maintain embedded systems (quality assurance systems in production lines) for a living. Appallingly, these are all VB6 apps. Yesterday I had done about three hours worth of editing, stripping out old dead code that never gets called, fixing a few subtle but nasty issues and adding the feature I was supposed to be adding. I ran the code and set a breakpoint in a routine that was doing some database access, then when it hit the breakpoint stepped into the part where it opened the recordset. Curious as to one of the field values in the first record retrieved, stupidly I asked for it in the immediate pane, and the VB IDE promptly puked on its shoes and lost my work for me.
Another nice one is if you right click a call to a Sub or Function defined in a UserControl and choose "Definition" it gives you a message about it being impossible to jump to that on the grounds that it's hidden. Of course it isn't really, but you have to 'walk there'.
VB6 is a tired old pain the arse. I love my job. I recommend C.
__________________
"I'm not a genius. Why do I have to suffer?"
|