error handling overriding normal situation

[Shawn29316]

I have a button in my database with common error handling code. My problem is, there's a normal situation (no bids for a job) that I want to use a message box to explain to the user but the error handling takes over.

Private Sub btnSubmit_Click()
On Error GoTo Err_btnSubmit_Click
...
'below is what I want to happen if emplid is 0
If (rstPostings("EmplID")) = 0 Then
    MsgBox "There are no bids for this position"
Else
...
End If
...
'below is what takes over
Err_btnSubmit_Click:
    MsgBox "You Must Select 'Accepted' Or 'Rejected'"

I used the ... to replace a lot of code which works ok.

I'd appreciate any help you can provide!

[zmbd]

So what have you done to trouble shoot this? What error are you actually getting? You say your code that you've omitted works, yet, the error trap is invoking prior (?) to the section you've posted; thus, something doesn't work in your code that you've omitted for the situation you describe.

>>> Insert a STOP at the beginning of your code and step thru it.

You might want to also follow the troubleshooting section of:
[*] > Before Posting (VBA or SQL) Code
This may catch a few other bugs in the code :) .

[NeoPa]

If you have a special situation which you'd like to be handled differently from the default then you'll need to be able to recognise that situation in your error-handling code. Generally that will be a specific error number (Err.Number).

In your error handler you'll need to recognise the situation and follow different paths depending on the situation identified by your code.

[Shawn29316]

I've made a change since the first posting once I realized EmplID is a text field. Now it says:

If (rstPostings("EmplID")) = "" Then
 
    MsgBox "There are no bids for this position"
Else
...
Err_btnCommand18_Click:
    MsgBox "You Must Select the Job to be Filled"
 

As I step through the code, everything is fine if EmplID isn't blank but if it is, the code skips the "There are no bids for this position" message and goes to the "You must choose accepted or rejected" message.
I'm assuming the problem has to do with an error in the If statement but I can't figure it out.

[zmbd]

Change your testing from:
If (rstPostings("EmplID")) = "" Then

to
If (rstPostings("EmplID") & "") = "" Then

to be sure, it's a subtle change; however, more effective in catching both zero-string and null values.

[NeoPa]

In many cases fields that have no visible content are not empty strings, as you've tested for, but Nulls.

NB. Nulls are not values like strings and numbers are, but are a special value that rather indicate the lack of any usable value.

Unfortunately, String fields can be complicated as they can be set to allow empty string values as well as Nulls. Hence the complicated way to test for a string value with actual characters in it.

There are various possibilities for this :

If Nz(rstPostings("EmplID"), "") = "" Then ...
If (rstPostings("EmplID") & "") = "" Then ...
If Not rstPostings("EmplID") > "" Then ...

Personally, I prefer the last of those, but all would work reliably for you.