VB6 does not see the default printer. Need to set VB printer to nothing for troubleshooting

My app is VB6 with Crystal Reports 6 Professional.  I have a user running this app on a Windows 7 machine.  At some point, VB stops seeing the default printer, so if she does a preview onscreen of the report, the printer icon is grayed out.  If she exits the app and comes back in, it is fine.  At least for a while.

This problem only occurs on this one pc.  Many other PC's running the app are fine.

I'm trying to come up with some code to detect this condition and call crystal.printerselect so she can select a printer and not get the grayed out icon.

I've tried all manner of setting the printer, changing the default printer, etc., but I want to set the VB6 printer name to null or nothing so I can see if my fix is going to work.

Any suggestions or ideas to solve this would be much appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

How are you running the report?

Skip_LaughlinAuthor Commented:
Out of VB.  Very simple.

Crystal1.DataFiles(0) = "somemdb"
Crystal1.ReportFileName = "report name.rpt"
Crystal1.Destination = 0
Crystal1.Action = 1
Your method is probably the issue.

You are using way out dated methods that I am surprised even work in Win 7.

I don't know of any way to capture the printer information or change it using the OCX.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Skip_LaughlinAuthor Commented:
Thanks.  Only thing I've found is that W7 isn't forgiving as all earlier Windows versions in treating strings and values.  I accidentally found out that in XP and earlier, I could evaluate 1000 as a string or as a value.  Not in W7.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.