Yes, that is all in tact. It's almost like Word VBA has it's own version of SET SAFETY but I've not been successful in locating where one might turn this off. I can't help but wonder if the ConfirmConversions:= parameter is being ignored (I have it set to False). This is the only one that even remotely looks like it might have an impact on my problem.

Dick