Creating a large string in a private heap

[vbwins]

The SysAllocString family of functions allocate BSTR strings which is what VB6 uses as it's native string type. They do a little more than simply allocate memory. It would make sense to throw an "out of string space" error when a call to one of these functions fail. It would more accurately reflect that we are dealing with a higher level abstraction, in this case, a BSTR. That's my instinct anyway.

Yes I thing you are right. I will catch the error and go back to view the dissambly in windbg which at least will show me what is being called. Tye arguments are beyond me,