Contact Linking Problem

  • Thread starter Thread starter Mike Hains
  • Start date Start date
M

Mike Hains

Using menu-bar functions, linking contacts in Public
Folders with other Public Folder contacts works fine.
Anyone on our network can see and use any links created
by anyone else.

- HOWEVER -

When creating links with VBA, the links are visible on
the other machines ... BUT cannot be opened. The other
machines show a "permissions" error. Changing
permissions doesn't make any difference - everyone can
have "owner" permission and it still doesn't work.

The code I am using follows the example in the MS Help
files, and is as follows:


If Not TypeName(LinkedContact) = "Nothing" Then
LinkFormSelectedFile.Links.Add (LinkedContact)
LinkFormSelectedFile.Save
Hide
Else
MsgBox "Link not selected correctly",
vbOKOnly, "Error"
End If


It seems that linking using the code adds some kind of
permission issue ... making the link "local" or something
similar.

I would very much appreciate help to solve this
(aggravating and several-month-long) issue.

Thanks in advance, MJH
 
Hi, Mike!

There is a place in the Options Security tab where you can click a box to allow macros from other mailboxes to run in the user's profile. I'm not on Exchange so I can't remember the exact path to get there. Hope this is helpful!
 
"macros" don't reside in mailboxes. "macros" are VBA procedures, local to
each user.

Maybe you're thinking of being able to run script from custom forms for
items in other users' mailboxes? That setting is on the Tools | Options |
Other | Advanced Options dialog.

But I don't think it has anything to do with the performance of linked
contacts. I've never heard of that problem. It would be useful to know the
exact text of the permissions error message.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Reb DeWinter said:
Hi, Mike!

There is a place in the Options Security tab where you can click a box to
Click to expand...
allow macros from other mailboxes to run in the user's profile. I'm not on
Exchange so I can't remember the exact path to get there. Hope this is
helpful!
 
Sorry for the poor symantics. If you are using VB code to create the links which is what it looks like is going on here, then if that code is being executed from VB Script or possibly a COM Add-in loaded for one of the shared mail boxes (i.e. other than the one it is being accessed from), then that is where I could see this problem popping up. I just mention this because it happened to me and checking off the aforementioned box fixed the problem.
--
Thanks and best regards,

Reb Dewinter


Sue Mosher said:
"macros" don't reside in mailboxes. "macros" are VBA procedures, local to
each user.

Maybe you're thinking of being able to run script from custom forms for
items in other users' mailboxes? That setting is on the Tools | Options |
Other | Advanced Options dialog.

But I don't think it has anything to do with the performance of linked
contacts. I've never heard of that problem. It would be useful to know the
exact text of the permissions error message.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Reb DeWinter said:
Hi, Mike!

There is a place in the Options Security tab where you can click a box to
Click to expand...
allow macros from other mailboxes to run in the user's profile. I'm not on
Exchange so I can't remember the exact path to get there. Hope this is
helpful!
Click to expand...
 
Mike,

Here is the path I was looking for:

#1: Outlook 2003 includes a new setting -- turned off by default -- to allow
forms in shared mailboxes to run script. You can change the setting by
choosing Tools | Options | Other | Advanced Options and checking the box for
Allow script in shared folders. See
http://www.outlookcode.com/d/ol2003problems.htm#mailboxscript for more
information on this setting and a comparable one (on by default) for public
folders.

Of course this only fixes the problem if your code is being run from VB Script within the form.
 
Back
Top