If there is no order, the button should not be clickable (i.e. should be disabled), so it won't trigger the error -- and save the user the extra step of having to click the button.  VBA would be better suited here.  Whenever a customer is selected (Current event), check if the customer has any orders (with DCount), then enable or disable the button (by setting the button's Enabled property).  You can even show a tiny red text next to the button that says "No Order."

Kevin Thanks Kevin.  I have not gotten into VBA much yet.  Do you have a suggestion for one of Ricks videos that i can watch, or perhaps a suggested line of code...

Here is a Tech Help video on the Current event: https://www.youtube.com/watch?v=LgCbKyOr7lA .  The video requires you watch "Intro to VBA" first ( https://www.youtube.com/watch?v=uvmtcjJeBe4 ).  If you have done programming in other languages, it may be easier to pick up VBA.  VBA is based on Basic, one of the oldest and also the easiest language to learn.  In the early 80s, I was taught Basic in the 10th grade.  I've never taken any of Richard's courses, so I'll defer to him and his students regarding the exact path of taking his courses.

Hi Tim, Which form are you on when you try to open the order? In Richard's App the user navigates from Customer to  Orders for that customer, where the open button is. HTH John

Tim is thay double = signnormal?   try getting it down to 1 to start

I had an Aha moment and queried the customer list to include only those with orders, simplifying the list and making it easier.  Thansk for the help though.  I stillhave a lot to learn and I am having fun learning it!