Posted in hope... still looking other places.
Our problem is this:
We are using V9, connecting to MS Outlook in NT. We want to be able to
either:
1) Connect as the current user of Outlook if it is active, or
2) Connect as the default Outlook profile if it is not active, or
3) Connect using a different profile, whether Outlook is or is not active.
Options 1) and 2) work fine for us; option 3) doesn't if Outlook is already
active.
V9 documentation on the CREATE Automation Object statement describes the use
of the CONNECT parameter, which supposedly controls the instantiation of the
object: If supplied, and the server is running, it connects to the existing
object. If omitted, a new instance of the server and object is created.
However, in actuality V9 connects to an existing server if it exists even if
the CONNECT parameter is not supplied. This causes a problem for us, because
it means if Outlook was already active, we can not use a different profile
without first killing the user's current session, which we don't want to do
(although one option would be to kill and restart).
Any one have any ideas on this, or experience with the problem? Any help
appreciated!
Dan Smith
Our problem is this:
We are using V9, connecting to MS Outlook in NT. We want to be able to
either:
1) Connect as the current user of Outlook if it is active, or
2) Connect as the default Outlook profile if it is not active, or
3) Connect using a different profile, whether Outlook is or is not active.
Options 1) and 2) work fine for us; option 3) doesn't if Outlook is already
active.
V9 documentation on the CREATE Automation Object statement describes the use
of the CONNECT parameter, which supposedly controls the instantiation of the
object: If supplied, and the server is running, it connects to the existing
object. If omitted, a new instance of the server and object is created.
However, in actuality V9 connects to an existing server if it exists even if
the CONNECT parameter is not supplied. This causes a problem for us, because
it means if Outlook was already active, we can not use a different profile
without first killing the user's current session, which we don't want to do
(although one option would be to kill and restart).
Any one have any ideas on this, or experience with the problem? Any help
appreciated!
Dan Smith
