D
Dave Zatz
Howdy,
We are in the midst of migrating from a Windows NT/OL98 client to a
Win2k/OL'02 client. Some common tasks we accomplished in the older
version of Outlook are no longer permitted due to the security lock
down.
We're wondering if there are any simple work arounds or clever hacks
to accomplish our tasks, which we think are pretty simple and are
surprised Outlook won't support it.
The first thing we're trying to prevent are the security warning
regarding accessing the address book or sending mail on our behalf. We
want users to click on our custom Send button, or even the builtin
Send button, and to add a recipient which we call 'Archive.' In OL98,
when a user clicks our custom 'Send' button we simply used an
Item.Recipients.Add ("Archive"). This doesn't work without the error
messages in 2002. Also we attempted a simple Function Item_Send() with
the same thing, and this also gave us error messages... err 'security
warnings.'
The only work around I've found which gets us close is a suggestion by
Sue Mosher to resolve a recipient in the To field (we'll use CC
instead) and then remove the field from the form. The problem is, when
the users click on To: to access the address book they may delete the
Archive recipient.
Any other ideas?
Thanks for your help!
We are in the midst of migrating from a Windows NT/OL98 client to a
Win2k/OL'02 client. Some common tasks we accomplished in the older
version of Outlook are no longer permitted due to the security lock
down.
We're wondering if there are any simple work arounds or clever hacks
to accomplish our tasks, which we think are pretty simple and are
surprised Outlook won't support it.
The first thing we're trying to prevent are the security warning
regarding accessing the address book or sending mail on our behalf. We
want users to click on our custom Send button, or even the builtin
Send button, and to add a recipient which we call 'Archive.' In OL98,
when a user clicks our custom 'Send' button we simply used an
Item.Recipients.Add ("Archive"). This doesn't work without the error
messages in 2002. Also we attempted a simple Function Item_Send() with
the same thing, and this also gave us error messages... err 'security
warnings.'
The only work around I've found which gets us close is a suggestion by
Sue Mosher to resolve a recipient in the To field (we'll use CC
instead) and then remove the field from the form. The problem is, when
the users click on To: to access the address book they may delete the
Archive recipient.
Any other ideas?
Thanks for your help!