>>>this is so weird ... WIN95 VFP6 SP5
>>>
>>Maybe it's an issue with cached images. Take a look at CLEAR RESOURCES.
>
>------------------------
>hi Al -
>
>holy cow !!! i didn't realized images were cached like that !!
>that issue sure sounds it has promise in solving my problem.
>not only that problem, but another mystery too.
>
>thanks much for the idea.
>------------------------------
>for CLEAR RESOURCES, the help contains the following statement:
>
>"When Visual FoxPro DISPLAYS a bitmap, picture, cursor, icon, or font resource, the resource is cached to optimized performance...."
>
>would you say that having an image included in a report constitutes
>"DISPLAYS". ??

Yes, it certainly *does* count. I have had to use CLEAR RESOURCES in reports in order to get the correct image(s) to print, rather than a cached earlier version. Interestingly, this is one case where having more RAM in your system makes the problem worse! More images are cached, so you get more incorrect ones printed. On a RAM-starved system images may not be cached at all, so you don't see the problem.

>-------------------------------
>on the part of my project that captures these images, i'm sure gonna
>try doing a CLEAR RESOURCES. every once in a while i get a message
>"...running low on resources..."

This message relates to different "resources" - typically the small Windows GDI heap in Win9x. I don't believe CLEAR RESOURCES has any effect on the occurrence of this message, but it can't hurt. To eliminate it entirely go to Windows 2000 or XP. You might try the undocumented SYS(1104) function to help clean up memory used by VFP.


>i assume there is a limited amount of memory used for cache ?
>is it possible that Windows is mishandling that cache? or FoxPro ?
>------------------------------------------------------------
>
>thanks again,
>patrick