Delphi Component : Appointments with Exchange / Outlook

• Project ID:

  788661

• Project Type:

  Fixed

• Budget:

  $30-$250 USD
  

Project Description:

I am looking for a developer to produce a Delphi 2010 Component (with source) that will provide the following functionality for applications to interface with Microsoft Exchange and therefore to the Users Outlook Calendar.

Calendar Entry to Outlook Via MS Exchange
Required Fields
Username : String
Start : TDateTime
End: TDateTime
AllDayEvent : Boolean ;
ShowAs:[busy,free,tentative,outofoffice]
Private:Boolean
Reminder: dd hh mm
Subject:String
Body:WideString
Location:String
File Attachment (via Filename) : String

Methods / Functions:
Add Appointment; //uses fields above to add to the users calendar
Delete Appointment(...)
Update Appointment(....)
FindAppointment(User:String;SubjContains:String;Start:TDateTime;End:TDateTime):TaAppointment

Events:
OnBeforeCreateAppt
OnAfterCreateAppt
OnBeforeDeleteAppt(CanDelete:Boolean)
OnAfterDeleteAppt
OnBeforeUpdateAppt
OnAfterUpdateAppt
OnStatus(message:string)
OnError(errorcode:integer;errortext:string)


The component should take as many of the fields as necessary and then add the entry to the specified users calendar by passing the appointment to exchange (could use CDO, but must allow for use with exchange 2003, 2007 and 2010)

The component must have the ability to find an existing appointment or range of appointments that correspond to the search criteria passed and then return these as a list of TaAppointment objects that can be referenced so that they can be passed to the Delete or Update Functions for deletion or updating as required:

e.g. in Pseudo Code ...
MyAppointments : TAppointmentList ;
i : integer ;
Begin
MyAppointments.Create;
Try
MyAppointments := myOutlook.FindAppointments('Fred Smith','test',nil,nil,nil);
For i : 0 to MyAppointments - 1 do
Begin
myOutlook.DeleteAppointment(myAppointments[i]);
End;
Finally
MyAppointments.Free;
End;

So the Appoinments can be held within a list object for easy referencing.

Events should be fired before and after each method/Function with relevant information such as error codes and status codes with text where available should be provided.
Status Codes and Error Codes should be provided when returned


All code should be Delphi or ASM
All Functions / Methods require documenting in the source as to the basic functionality of the code fragment
The Component should only rely on the installed standard delphi components and not require any third party component sets for operation
Full Source must be supplied
All functions will be tested on completion and all errors to be resolved
Payment Terms are 40% on Start 40% on supply of completed Component and 20% after testing and acceptance

If this project is completed successfully, the same type of component for Tasks will be required.

Skills required:

Delphi