Leemi
Tue May 25 12:22:11 CDT 2004
Hi Wolfgang:
One of the first items I recommend to anyone who see a memory error in the
Debugger is to delete or rename the Foxuser.dbf and Foxuser.fpt files. The
Debugger stores a lot of settings in the Foxuser files, such a window
positions. If those files become corrupt, you can see an error like you
received.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003
>Hi Cindy,
>thank you very much for your comment.
>Hhmm... you are right, just now I tried to repeat the mentioned error and
it
>did not happen again.
>Anyhow, I checked the Event Logs and I found the following entry:
>The description for Event ID ( 1000 ) in Source ( Microsoft Visual FoxPro )
>cannot be found. The local computer may not have the necessary registry
>information or message DLL files to display messages from a remote
computer.
>You may be able to use the /AUXSOURCE= flag to retrieve this description;
>see Help and Support for details. The following information is part of the
>event: vfp8.exe, 8.0.0.3117, ntdll.dll, 5.1.2600.1217, 00007ec4.
>Wolfgang
"Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message
news:OU%23QXUPQEHA.3596@tk2msftngp13.phx.gbl...
> In news: eay1qOOQEHA.368@TK2MSFTNGP09.phx.gbl,
> Wolfgang Greger <gregerw@loxinfo.co.th> wrote:
> > To stop the program and to inspect some variables in the Debugger I
> > usually put a Set Step On into the program code.
> >
> > After finish checking and clicking the Cancel button VFP keeps
> > crashing.
> >
> > This behaviour follows me since the debugger has been introduced over
> > a decade ago and through all VFP versions.
> >
> > Due to this behaviour I trained myself to close the Debugger with
> > "Debug - Fix". Recently I forgott it and clicked the Cancel botton
> > and VFP (now version 8) again crashed.
> >
> > I wonder how this Bug (?) could make its way so far - or did I do
> > something wrong?
>
> Hi Wolfgang,
>
> Well, I don't have this problem, and I haven't seen many complaints about
> it, so there must be something unique about your setup or programs that is
> causing this. Have you looked at your system Event Viewer to see what's
> there after a crash?
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy.winegarden@mvps.org www.cindywinegarden.com