Error code to prevent error messages

[sanal]

I have used event proceedure in a click event of a button to open a report. Sometime certain error messages are occurred due to certain wrong user input such as null value in a field. I have tried to use my own error handlers in the code but not succeeded. Hence will you please inform me the correct code to suppress the system error messages and to show my own error messages such as "Avoid null value in the field..."etc.

[June7]

Prevent the bad input.

Set fields as Required in table.

Use ValidationRule and ValidationText properties.

Validate data input before record committed table.

Validate user inputs for filter criteria before opening report.

For error handler, review http://allenbrowne.com/ser-23a.html

[orange]

sanal,

Further to June's good advice, I recommend you do some searching google and/or youtube for Examples of Error Handling with Access vba

Paul Kelly has a great article of VBA Error Handling. He is an Excel guru, but the material is applicable to vba--so is relevant to Access.

Error handling by Allen Browne.

[sanal]

THANK YOU for the advice. As per your directions the error handler I created is as follows.Now it seems to be working but I am not sure. Please verify the code and inform me your valuable suggestions. I have also used the No data event of the report to prevent the opening of the report if there is no data.

Private Sub Command138_Click()
On Error GoTo Err_Command138_Click

DoCmd.OpenReport "Bill59C", acViewPreview
Exit_Command138_Click:
Exit Sub
Err_Command138_Click:
Select Case Err.Number
Case 440
Resume Next
Case Else
MsgBox Err.Description, vbDefaultButton1, "PF TAP"
Resume Exit_Command138_Click
End Select

End Sub

I eagerly waiting for your suggestions and help. Thanks in advance.

[orange]

You should use code tags when posting code.
Your code will be easier to read and debug and maintain if you do some consistent indenting.ms access error 440

Private Sub Command138_Click()
    On Error GoTo Err_Command138_Click

    DoCmd.OpenReport "Bill59C", acViewPreview
Exit_Command138_Click:
    Exit Sub
Err_Command138_Click:
    Select Case Err.number
    Case 440
        Resume Next
    Case Else
        MsgBox Err.Description, vbDefaultButton1, "PF TAP"
        Resume Exit_Command138_Click
    End Select

End Sub

What exactly is error 440? Why did you choose to Resume Next?

[sanal]

lam only a beginner in programming . I want to suppres the error messages related to the Error No.440. Please help me to rewrite the code.

[Minty]

Error 440 is an "Automation error" - which I don't understand if you are simply opening a report.
Remove the error handler and show us where it goes wrong in the code, If it's when it opens the report then show the code in the Report.

[isladogs]

As a general rule, you should only suppress error messages if you know they can be ignored without harm
In the case of an automation error you definitely need to identify the cause

Try opening the same report from the navigation pane. Does that work?
Try opening another report (or form) from that button code. Does that work?

Doing both of these will help identify whether the issue os the report itself (possibly corrupted) or the source form with the button code

[sanal]

I have used a function in a textbox in the report to convert number to words. The error Occured when the reports has no data . There seem to be no harm if the error is ignored. Pl help me to rewrite the error handler to ignore the error.

[isladogs]

Suggest you add code to the NoData event in the report to manage that situation and/or add error handling to the number to words function e.g use Nz function

[Minty]

As Ridders suggests , you should fix the data issue in the function, not cludge around the result of the poor or missing data.
This will make your process much more robust and is by far the best practice

[June7]

Prevent the bad input.

If the issue is only some records do not have value in the field, as suggested, use Nz(): MyFunction(Nz([fieldname]))