Michael,
I know what you're trying to do with the set focus, and I had tried to go down that path before as well. Unfortunately I've never been able to call the setFocus on a prePrint event. While it makes logical sense that if you set focus on some field as the first step in your preprint process that the exit event would be called on the input field, and your concatenation would work because the user would no longer be in the input field. Unfortunately this does not work. You really are limited by this, but again you can get around all this by using a print button on your form. One way to help cope with the fact that a user can still select print from the menu options, is to tie a hidden print flag field to the print button. This flag would only be set to true if the print button is pressed (set in the click event). In the preprint event you can then check for this flag. If it is set to false (print button was not pressed) then you could display a message box to the user telling them that certain functionality requires them to print using the print button on the form. This way you are at least telling the user that the printed form will not look correct/have the right information unless the print button is used. At this point you're really just trying to find a workaround solution for the limitation of a field having focus on a preprint event, and not having the data that was entered in that field acknowledged by the system. Hope this helps, or gives you an idea of how to overcome this limitation for your situation.