Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: suhas hegde
  Where is suhas hegde?
 sirsi
 India
 suhas hegde
 To: Ilya Rabyy
  Where is Ilya Rabyy?
 Fountain Valley
 California - United States
 Ilya Rabyy
 Tags
Subject: RE: Prog stops where it shan't in Debugger
Thread ID: 154927 Message ID: 155012 # Views: 1 # Ratings: 0
Version: Visual FoxPro 9 Category: Errors & Debugging
Date: Friday, December 21, 2007 6:20:02 PM         
   


> >
> > Hi,
> > I checked and and the break points are stored in the resource file.
> >
> > Suhashegde
>
> Hmmm...
> I believe this is not the case with my problem: it was not even I who wrote the code in the first place, I just added couple fields to the resulting cursor (used for report) and I've never run this method in STEP ON mode before. And the machine - I am its first user.
>
> Anyway, Suhas, where do I look in the FoxUser table to find those breakpoints? I looked up the record with this class in FoxUser: the Name field carries only the lib/class name (surprise!?!), and the Data field carries non-printable chars...
>
> Regards,
>
> Ilya


Hi,
Simple way
1)start VFp
2) start Debugger
3) debugger > file > save configuration (always Make a backup right thats why)
4) Make a file with "nobp.dbg" on the desktop open with notepad
paste the following in it

DBGCFGVERSION=4
BPMESSAGE=ON
EVENTWINDOW=ON
EVENTFILE=

save the file

5)Debugger > file > load configuration ... the file created on desktop
6) Run the form which troubled you.

FOr detail where it is stored in Foxuser read below how i located it...

If that fails then

There might not be a direct way but you can trap it.

Read Post script first if that fails then this

Follow these steps


make a backup of Foxuser.dbf and associated files (.fpt ) best is copy foxuser.* after u set "set resource off "

then start as follows

open Vfp & debugger
minimise debugger

Always keep sysmenu to default in the form run so that you can access it.

Set resourse off
Run the form.
Go to the code where u have the breakpoint (not run the code now .. v have a bit more work to do)

tools > options > File locations > select the your resorse file

Now run the code which causes the break point to stop
execute the break points lines in the debugger.

after the code execution is finished
tools > options > File locations > clear out resourse file

exit the form

Open resourse file with USE

You will now have a record with (may be many) check for current updated date

TYPE ID
PREFW BPOINTS ... Check the memo field value

thats it...

HTHS
suhashegde

P.S.: If you see before all these steps you will not see the BPoints atall or infact You might too. In that case if you have BPOINTS in ID Check what value it holds in MEMO ... deleteing that might help..

Normally
it stores in ID SNIPLAST pointing to Debugger Configuration file (Where it is i dont know.. where it reads the debugger conf file i dont know Still checking on it)

ENTIRE THREAD

Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/20/2007 5:13:21 PM
RE: Prog stops where it shan't in Debugger Posted by Ken Murphy @ 12/20/2007 5:17:47 PM
RE: Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/20/2007 5:57:20 PM
RE: Prog stops where it shan't in Debugger Posted by Jon Goad @ 12/20/2007 5:26:47 PM
RE: Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/20/2007 5:50:51 PM
RE: Prog stops where it shan't in Debugger Posted by suhas hegde @ 12/20/2007 6:55:02 PM
RE: Prog stops where it shan't in Debugger Posted by Tamar Granor @ 12/20/2007 10:32:40 PM
RE: Prog stops where it shan't in Debugger Posted by suhas hegde @ 12/21/2007 12:23:39 PM
RE: Prog stops where it shan't in Debugger Posted by Ilya Rabyy @ 12/21/2007 5:11:49 PM
RE: Prog stops where it shan't in Debugger Posted by suhas hegde @ 12/21/2007 6:20:02 PM