[jd576]

Thank you for the comments. I discovered the problem, and it is not within the code.

For some reason, if I set the oWinFax object within the VB program and then print from within the same program, the above stated problem occurs.

BUT if instead of printing from within the program, I shell out to a different small .exe routine and have it print the form — then all works well.

So I compiled the print routine into a small exe, I shell to it with the print parameters, it exits after printing to the WinFax printer, then from within the calling program I close the object and quit the fax print.

This works. I have no idea why I cannot set the object and print from within the same program, but this seems to be the case.

Took 12 hours to figure this out. I hope it is of help to others.

[jd576]

I create the form entirely within VB6 using VB6 print methods, then send it. The printed form is being transfered properly, and appears in WinFax complete. It is just the recipient setup that is not transfering. Also the print function seems to work fine with multiple systems and printer drivers without problem — it seems to have no problem printing to winfax driver.

To the code posted above, I should note that after adding recipient info, I send the oWinFax.AddRecipient command. If I check oWinFax.GetRecipientCount, I find the recipient has been added on the object. But after the form print, I am taken to the WinFax Send screen, where I find empty recipient info and failure to use the requested coverpage (which does exist and is available).

I can make the sample program in SKDSend material (from WinFax) work properly, printing from notepad.

My question is if there is a property of the object that I am not setting that might make a difference. I have tried setting just about all the properties (which I have always previously just left at default, as in the above code) without success.

Thanks.

[Author]

Posts