> Is this due to some incompatibility between Outlook
> 2000 and Outlook 2003 or is there something else that I'm
> missing?
Yes, it is. Each Outlook Version has its own Outlook Object Model, and
Microsoft has not kept backward compatible. You need to include code
that determines which version of Outlook is running and to use the code
that is appropriate to OL2003 in one leg. How to tell? I am not sure,
but you might look on http://www.slipstick.com/, www.outlook-tips.net ,
http://www.outlookcode.com, Ken Slovak' site, or MicroEye.
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
Mukilteo, WA USA
Neil Dittmar - 02 Jan 2004 19:55 GMT
Hollis,
Thank you for your reply. In waiting for someone to
reply to my post, I started playing around with my form to
try and find out what exactly was hanging it up when
booking resources. Suprisingly, it seems to be any
VBScript code that is added to the form.
I started by taking all the VBScript code out of the
form, saving it, republishing it, and running it through
Outlook 2003. The resource successfully booked. As soon
as I added code into the Script Editor (I added "Option
Explicit" as the first line of the code with nothing
else), I then republished and re-ran the form and voila, I
got the error again.
I have a custom contacts form published on the same
machine and that appears to work fine. It seems to only
be an issue on the calendar form when booking resources.
If you or anyone else has any suggestions or
information, it would be greatly appreciated.
Thanks,
Neil Dittmar
Software Developer
Aurora Information Systems
>-----Original Message-----
>> Is this due to some incompatibility between Outlook
[quoted text clipped - 16 lines]
>
>.