Re: Faxing of Blank Pages problem from FaxPack for Windows: We've put together this tech note/letter to assist with a problem you may encounter when using FaxPack for Windows while using 4D Write. There is an odd problem when printing from within 4D Write and using Faxpack for Windows. It is kind of a double whammy, as the printing seems to pass through 4D Write, through 4D and then through the OS.  Therefore, the whole process takes longer than it should. The way that FaxPack works is that we set up the print driver to do a special print to the WinFax printer driver the next time that a print command happens.  Basically, the printing process generates a temporary file, which is then assembled into a final fax document, when the "SPEndMessage" is executed. What it appears is happening, is that the generation of the temporary file is taking too long from 4D Write. Unfortunately, this temporary file is then handled 100% by WinFax, without any messaging back to FaxPack and without any way for FaxPack to know the progress of the generation.  Therefore, when the SPEndMessage is executed, the temporary file that contains the image of the 4D Write printing, is not available - and the fax is generated without the image. Try this... Insert a "WAIT" or "DELAY" command just before the SPEndMessage command and wait from 10 to 30 seconds before you continue. Unfortunately, inserting a timed pause loop at this point may be the best solution to deal with the print delays which are experienced on 4D when using 4D Write! -- Tim Haratine