Custom form isn't working on shared folder

  • Thread starter Thread starter Wilf
  • Start date Start date
W

Wilf

Pretty simple problem really but I'm stumped for a fix. The workaround
(emailing out the .oft and having everyone publish to their own personal
forms library) sucks, so what else can be wrong?

Create a custom form (based on contact folder), and it works fine if
published locally, but when published to the shared folder (note this isn't
MY folder) the form is unusable -- Object not found when trying to create a
new contact in that folder. Again -- the exact same form worked published
locally, but not when published to the shared folder.

I don't want to use the workaround as this will be shared by a LOT of people
and updates will need to be replicated manually. What else could be wrong?

Thanks.
 
I should probably add that the shared folder is, in fact, in a shared mailbox
as well. Not sure if it's relevant but another data point -- Outlook 2007.
 
If you are suggesting its the "allow script" settings -- been there; done
that. No effect. Same problem persists...
 
Did you restart Outlook after making the change to allow script to run on
forms in other mailboxes? Is the code running but raising an error? If so,
which statement is raising the error?
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
Restarted Outlook, rebooted, you name it -- we've tried it.

How would I know what statement is executing? I don't have VS installed so
how do I debug it?
 
What o/s? You only need VS on Vista. On Windows XP, you can install the "web
scripting" component from the Office installation. Alternatively, sprinkle
MsgBox statements throughout your form's code to track how far execution
gets.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
Unfortunately, this is Vista.

Sue Mosher said:
What o/s? You only need VS on Vista. On Windows XP, you can install the "web
scripting" component from the Office installation. Alternatively, sprinkle
MsgBox statements throughout your form's code to track how far execution
gets.
 
Back
Top