J
John Ford
This is related to my previous post "Item_Open = False Causes Outlook
to Abort" on this list.
I'm attempting to create a smooth, fool-proof method of deploying an
Outlook Form that goes into each user's Personal Forms Library. Here's
what I'm trying:
FormA is the one that the users want in their Personal Forms Library.
FormB contains VBScript in its Item_Open() function to publish
Attachment(1) (I insert FormA.oft as a file attachment to FormB).
After attaching FormA to FormB, I save FormB (in my Drafts folder).
Now, I write the user a nice email with instructions (let's call this
"FormC", even though it's just the standard Message form), and insert
FormB as an item-type attachment. The instructions say to open the
attached FormB and click "Enable" to the macro warnings. The
Item_Open() script in FormB publishes FormA to the user's Personal
Forms Library.
Works great so far - the user gets FormC in their inbox, opens it and
reads the instructions, and opens the attached FormB. But this leaves
FormB (as well as FormC) open on their desktop. So, I add "Item_Open =
False" to the script in FormB, so FormB will never pop up on their
screen - it will just publish and go away.
HOWEVER, when FormB has the Item_Open = False in its script, it causes
Outlook (2002, SP2) to die (with the option of sending info to
Microsoft). Is this because FormB was opened (as an attachment) from
FormC instead of an independant mail item?
Geez this sounds confusing - does this picture help?
FormC (tells user to open attachment & enable macros)
+--->FormB (its Item_Open publishes Attachment(1) [FormA])
+--->FormA (the form the user wants in Personal Forms Lib)
All I want the "intermediate" FormB to do is publish and go away.
Why can't I do "Item_Open = False" in FormB? (I tried Item.Close -
same results).
-jcf
to Abort" on this list.
I'm attempting to create a smooth, fool-proof method of deploying an
Outlook Form that goes into each user's Personal Forms Library. Here's
what I'm trying:
FormA is the one that the users want in their Personal Forms Library.
FormB contains VBScript in its Item_Open() function to publish
Attachment(1) (I insert FormA.oft as a file attachment to FormB).
After attaching FormA to FormB, I save FormB (in my Drafts folder).
Now, I write the user a nice email with instructions (let's call this
"FormC", even though it's just the standard Message form), and insert
FormB as an item-type attachment. The instructions say to open the
attached FormB and click "Enable" to the macro warnings. The
Item_Open() script in FormB publishes FormA to the user's Personal
Forms Library.
Works great so far - the user gets FormC in their inbox, opens it and
reads the instructions, and opens the attached FormB. But this leaves
FormB (as well as FormC) open on their desktop. So, I add "Item_Open =
False" to the script in FormB, so FormB will never pop up on their
screen - it will just publish and go away.
HOWEVER, when FormB has the Item_Open = False in its script, it causes
Outlook (2002, SP2) to die (with the option of sending info to
Microsoft). Is this because FormB was opened (as an attachment) from
FormC instead of an independant mail item?
Geez this sounds confusing - does this picture help?
FormC (tells user to open attachment & enable macros)
+--->FormB (its Item_Open publishes Attachment(1) [FormA])
+--->FormA (the form the user wants in Personal Forms Lib)
All I want the "intermediate" FormB to do is publish and go away.
Why can't I do "Item_Open = False" in FormB? (I tried Item.Close -
same results).
-jcf