In the Core 2 class there's a series of slides that covers this exact situation. The solution that they call the "best" is to put a case structure around each dialog box function so you can bypass it if there's an error. When teaching, I point out that this is really the 2nd best solution. The discussion goes something like this:
"The difference between an amateur and a professional LV developer is easy to see. Amateurs write programs, professionals write toolboxes. By that I mean professional developers are constantly asking themselves, 'Will I ever need to do this again?'
"So ask yourselves, is this the only time you will ever want to suppress a dialog box when an error occurs? No, of course not. The best solution therefore is to create a VI that encapsulates the dialog box function and the case structure, and brings out controls for all the existing inputs on the dialog function. Now whenever you need to do this same thing again you don't have to waste time thinking about how to do it again. You have a reusable VI already made to do it for you.
"Work this way for a while and you will have a toolbox of hundreds of simple, reusable pieces that will let you do amazing things in an amazingly short period of time."
Of course the builtin function should already come with error clusters on it, but that's a rant for another day. I hope you have found these ramblings helpful.
Mike...
