PowerBuilder and Default Printer Problem

  • Thread starter Thread starter Brett I. Holcomb
  • Start date Start date
B

Brett I. Holcomb

We have a strange problem that started about a year ago with a
PowerBuilder app that runs on Windows XP (SP2). This app gets the
printer information from an ini file and then when a print is requested
it saves the "HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Windows\Device" key value, replaces it with the
printer info from the ini file and then puts back the original value (at
the time this was the recommended method of printing). Sometime in the
last year this stopped working. The registry gets changed but the app
does not print. There were no changes in the application. I'm
wondering what could have caused this to stop working - does anyone have
any ideas? Were there any changes to the way things work in XP? The
app developers are looking at updating the app to use new features in
PowerBuilder's newer versions that eliminate the need to do this but I
am curious as to what might have happened?

Thanks.
 
Brett I. Holcomb said:
We have a strange problem that started about a year ago with a
PowerBuilder app that runs on Windows XP (SP2). This app gets the
printer information from an ini file and then when a print is requested
it saves the "HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Windows\Device" key value, replaces it with the
printer info from the ini file and then puts back the original value (at
the time this was the recommended method of printing). Sometime in the
last year this stopped working. The registry gets changed but the app
does not print. There were no changes in the application. I'm
wondering what could have caused this to stop working - does anyone have
any ideas? Were there any changes to the way things work in XP? The
app developers are looking at updating the app to use new features in
PowerBuilder's newer versions that eliminate the need to do this but I
am curious as to what might have happened?

Thanks.
Click to expand...
 
Brett I. Holcomb said:
We have a strange problem that started about a year ago with a
PowerBuilder app that runs on Windows XP (SP2). This app gets the
printer information from an ini file and then when a print is requested
it saves the "HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Windows\Device" key value, replaces it with the
printer info from the ini file and then puts back the original value (at
the time this was the recommended method of printing). Sometime in the
last year this stopped working. The registry gets changed but the app
does not print. There were no changes in the application. I'm
wondering what could have caused this to stop working - does anyone have
any ideas? Were there any changes to the way things work in XP? The
app developers are looking at updating the app to use new features in
PowerBuilder's newer versions that eliminate the need to do this but I
am curious as to what might have happened?

Thanks.
Click to expand...
 
It might be me but I got nothing except my message back with my text
quoted. Thanks.
 
Back
Top