How do you handle failed faxes and informing the user that the fax didn't go through? Currently the way I have it set up is the fax server can be polled via a flag in the database to request the status of the fax from winfax, then update the SQL record. Which in turn can be read by the client. This however isn't real time and is quite cumbersome for the user. I pondered using Winsock on the fax server component and the client to do real time status polling, but that adds another layer of complexity that I would like to avoid if possible.

Also how do you do have winfax set up to do dialing? Dial as Entered or use rules? Right now I use dial as entered and force the user to attach an area code if the number is long distance.

-Joe

>Gaylen
>
>I looked at this problem for a very long time. I played around with all sorts of expensive software and in the end I wrote my own faxserver. The principle is simple. The workstations send 2 pieces of information to a faxserver database on the faxserver.
>
>1. What record on the main database to access
>2. What report to run
>
>The faxserver polls the faxserver database every 5 minutes abd runs the required report using the central database record supplied. VFP reports are converted to faxes using a single copy of Winfax.
>
>It took me 2 days to write and it had been running without a problem for the last 2 months.
>
>Cost - almost zilch!!
>
>Colin Northway