Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

error in printing

Posted on 2014-09-29
8
Medium Priority
?
120 Views
Last Modified: 2014-10-06
I have a form that users are printing and sporatically they get a runtime error.  I think I narrowed it down to this section of code:

If MsgBox("Would you like to print this record?", vbYesNo Or vbQuestion, "Print Record") = vbYes Then
Me.PrintForm
Printer.Print ""
Printer.PaintPicture Picture2.Picture, 0, 0, 12000, 12000
Printer.EndDoc
End If

Open in new window


When they click Yes, they get an error sometimes.  Is there  a better way to print Picture2?
0
Comment
Question by:al4629740
  • 5
  • 3
8 Comments
 
LVL 49

Expert Comment

by:Martin Liss
ID: 40350228
What error do they get?
0
 

Author Comment

by:al4629740
ID: 40350481
I wish I could get them to write it down, but it is a runtime error.  I don't get an error.
0
 
LVL 49

Expert Comment

by:Martin Liss
ID: 40350649
Some thoughts:
What's different about your customer(s) with the problem? Different OS? Different printer?
Is it always the same customer?
Is it always the same picture?
There's code out there that you could add to your project that would send you an email containing the error information when the error occurs.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:al4629740
ID: 40351135
Can I send the code to the database when An error occurs
0
 
LVL 49

Expert Comment

by:Martin Liss
ID: 40351150
You can do anything you want.
0
 

Author Comment

by:al4629740
ID: 40357900
Can you provide a good example that would retrieve the error and send to db by chance
0
 
LVL 49

Accepted Solution

by:
Martin Liss earned 2000 total points
ID: 40358179
No I can't but if you are already writing to a database from the application then it should be easy to add a new table for the errors and in that table include things like the user's name, err.number, erl (the line number where the error occurred), and the name of the procedure where the error occurred. For help with the latter take a look at my Automatic Insertion of Procedure Names add in.
0
 
LVL 49

Expert Comment

by:Martin Liss
ID: 40364644
I'm glad I was able to help.

In my profile you'll find links to some articles I've written that may interest you.
Marty - MVP 2009 to 2014
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The debugging module of the VB 6 IDE can be accessed by way of the Debug menu item. That menu item can normally be found in the IDE's main menu line as shown in this picture.   There is also a companion Debug Toolbar that looks like the followin…
When trying to find the cause of a problem in VBA or VB6 it's often valuable to know what procedures were executed prior to the error. You can use the Call Stack for that but it is often inadequate because it may show procedures you aren't intereste…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
Suggested Courses

877 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question