General information
Category:
Windows API functions
David,
The weird thing is that the call to ShellExecute() to run this little print utility works fine here in development, but on the test machines an error code of 5 is generated. In my tests here in dev I've renamed the utility so that ShellExecute can't find it, and I get the expected error code of 2, not 5.
Is there an alternative way to achieve the same desired effect of not having the DOS session window flashing up on the screen?
TIAFAH,
Bruce
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only