More aptly described as a 'Bug Maybe' OR just a behavioural change.

Steps to reproduce (well it's not an error :-) ) problem.

In VFP6 open a file and set a breakpoint to a valid line of code.
The debugger opens Minimised
Run the code
Do while .t.
The debugger opens
The debugger displays the breakpoint in code. Very good! BG
Close the Trace Window (very important) and minimise debugger.
Run Code again.
enddo

When you're sick of this development cycle, STOP. :-)


Open the same Code in VFP7
Set a Breakpoint at the same line of Code
The debugger opens Minimised
Maximise the debugger and make sure that trace window is open and then minimise.
Run the code
The debugger opens
The debugger displays the breakpoint in code. Very good! BG
Close the trace window (Very Important)
Minimise the debugger
Run the code
N O D E B U G G E R O P E N S <- What a bugger! No pun intended :-)

In VFP6, even if the trace window is closed, the breakpoint will force the opening of the trace window. In VFP7 it doesn't.... hence the previous post with no replies.

Vlad? Vlad? Where are you? Cna you please confirm this or am I in dreamtime downunder?

Pete