I figured it out. This is kind of an ugly hack but it works.
Under the XML View, look at the button properties. You should see one event. Now this can cause some wierd affects; you've been warned. I just added another from another button that did the emailing part (or WS part, whatever). So essentially I have two events for one button. Now if the Email Event is below the webservice Event, it won't give the user that nice dialog to print, which email client to use or just to save the XML locally. It will just fireup the default email client with the XML attached (which maybe a desireable outcome). It's not pretty, but it works.
.
.
.