steveaubrey
MIS
Our application uses a registry setting in the course of printing. If there's a problem printing, that setting is one of the first things we check -- is it there, and is it set correctly.<br>
<br>
Sometimes we have something strange happen: no printing, but the registry entry exists and is correct.<br>
<br>
Then a stranger thing happens: deleting the entry and re-adding it (through a .reg file, so no mis-keying, just like the first time) enables the application to print.<br>
<br>
It's almost like the application (or the registry?) was not able to see the original entry.<br>
<br>
Is that possible? I know it is, because I've seen it and experienced it, but I don't like this kind of strangeness.<br>
<br>
Any ideas or suggestions?<br>
<br>
Thanks in advance,<br>
Steve
<br>
Sometimes we have something strange happen: no printing, but the registry entry exists and is correct.<br>
<br>
Then a stranger thing happens: deleting the entry and re-adding it (through a .reg file, so no mis-keying, just like the first time) enables the application to print.<br>
<br>
It's almost like the application (or the registry?) was not able to see the original entry.<br>
<br>
Is that possible? I know it is, because I've seen it and experienced it, but I don't like this kind of strangeness.<br>
<br>
Any ideas or suggestions?<br>
<br>
Thanks in advance,<br>
Steve