That's not what the Conflicts property does. It deals with copies of the item created when multiple users save changes at the same time.
What you should be doing is checking the given time interval for overlapping appointments by searching that interval; see http://www.outlookcode.com/d/finddate.htm -- Sue Mosher, Outlook MVP Author of Microsoft Outlook Programming: Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx
"fiznool[ at ]gmail.com" wrote:
[Quoted Text] > Hi, > > I am implementing a COM add-in in OL2003 which allows users to schedule > phone calls using an external soft-phone. I have created a custom form > which is based on the Appointment Item form, and have published it in > the Calendar folder, and so all of the appointment item properties are > available - including .Conflicts. > > I want to check that a new item to be added to my calendar does not > conflict with an existing calendar entry, and I believe the best way to > do this is to use the VBScript in the form itself and manipulate the > code in the Item_Write event, checking as the item is about to be > saved. I thought about using the .Conflicts property
|