RE: exw.exe (when 4..0.0) and Win32lib
Yep. But it is not anything new to Win32lib that is causing this as I
have gone back through all the win32libs I have back to v50c and they
all get an error message when calling getPrinter function.
You can test this using the print menu option from Generic.exw in Demos
in the distribution.
--judith
Derek Parnell wrote:
> ----- Original Message -----
> From: "Judith Evans" <camping at txcyber.com>
> To: "EUforum" <EUforum at topica.com>
> Subject: exw.exe (when 4..0.0) and Win32lib
>
>
> > Hi All,
> >
> > Now I remember why I used exw.exe as 3.1 for so long; exw.exe as 4.0 and
> > Win32lib will not allow printing from my exw program. Although I can
> > bind it (I guess my bind.exe is still 3.1) and print ok. This has me a
> > bit worried if RDS is going to issue Eu 2.4 with exw.exe as 4.0. and
> > bind.exe as 4.0 also. I like the effect of Windows as 4.0 but certainly
> > don't want to be converting back and forth for those applications that
> > need to print data.
> >
> > If I recall correctly there was some discussion on Topica about this
> > quite awhile ago but when doing a search on messages I can't locate if
> > there was any solution with Win32lib. Does anyone remember this?
> > --judith
> >
> >
> > TOPICA - Start your own email discussion group. FREE!
> I don't recall this being discussed, Judith. Are you saying that if
> exw.exe
> is a 4.0 program then win32lib programs fail to print?
>
> ----------------
> cheers,
> Derek Parnell
>
>
|
Not Categorized, Please Help
|
|
