[JohnD]

remove the sendfaxui code, in its place you need to do two things.

1. set winfax as the current printer driver.
2. print your report.

Hope this helps

[JohnD]

set WinFax as the default printer, and then use the WebBrowser control on your form.

‘ get html or txt file and display it in the Webbrowser window

WebBrowser1.Navigate Filename

‘print it using ExecWB, no dialog/prompt

WebBrowser1.ExecWB OLECMDID_PRINT, OLECMDEXECOPT_DONTPROMPTUSER

[JohnD]

nope. this is not available in the sdk

[JohnD]

switch to Delrina Fax 10.0 (WinFax PRO 10.0), there is no other solution.

[JohnD]

I think the reason was many were having problems, since they never tested (or intended to run) on a server machine — it was never supported.

[JohnD]

I don’t think any error list exists. If you are getting error, you may be not allowing enough time for WinFax to process the attachment

[JohnD]

You should not use the SendFaxUI option, as this is not required if you are printing to the WinFax driver.
You need to switch the printer driver to WinFax, and then print your report. When done, switch the printer back to the original printer driver.

[JohnD]

‘

---

‘ 32 bit error values as per Win32 standard (see winerror.h)
‘
‘ Use CLng(result) to convert error codes returned from the Conversion interface
‘ into values that can be compared to these constants.
‘

---

Public Const errFxconvertFileInfo As Long = &HE0040101 ‘ Failed to fetch file information
Public Const errFxconvertInitBitmap As Long = &HE0040102 ‘ Failed to initialize file read structure
Public Const errFxconvertSetPageToRead As Long = &HE0040103 ‘ Unable to set number of page to be read from file
Public Const errFxconvertCantWriteDest As Long = &HE0040104 ‘ Unable to save file to disk in indicated format
Public Const errFxconvertCantReadSrc As Long = &HE0040105 ‘ Unable to read file from disk
Public Const errFxconvertBadPageNumber As Long = &HE0040106 ‘ Invalid page number
Public Const errFxconvertBadFxFormat As Long = &HE0040107 ‘ Invalid FX format code
Public Const errFxconvertBadBitsPerPixel As Long = &HE0040108 ‘ Invalid bits per pixel
Public Const errFxconvertBadFormat As Long = &HE0040109 ‘ Invalid format code
Public Const errFxconvertDescriptionTooLong As Long = &HE004010A ‘ Description string is too long

Public Const errFxconvertUnknown As Long = &HE0040120 ‘ Unexpected error code
Public Const errFxconvertCantCreate As Long = &HE0040121 ‘ Unable to create file
Public Const errFxconvertFailedToOpen As Long = &HE0040122 ‘ Unable to open file
Public Const errFxconvertBadWrite As Long = &HE0040123 ‘ Error writing to file
Public Const errFxconvertBadRead As Long = &HE0040124 ‘ Error reading file
Public Const errFxconvertNotOpen As Long = &HE0040125 ‘ File was expected to be open
Public Const errFxconvertBadSeek As Long = &HE0040126 ‘ Error seeking in file
Public Const errFxconvertLineCount As Long = &HE0040127 ‘ Unable to determine image linecount
Public Const errFxconvertNotFxFormat As Long = &HE0040128 ‘ File is not a proper FX? format file

this is from
http://www.getfaxing.com/downloads/ifxconv.bas

hope that helps

[JohnD]

Try this code

Dim objWFXSend As Object
Set objWFXSend = CreateObject(“WinFax.SDKSend8.0”)
objWFXSend.SetClientID (“Client Name”)

With objWFXSend

.SetCountryCode (“”)
.SetAreaCode (AreaCode)
.SetNumber (PhoneNumber)
.SetTo (FullName)
.SetCompany (rs!Company & “”)

.SetSubject Msubject
.SetCoverText (sCoverText)
If Len(docAttach) = 0 Then
Else
.AddAttachmentFile (docAttach)
End If
End With

objWFXSend.LeaveRunning()
objWFXSend.AddRecipient
objWFXSend.Send (1)
objWFXSend.ShowSendScreen (0)

‘ this routine waits until “IsReadyToPrint” returns a Non-zero ‘value (ready) this loop will wait but allow background ‘processing to continue

Do While objWFXSend.IsReadyToPrint = 0
DoEvents
Loop

‘ Close it down.

Set objWFXSend = Nothing

Edited By JohnD on May 31 2002 at 12:20

[JohnD]

@leopard wrote:

If Winfax Pro 10.02 has a problem with DDE and Windows XP, is Winfax Pro 10.0 compatiable enough with Windows XP to mostly function or does it just not work with Windows XP?

10.0 will work fine if you don’t integrate with Outlook 2002. I have not found any other problems with 10.0 and XP. It is possible that user-switching may be a problem.

[JohnD]

I think 10.02 and WinXP has problems with DDE, I am not aware of any solution.

[JohnD]

are you trying to send a fax here, or make an attachment? I don’t follow your code.

[JohnD]

i don’t think the .dat file structure has ever been released from symantec.

[JohnD]

Printing functions are different in Win2K. If you used Win9x, you probably will encounter problems if you move your code to WinNT platform.

You’ll probably need to edit your code, add fix timed delays after your DDE commands. (1 second or so)

[JohnD]

@JohnD wrote:

no, this is not supported. You should look at http://www.faxback.com they offer the server software that will probably handle this, you can still use WinFax as the front end.

Here is a direct link to the software they provide that uses WinFax as a front end.

http://www.faxback.com/netsatisfaxtion/index.html

[Author]

Posts