yes, we are still using visual studio 2005 for our development, although we hope to cut over to 2010 in the next few weeks. anyways, a customer was having problems printing reports to a particular printer, and from previous research i knew the problem was turning the “No Printer” option on in the crystal reports designer. now we have a lot of reports, so i wanted to automate this process for all our reports. so i turned to the built-in scripting functions of visual studio, however, it turns out that you can’t control dialogs through macros. so one person recommended using autohotkey, and i had a basic knowledge of that, so I would give it a try.

Continue reading