Legecy fax usage

>I realize this is not the correct newsgroup but all the others seem to be
> full of porn.
>
>
>
> I have a very large legacy application (written in VB3
>
> currently running under WIN98) that I am attempting to get to print to the
> shared fax on WIN2003 server. The shared fax has been locally set up as
> print device. Printing from any other windows product operates correctly.
> I.E. the fax window opens and the printed material appears in the fax.
>
>
>
> In the past the application captured the current default printer, switched
> the default printer to the fax printer, printed the fax and then switched
> back to the original printer. This worked when the fax application was
> installed on the local machine.
>
>
>
> After changing the local fax to the shared fax printing the application is
> not able to print to the fax. When the application attempts to print to
> the
> shared fax the fax window does not open at all.
>
>
>
> I am confused why anything printing to the fax device does not
> function in the same manner.
>
>
>
> I realize I am asking a question that seems not worth dealing with. The
> obvious answer is to upgrade the legacy application.
>
>
>
> However the company involved is very small and cannot afford the costs
> involved. The legacy application has evolved over 10 years, is very large,
> meets all the clients needs, relies heavily on database and development
> tools that are not available in current development environments, and the
> company requires the application to operate.
>
>
>
> I need to determine a way to accomplish this.
>
>
>
> For example printing to a .prn file and then shelling an application that
> transfers the .prn file to the fax or some manner of loading the shared
> fax
> application with a .prn file as input?
>
>
>
>
> --
> rykk
>
> C. Richard Jamieson
> WIM Consulting
> Sales@WIM.ca
> Phone (780) 464-2214
> Cell (780) 992-2221
> Fax (780) 467-2583
>
>