VBA Debugging - F8 sometimes acts as F5

[Isaac]

Anybody else ever see this behavior?

Just once in a while, when I use F8, instead of executing the single line, it just cruises on and finishes the procedure.

Particularly when executing a messagebox line - but NOT always when doing so, sometimes I press "ok" to the messagebox and it breaks on the following line, as I'd expect.

I do tend to sit here all day these days using F8, so maybe it gets tired or something?

 

[Ranman256]

your F8 may be sticking.

 

[Isaac]

Ahh, true, I suppose that's a possibility.

 

[namliam]

have you not noticed yet? There is a bug in windows that screws up the Fx keys, swapping the F5 and F8 is one of the known problems as are the F2/F11 and F3/F12 ... reason for the bug as yet is unknown.

Personaly I do also seem to experience problems with swapping of Page up and Page down... but that fixes itself when I return my screen to its upright position

Spoiler

Yes I am kindding
sorry couldnt resist

 

[Isaac]

Page up and Page down... but that fixes itself when I return my screen to its upright position

Reminds me of one of the most useful hacks in cubicle life! Taking one of those corporate-supplied, ridiculously wide screen monitors and turning it on its head while also changing screen orientation, to better eyeball those long SQL scripts. Really catches people's attention, too. We've been so programmed by society to expect that all visuals must be very wide, but sometimes Tall is better.

 

[namliam]

Reminds me of one of the most useful hacks in cubicle life! Taking one of those corporate-supplied, ridiculously wide screen monitors and turning it on its head while also changing screen orientation, to better eyeball those long SQL scripts. Really catches people's attention, too. We've been so programmed by society to expect that all visuals must be very wide, but sometimes Tall is better.

I have one of my work screens in portrait for that particular reason to be able to see entire sqls, views, functions, packages etc....

I always get remarks about having my screen the wrong way.

 

[pbaldy]

Reminds me of one of the most useful hacks in cubicle life! Taking one of those corporate-supplied, ridiculously wide screen monitors and turning it on its head while also changing screen orientation, to better eyeball those long SQL scripts. Really catches people's attention, too. We've been so programmed by society to expect that all visuals must be very wide, but sometimes Tall is better.

Me too, I have one wide and one flipped tall. I like having the Access window with form/report in design view on the wide monitor and the VBA window on the tall monitor. See more code that way, less scrolling. Having object design on the wide monitor makes sure I'm matching the user's orientation.

 

[Galaxiom]

We've been so programmed by society to expect that all visuals must be very wide, but sometimes Tall is better.

It isn't a matter of "programming". The wide orientation is a much better fit to the human field of view if taking in a single image.
The old 4:3 format was due to the limitations of building CRTs (cathode ray tubes) or TV would have been wider from the start.
(The very earliest televisions had round screens because that was the easiest form to manufacture.)

 

[Isaac]

The wide orientation is a much better fit to the human field of view if taking in a single image.

Yeah, but when you want to see something inherently skinny and tall the monitor flip is nice

 

[sxschech]

I have experienced that usually when the next line of code is calling calling a function using the File Dialog Picker and then after that popup closes the program continues running as if step mode wasn't in use.

 

[Isaac]

I have experienced that usually when the next line of code is calling calling a function using the File Dialog Picker and then after that popup closes the program continues running as if step mode wasn't in use.

Bingo! I get that with the message box occasionally too. it seems that any modal interruption flummoxes the sequence of Step-through functionality somewhat