Re: FoxPro is a frustrating and very user unfriendly

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: MAppell917 (mappell917_at_aol.com)
Date: 09/10/04 

Date: 10 Sep 2004 21:30:37 GMT

Ook - I could only speculate on the following ideas as to why some get
c0000005 more than others...

1. When I compile my program for the final exe, I remove all the methods prg
code from the forms and classes. It also has the advantage of making the exe a
lot smaller.

2. I always set my CreateObject variables to "" and then release them at the
end of the procedure.

3. I use very few public variables (maybe 4 or 5 in the entire app).

4. I never use inheritance more than 2-3 levels deep (mainly because I have
just never needed to).

5. I use encapsulation as much as possible and use as few modal forms as
possible.

6. I display the detailed error information including the procedure/class name
and line number for quick and easy debugging if errors ever do occur.

There are probably other things I do as well but I'm not sure if one or several
of the above minimize the C000005 errors. In fact, I think it has been months
since ANY of my clients have mentioned this error (this could also be due to
further migration to XP but it's very infrequent even with my Win 98 clients).

Regards,

>I've been on this list for many years, and I've been sharing experiences
>with others here for a long long time. And one thing I've learned is that
>some people get them a lot while others don't get them at all. I wish I knew
>why. I've experienced specific method code corruption issues in VFP6 quite a
>bit, and I've met several others that have seen it also. Yet many others
>have never had it happen. Why?
>
>I can't answer that question, but I can definitively say that VFP6 gave me a
>lot of c0000005 no matter what machine I worked on, while VFP8 almost never
>does.

Mike

Relevant Pages

  • Re: exporting functions/subs from fortran?
    ... Implicit in the tlb approach that I mentioned is that the 'exe' has no ... > It's nice to hear other developers with your caliber exist. ... >> So your clients are developers. ... >> stick with a classic CVF DLL with exports. ...
    (comp.lang.fortran)
  • Re: FoxPro is a frustrating and very user unfriendly
    ... > DO FORM XYZ ... When I compile my program for the final exe, ... >> methods prg code from the forms and classes. ... >> very infrequent even with my Win 98 clients). ...
    (microsoft.public.fox.programmer.exchange)
  • Re: FoxPro is a frustrating and very user unfriendly
    ... Your mention of modal forms jarred a memory loose. ... DO FORM XYZ ... When I compile my program for the final exe, ... > since ANY of my clients have mentioned this error (this could also be due ...
    (microsoft.public.fox.programmer.exchange)
  • Re: vfp9 speed issues
    ... it has been a while since we moved up from VFP6, however i seem to recall ... In recent months we have recompiled our vfp6 application in vfp9 and are ... in the process of rolling this out to our clients. ... the speed of some of the longer processes ...
    (microsoft.public.fox.programmer.exchange)
  • Re: vfp9 speed issues
    ... If you're coming from VFP6, you're unlikely to have code that handles and/or ... We have a number of clients advising us of a substantial degradation ... in the speed of some of the longer processes ... Is this characteristic of vfp9 or is there some new option that is likely ...
    (microsoft.public.fox.programmer.exchange)