>I have recently modified a VFP(6) app ( most notably changing to private datasessions and optimistic buffering ). I have a pageframe/page that interactively builds/runs an SQL statement ( mostly previous code ) that keeps generating an error when the SQL is run. Error 2000, "Memory is low, so streaming output updating has been disabled". This happens on Win95/98/2000Pro PCs that definitely have tons of extra memory available. I can reset this condition by re-launching the app. I checked the docs on this error, and they say "The offscreen bitmap could not be created by a command such as ?,LIST, or DISPLAY." I am running a local .exe that is looking at remote data on Novell servers. I have never experienced this problem before and don't even know where to get started.
I've seen this error quite often (while working with ProMatrix), and it's usually happening when it should report some other error. Could be the error handling routine is trying to display something, but for some reason it can't, and you actually get this as a second message (which then somehow gets through).
This is actually guesswork; the only thing I know is that, in my experience, this error stems from something totally unrelated, having nothing to do with bitmaps.