CompuServe Thread

I am developing an IPAS and cannot get file "write" to work when the "write" instruction is in a subroutine called by the IPAS module. This is what I did: Took the VBLUR sample, and stripped it then added my own stuff to simply transfer inpix scans to outpix scans, and also wrote each scan to a separately allocated memory DIB. After processing the final scan, I opened a file in the ClientProcImage function, and passed the file handle and DIB pointer to a subroutine. The subroutine called "write" to write 54 bytes and got a return value of 54, suggesting success. Then the subroutine returned and the ClientProcImage function then "close"d the file. Result was a file of 0 bytes. If instead of calling the subroutine I do "open", "write", and "close" all in the ClientProcImage function, then the file is truly 54 bytes long when closed. SO QUESTION: If "write" returns a non-zero value when called from the subroutine, I cannot understand why the file when closed would be zero length in this case, but would have proper length when the write takes place in the same object module. By the way, the subroutine with the "write" is in a different object module.