See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The PatternEndDateproperty gets or sets a Variant time date object that represents the end date of the recurrence.
To get the value of the PatternEndDateproperty, call the property method described here.
To set the value of the PatternEndDateproperty, see the IRecurrencePattern::put_PatternEndDateproperty method.
Syntax
HRESULT get_PatternEndDate( DATE * pst ); |
Parameters
- pst
-
[out] Reference to a Variant time date object that represents the end date of the recurrence. For information on the DATEtype, see IPOutlookApp::VariantTimeToSystemTime. For information on the SYSTEMTIMEstructure, see SYSTEMTIME.
Return Value
This method returns the standard values E_INVALIDARG, E_OUTOFMEMORY, E_UNEXPECTED, and E_FAIL, as well as the following:
- S_OK
-
The method completed successfully.
Remarks
After you set this property, the Occurrencesproperty is set automatically when you save the task or appointment.
This property is not used if NoEndDateis TRUE.
To use, call put_NoEndDatewith a value of FALSE.
Requirements
| Header | pimstore.h |
| Library | Pimstore.lib |
| Windows Embedded CE | Windows CE 2.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |
See Also
Tasks
Creating a Recurring AppointmentReference
IRecurrencePattern::put_PatternEndDatePocket Outlook Object Model Interfaces
Other Resources
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.