Hi Al,

I am going to check out having too much memory assigned to the foreground memory - I think I have it set to about 1024MB. See my other thread replying to Naoto.

Thanks a lot.
Albert

>>Hi all,
>>
>>I have a customer who is running into "not enough memory" errors in VFP. The code where it fails is in a 3rd party add-on, very old, very ugly code that uses a lot of memory variables to hold configuration items. Users did not run into this before generally but it seems to be getting worse. I realize that something else may have changed in the environment but to try to figure this out, has anyone else had more trouble with VFP under Windows 10? I sort of remember seeing here that others have experienced that Win10 is not good at memory management.
>
>I don't know of, and haven't heard of any specific issues with Win10 memory management. If you have any specifics I'd be interested.
>
>The only thing I have heard of with Windows in general (not Win10-specific) is that systems with large amounts of memory installed may (counter-intuitively) cause VFP apps to run *slower*, or with odd problems, if default VFP memory settings are used. Naoto has already pointed that out it can be helpful to *limit* the amount of RAM VFP can use via SYS( 3050 ). ISTR Thomas Ganss (?) recommending that VFP's best performance is if it's limited to using ~ 256MB, and should never be allowed to use more than 512MB (i.e. set to 511 or 500MB) to avoid slowdowns or problems.
>
>http://fox.wikis.com/wc.dll?Wiki~SyS3050
>
>Recently I was running code that embedded files into a SQL Server database. It makes use of FILETOSTR( ), which as Rick Strahl points out in his blog can create VFP "strings" which are much larger than the nominal 16MB limit: https://west-wind.com/wconnect/weblog/ShowEntry.blog?id=882 . His blog shows an example of importing a 680MB file into a VFP string. In my case I was doing some post-processing using CREATEBINARY( ) and my code crapped out on a file a little over 350MB with an "out of memory" error. So if you're using large strings in this manner it's possible to hit those types of errors.
>
>One other edge case: I seem to recall a long time ago someone (Rich Simpson / MERE?) discussing limitations of GDI in VFP when using SET REPORTBEHAVIOR 90. There are limits in GDI which I *think* can manifest as out of memory-type errors in VFP: https://blogs.technet.microsoft.com/markrussinovich/2010/03/31/pushing-the-limits-of-windows-user-and-gdi-objects-part-2/ . If you're using a lot of GDI objects or running large/complex 90 reports it might be worth looking at.