Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Greg Green
  Where is Greg Green?
 
 Georgia - United States
 Greg Green
 To: Ilya Rabyy
  Where is Ilya Rabyy?
 Fountain Valley
 California - United States
 Ilya Rabyy
 Tags
Subject: RE: SET STEP ON/Debugger malfunction
Thread ID: 396228 Message ID: 396234 # Views: 48 # Ratings: 0
Version: Visual FoxPro 9 SP2 Category: Errors & Debugging
Date: Thursday, January 23, 2014 8:38:41 PM         
   


> Colleagues,
> My woes won't cease! This time it's debugger who's givin' me "blues".
>
> I put the stop point before a cycle programmatically, that is
>
>
***** Debug *****
> IF _VFP.StartMode==0
>    SET STEP ON
> ENDIF
> *****************
> SCAN

> on the line # 409, to be exact. However, when I run this PRG in IDE, it skips this command and stops way down, inside the SCAN cycle, on line #597...
> I, then, removed (commented out) the IF...ENDIF brackets and left the pure SET STEP ON in - same result: skipped this line and stopped on that line 597.
>
> I did what Pete Sass recommended: copy/pasted this program into Notepad, saved, closed, re-opened in Notepad - no "illegal" characters. Ran it in VFP's IDE again - same behavior!
>
> I then opened the Break Points dialog and ensured that there are no break points set. Nevertheless, it continued to stop on that line 597 instead of 409 (or 410, rather).
>
> I, then, commented out the entire IF...ENDIF block - the PRG was executed all throughout with no stoppage.
> Uncommented this block - stopped on that cursed line 579!
>
> Out of desperation, I changed that SET STEP ON command to WAIT WINDOW '_VFP.StartMode==0' - the banner did appear! But SET STEP ON, when it's on that same line, is being ignored!
>
> I suspect, that something in the FoxUser table forces this behavior, but I dunno where to look for it in there. I coulda erase the entire FoxUser, but then I'd have to spend an hour or two restoring all my bloody settings, thus I'm reluctant to do it...
>
> Any other ideas?
>
> AHWBGA!
>
> Regards,
>
> Ilya

Is the above in a form or visual class? If so, try compiling the form or class:

COMPILE FORM
COMPILE CLASS

Possibly the compiled code is not in-sync with the text code...

ENTIRE THREAD

SET STEP ON/Debugger malfunction Posted by Ilya Rabyy @ 1/23/2014 8:28:49 PM
RE: SET STEP ON/Debugger malfunction Posted by Greg Green @ 1/23/2014 8:38:41 PM
RE: SET STEP ON/Debugger malfunction Posted by Ilya Rabyy @ 1/23/2014 9:18:43 PM
RE: SET STEP ON/Debugger malfunction Posted by Greg Green @ 1/27/2014 7:51:12 PM
RE: SET STEP ON/Debugger malfunction Posted by Ilya Rabyy @ 1/27/2014 10:04:29 PM
RE: SET STEP ON/Debugger malfunction Posted by Ilya Rabyy @ 1/27/2014 5:54:47 PM