1. Thank you so much for your time, if we can get this to go, it will save
us much time and headaches.

2. On your points 1 and 2, I have checked with our S-6 (thats Army slang
for the Command Staff Combat Geeks) and verified that item your item 1 is
satisfied. On item 2, I have to present buy-in from the players and our
Commander, plus a project file containing samples, functional specs, and
source code for their security inspection and approval. This is not a
problem, I can do that.

3. On your point three, I'm not certain if you intended this - but you
caused me to rethink part of my flow process. Instead of having the TC/AIMS
personnel (those who would create the message and actually attach the files
and send the message) fire the code that would process the file, I can have
the code on the read page and have the recipients do that processing.

Additionally, you mentioned that the only thing Outlook can do with a file
is save it as a file. Does that mean code embedded in the form cannot open
the file, parse it with the additional data from the form and then save the
file with a different (user specified) name?