Ook
Mon Aug 02 14:40:43 CDT 2004
I believe that VFP has just been exonerated. I did a clean start by removing
everything from my startup, and found that the USER object count did not
skyrocket when joining the project. Something that gets run from startup
must be causing this, but I have no idea how it would do this. This is a
company machine, and I don't have time to remove startup items one at a time
to find the guilty culprit. Suffice to know that this appears to not be the
fault of VFP (unless VFP is not getting along with one of my startup
programs, and it really is bad VFP after all lol).
The key here is the USER object count. Win9x had a terminal issue with
limited GDI and USER resources. Win2000 fortunately does not, but when an
app uses close to 3000 USER objects, this is a big red flag, klaxons,
flashing lights, etc.
"Lee Mitchell" <Leemi@online.microsoft.com> wrote in message
news:YDojp5LeEHA.676@cpmsftngxa10.phx.gbl...
> Hi ook:
>
> Have you tried creating a new VFP project in case the one you have is
> corrupt?
> Issue a SYS(1104) before joining source control project. Try limiting
> VFP's internal memory usage with the sys(3050) function. I would try
> settings like SYS(3050,1,256), SYS(3050,1,10000000), and
> SYS(3050,1,50000000), for a start. (Normally, SYS(3050) only helps with
> memory when accessing tables for views, but it is worth a try here.)
> Finally, what version of VFP are you using? Do you have the most recent
> service pack installed?
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 Public Beta Now Available!! --*
> Download the VFP9 beta here:
http://msdn.microsoft.com/vfoxpro/
>
> *-- 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 retired Sept. 30th, 2003
>
>
> >File -> Join source control project. This is a large project with several
> >thousand files.
>
> >VFP apparently does a get latest on the PJM file, builds a new PJX., and
> >then does a get latest on everything in the PJX. When it finishes, I get
> >"There is not enough memory to complete this operation". At the time this
> >occurs, VFP is consuming 20MB physical memory, 10MB swap file, 209 GDI
> >objects, and 2911 USER objects. This last entry concerns me, as 2911 USER
> >objects is quite high and is probably why the error occurs. VFP will
> >normally have less then 100.
>
> >Historically, excessive USER or GDI usage is a result of poor
programming,
> >bugs, or memory leaks. I also think that this should work, even if it is
> >using a lot of USER resources. Win2000/XP doesn't have the terminal USER
or
> >GDI limits that Win9x had, so I'm thinking that the problem here is
> internal
> >to VFP. Also, it works for some of us, and not for others. It's not just
my
> >workstation, as I'm not the only one having this problem. Any ideas?
>