I wonder if anybody knows how to fix the following issue:

We run multithreaded COM objects, compiled with VFP 7 SP1 on Windows 2000 Server SP3 with all patches installed. The object is registered in COM package under COM+ Server. The machine is dual Xeon 2.8 GHz box with 2 GB of RAM. There is nothing else running on the box. An object is called from ASP.

The problem occurs when we grab a huge data set from SQL Server into VFP local cursor1, and then execute
SELECT .... FROM cursor1 INTO cursor2, and then reindex - we get "not enough memory..." message. When cursor is loaded it takes 410MB of memory, then the SELECT INTO increases memory utilization to about 850MB, and finally during indexing, memory utilization goes up to about 1.2GB and then we always get full stop with "not enough memory...". This is very well reproducible situation, and I could not find a way to make VFP to utilize the rest of available RAM. I tried SYS(1104), SYS(3050), it does not seem to affect anything over 1GB (while it helps below 1 GB in other cases).

I wonder if this is a bug or a VFP limit (the documented limit is 2 GB), or I miss some config parameters?...

Thank you,
Igor.