Outlook 2003 & VBScript Code

[Neil Dittmar]

Hi Everyone,

I'm running into an issue programming a custom
calendar/appointment form in Outlook 2003 using VBScript.
The issue occurs if I try to book a resource using the
custom form. Everything else appears to be fine (VBScript
code runs as expected), however when I try to book a
resource I get the following error:

"The object could not be found. Unable to directly book a
resource for this meeting."

The strange thing is that I can book a resource using
the default Outlook 2003 appointment form. I can also
book a resource using my custom form if there is no
VBScript code behind it. The error only occurs when there
is any VBScript code behind the custom appointment form.
I have tested this by simply adding "Option Explicit" as
the only line of code in the editor, republishing the form
and attempting to create an appointment with an added
resource. It is specifically any code behind the
appointement form that causes it to error out. If anybody
has any suggestions or information regarding this issue,
it would be greatly appreciated.

Thanks,

Neil Dittmar
Software Developer
Aurora Information Systems

 

[Sue Mosher [MVP]]

I wonder if the fact that Outlook 2003, by default, doesn't run script in
other people's mailboxes is part of the problem. See
http://www.slipstick.com/dev/ol2003problems.htm#mailboxscript

 

[Neil Dittmar]

Thank you for the reply Sue. Looking into things a
bit further, I've found that if I publish my form to the
calendar of the resources mailbox, everything works fine
(resource books correctly, etc.) Although it makes things
work, this may be undesireable as the admin would have to
publish the custom form into the calendar of every
resource. If there are many resources, this would be very
time consuming. Does anybody have any thoughts as to why
this type of synchronization would need to be invoked and
most importantly, how I can get around having to do it in
the first place? It may be important to mention that my
server system is Small Business Server 2003 (Windows 2003
Server / Exchange 2003 Server). Any ideas or suggestions
would be greatly appreciated.

Thanks,

Neil Dittmar
Software Developer
Aurora Information Systems