I have an application written in VB which takes advantage of a Crystal report object.
My problem is when a user changes their default Windows printer while the application is open, Crystal reports does not recognize that the default printer has now been changed (the only way around this is to get the user to close the application and fire it up again - which is not what I want).
I may be way off base here but I am thinking it might have something to do with the fact that when I get the Crystal Reports object to print I give it the built-in Destination constant, cryptToPrinter which I suppose remains static throughout the running of the program.
Is there anyway of getting around this or is there something else going on that I am not aware of?
My problem is when a user changes their default Windows printer while the application is open, Crystal reports does not recognize that the default printer has now been changed (the only way around this is to get the user to close the application and fire it up again - which is not what I want).
I may be way off base here but I am thinking it might have something to do with the fact that when I get the Crystal Reports object to print I give it the built-in Destination constant, cryptToPrinter which I suppose remains static throughout the running of the program.
Is there anyway of getting around this or is there something else going on that I am not aware of?