>I seem to remember something on this site about the FoxUser file causing or being involved in the error, but don't remember. Anyone have any idea what I am talking about ? Care to shed some light ??
I had a C...5 problem I believe to be related to saving form positions, code window positions, etc., to the FoxUser file. My problem is:
1) with form open in designer, double-click on an object on a form (or the form itself) to bring up a code window with the last method I added code to for that object
2) remove all code from that method (to go paste it into another method, but that's not necessary for the error)
3) close the code window but not the form designer
4) the next time I double-click on that object which no longer has code in the method VFP wants to bring up, I get C...5.
Notes: if I close form designer after removing the code, before double-clicking the object again, no error.
The reason I think it has to do with FoxUser is because it crashes at the moment VFP is checking FoxUser to see which method of that object to get the code for.
Microsoft FoxPro Development Team asked me for sample form, code, config.fpw and foxuser files, which I supplied, and they can't reproduce the error. So it might just be a conflict with other software installed on the machine I'm using at current client's site.
Help? (Didn't think so ... :)
Rich Addison, Micro Vane, Inc., Kalamazoo, MI
Relax, don't worry, have a homebrew.
- Charlie Papazian, The New Complete Joy of Home Brewing