Fax Software

Community Forums

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #3455
    Anonymous
    Member

    TWIMC:
    I have 2 W2000 WKSTN, 1 XP WKSTN. Sever 2000. I have setup a WFP 10.03(reguired version) on a host/client setup.
    I use a FileMaker Pro Application that sends out faxed records. These records get to the host wkstn. In 95% of the time the faxes get to the correct destination. The other 5% is a disaster, as confidential information is sent to the wrong fax number.
    I have followed these fix suggestions:
    Make sure 10.3 was used on both client/host
    Make sure all locations are the same on client/host

    Observations I cannot explain:
    In many fax the CSID is the same as the fax number
    In one fax the CSID is a completly different number
    In one fax it used the number of another person sent 5 days prior.

    This problem has been going on for over a year and no one has been able to even give me a clue what could be wrong.

    Any help would save a mind, as I am going crazy.

    Thanks.

    GERROM :O

    #6825
    Anonymous
    Member

    Is this an automated process, or are you manually selecting the record to fax from your application? (are you using a third party application to communicate with WinFax)

    What do your faxes consist of? Is it a single page, with a cover page, or an attachment file?

    How many faxes do you normally send in a week?
    When was the last time you archived/cleaned up your send and receive logs?

    #6826
    Anonymous
    Member

    This is an automated process in a certain sense. In the FMPro application each client is one master record with many sub-master or sibling records( a one to many relationship.)

    Sibling records maybe faxed, with the specific record selected, a fax will be sent to that location, then another sibling record, of the same Master, is selected with a different fax number is sent. All fax numbers are stored in the database.

    Once the fax is selected, and send fax in the FMPro database is clicked, the FMPro application will create and queue the fax into the WinFaxPro client, which in turn sends this fax to the host.

    Each fax can be up to 4 page long excluding the cover.

    We can send up to 125 faxes per week, but the average is 75.

    The clean up has been over 30 days. However the problem has returned after each clean up.

    Hope this helps.

    #6827
    Anonymous
    Member

    @GERROM wrote:

    This is an automated process in a certain sense. In the FMPro application each client is one master record with many sub-master or sibling records( a one to many relationship.)

    Sibling records maybe faxed, with the specific record selected, a fax will be sent to that location, then another sibling record, of the same Master, is selected with a different fax number is sent. All fax numbers are stored in the database.

    Once the fax is selected, and send fax in the FMPro database is clicked, the FMPro application will create and queue the fax into the WinFaxPro client, which in turn sends this fax to the host.

    Each fax can be up to 4 page long excluding the cover.

    We can send up to 125 faxes per week, but the average is 75.

    The clean up has been over 30 days. However the problem has returned after each clean up.

    Hope this helps.

    From what your describing, that appears to be automated where your FileMaker application is sending the information to WinFax automatically, via the WinFax Software Development Kit (SDK) or another process called Dynamic Data Exchange (DDE).

    If your application is automatically using the fax number and sending it to WinFax to process, then you’re using one of those two interfaces to communicate with WinFax. It’s possible the problem is within the code you are using. Do you know which is being used?

    #6828
    Anonymous
    Member

    Thanks for the quick reply. No I do not know which process is being used, but I will query the developer and come back to you with an answer. Please give me a day or two.

    #6829
    Anonymous
    Member

    @GERROM wrote:

    Thanks for the quick reply. No I do not know which process is being used, but I will query the developer and come back to you with an answer. Please give me a day or two.

    Chances are the application is using the WinFax SDK and not DDE.

    This is likely the source of the problem, you need to confirm that all faxes generated are the correct faxes being sent to WinFax to process. Perhaps if you have more than one user sending faxes from the client to the host at the same time, that may be causing a problem for WinFax.

    #6830
    Anonymous
    Member

    In response the application FileMaker Pro uses Send Fax plugin. In the total process, as I understand, it goes like this: Within the FileMaker application, a fax is generated in a PDF format. Send Fax plugin ties this to WinFax Pro 10.03 and WinFax Pro faxes the information. There is a preset delay of 5 minutes between faxes and WinFax Pro queue’s these faxes. That is the entire process.

    An example of what happens is where a fax, say (925)444-4444 is sent correctly, then at some point another fax is sent with the number (925)555-5555, but it picks up the 444-4444 number and sends the fax.

    I am trying to understand why and where this takes place, in the application or WinFax Pro.

    I now have rebuilt the database in WinFax Pro.

    I hope all this helps.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.