Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Probs with debugger
Message
From
08/04/2016 12:48:40
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
08/04/2016 10:29:46
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8.1
Network:
Windows Server 2012 R2
Database:
Visual FoxPro
Application:
Desktop
Virtual environment:
VMWare
Miscellaneous
Thread ID:
01634403
Message ID:
01634542
Views:
49
Albert,

my opinion is it will change nothing to nuke the foxuser. But if you are afraid testing, simply create a copy of the files on explorer and give it a try. If wrong, rename the copy back. (Shut down VFP before copy / rename)

>HI Lutz,
>
>Thanks for the response. Have you ever tried nuking the resource file (if you use one). I just had this thought that stuff like breakpoints might be stored in the resource file and maybe there is a problem there. Thought I would ask before trying it.
>
>Albert
>
>
>>Dragan,
>>
>>what he describes occurs if you have many layers of classes and large callstack on it.
>>
>>You doubleclick in the debugger
>>- no breakpoint mark (visibly) set, breakpoint not respected
>>- breakpoint mark set, breakpoint not respected
>>- run-to-line (F7) fails
>>
>>it runs through the line.
>>
>>I have this on a regular base.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform