>> I've got a client that won't upgrade their app to 2.6 and we've needed to
>> access the Windows Printer dialog. I utilized some code that I have found
>> using FOXTOOLS using GETPROFILESTRING and WRITEPROFILESTRING, but fairly
>> often they get memory overflow errors. We are also seeing this on multiple
>> machines in our office as well. Has anyone written a "good" printer dialog
>> box for FPW? I also have a need for this in FPW 2.6 unless someone knows
>> of a way to override the selected printer from SYS(1037). I have an
>> application that pre-selects several printers for different reports. If
>> you use SYS(1037) and they select a different printer from default, that
>> printer overrides any printer set in Windows, so the automatic switching of
>> printers within the reporting won't work. It all goes to the last selected
>> printer. This is an aggravating "feature" of FPW. If anyone has any
>> thoughts, I would very much appreciate the ideas. I don't have a lot of
>> hair left to pull out!
>>
>> Rod Lewis
>> MS Consulting, Inc.
>> Minneapolis, MN
>>
>>
>>
>
>I realize this does nothing to solve your problem but it did bring up
>question for me. When using the sys(1037) well before a report is
>called in a program, how do you handle it if a user presses the
>cancel button in hopes of terminating a program. It returns
>an empty character string with no way to determine which button was
>pressed.
>Andy Roth
>Neyenesch Printers
>619 297 2281
>andyroth@electriciti.com

Currently I don't use SYS(1037) for this very reason. I wrote my own printer dialog (using many different routines supplied by other programmers and a few of my own). However, I am running into an out of memory error on many different machines in FPW 2.6 as well. I posted the second part of it to see if I could go "back" to SYS(1037). I think I can work around the "cancel" button if I can get the main issue out of the way.