Share via

2.2.1.44 PidLidAppointmentRecur Property

  • Article

Type: PtypBinary ([MS-OXCDATA] section 2.11.1)

The PidLidAppointmentRecur property ([MS-OXPROPS] section 2.22) specifies the dates and times when a recurring series occurs by using one of the recurrence patterns and ranges specified in this section. The value of this property also contains information about both modified and deleted exceptions and information such as dates, subject, location, and other properties of exceptions. The binary data in this property for Recurring Calendar objects is stored as the AppointmentRecurrencePattern structure specified in section 2.2.1.44.5. This property MUST NOT exist on single-instance Calendar objects.

The following are some limitations of recurrences:

  • Multiple instances cannot start on the same day.

  • Occurrences cannot overlap; specifically, an exception that modifies the start date of an instance in the recurring series can occur only on a date that is sometime after the end of the prior instance and before the start of the next instance in the recurring series. The same is true if the prior or next instance in the recurring series is an exception. Note that calculating exception overlap is an implementation-specific choice.<11>

The schedule of a recurring series is determined by its recurrence pattern and range. This section specifies the types of recurrence ranges and recurrence patterns that are supported by this protocol.

Recurrence Range

The recurrence range identifies how long the event will continue. This protocol supports three ranges:

  • Ends after a specific number of occurrences

  • Ends by a given date

  • Continues indefinitely

Recurrence Pattern

The recurrence pattern determines the frequency of an event. The RecurrencePattern structure (section 2.2.1.44.1) is also used to define recurring tasks, as specified in [MS-OXOTASK] section 2.2.2.2.15.

The following table lists the types of recurrences that are supported by this protocol.

Recurrence type

Description

Example

Daily recurrence

Schedules events according to one of the following patterns:

  • Every n number of days.

  • Every weekday.

An event that repeats every three days, starting on Monday, April 30, 2007, and continuing through Friday, June 8, 2007.

Weekly recurrence

Schedules events according to the following pattern:

  • Every n weeks on one or more particular days of the week.

An event repeats every two weeks, on Tuesdays, starting on Monday, April 30, 2007, and ending after five occurrences.

Monthly recurrence

Schedules events according to one of the following patterns:

  • On the nth day of every month.

  • On a specific day of the week on the first, second, third, fourth, or last week of every month (for example, the first Tuesday of the month).

An event that repeats on the fourth of every month, effective Monday, April 30, 2007, without an end date.

Every n months recurrence

A combination of the monthly and weekly patterns. An every n months pattern can schedule events according to one of the following patterns:

  • On the mth day every n months.

  • On any day of the week on the first, second, third, fourth, or last week every n months (for example, the third Thursday of the month).

An event that occurs on the last Thursday of every two months, effective March 12, 2007, with an end date of December 31, 2007.

Month end recurrence

Schedules events to repeat on the last day of every n months.

An event that repeats on the last day of every month, effective Monday, April 30, 2007, without an end date.

Yearly recurrence

Schedules events according to one of the following patterns:

  • On the mth day of the nth month, of every year.

  • On any day of the week on the first, second, third, fourth, or last week of the nth month, of every year.

The yearly recurrence pattern is based on a 12-month interval, and therefore uses the monthly recurrence parameters to represent all the yearly recurrences.

A birthday that occurs every June 22, and is an all-day event.