As we're short of questions, thought I'd throw this in ...

I'm playing with someone else's problem, and probably trying to be a little too clever, and I can't get my error trapping to work properly. I'm going to be out most of next week so there's no urgency here; I just wondered what was happening and whether there's a way round it.

If I go to Print a Document (Ctrl-p or whatever), and give some erroneous input (enter "abc" in the Pages: textbox, for example) I get an error message popup - "This is not a valid print range" - and am then returned to the Dialog to correct it. All as you would expect.

Now, if I try and drive this from code ..

[VBA]
With Application.Dialogs(wdDialogFilePrint)
.Display
End With

[/VBA]

.. the Print Dialog is displayed. This time, if I enter "abc" in the Pages: textbox and press "OK", the dialog is refreshed with the invalid text blocked, but no error message popup. So I know what's wrong and I correct it, and press "OK" again. Control now returns to my code with an Error 5141 (This is not a valid print range) and the .Pages value is empty - it has neither the invalid "abc" nor the corrected "1". I have the error number and know what WAS wrong (if not the complete cause of it) so can tell the User, BUT the User has already corrected the problem and I do not have details of the correction so must ask them to supply the correct input again. No amount of error trapping makes any difference - control does not return to the code until there is no longer an error but it reports the error there was before correction.

Of course, as usual, I'm probably missing the blindingly obvious so what do I do to resolve it?