>>>Hmm, there are two possibilities here. The first is that foxtools can't properly handle a string that long. I believe that you mentioned it was 900,000 bytes or more. The second has to do with passing the scan lines. Despite the fact that you're getting back 3 bytes per pixel, you only pass the number of necessary scan lines. In other words the height of the area in pixels. Is this what you're doing?
>>
>>One thing bugs me with this (not that I can help with the issue) - do we still have to use RegFn and CallFn now when we have Declare ... In ...?
>
>Only in FPW. Thankfully, I'm dealing less and less with it.:-)

Well, then, this 900,000 byte string doesn't have to go through FoxTools (which is somewhat 255-limited), but directly into an API call. Or did I sleep over the most interesting part of this thread?