As part of an application I am developing I need to be able to create Calendar appointments programatically in LotusScript. Single non-repeating appointments are fine but I am having real problems with repeating appointments.
My method for creating the repeats was to start by manually creating a Repeating appointment and then look at the two documents that get created. The first is a parent document. The second is a response to this parent . This response doc is the actual document that appears in the calendar because it contains the CalendarDateTime item (which the parent does not).
I have looked through all the items on these two documents (including all the system $ items) and got my code to re-produce this situation exactly i.e my code creates two docs, one parent, and one response. Both docs contain all the items that the manually created ones do. I am using a doc compare tool to check this and everything is identical in terms of item types and item values.
However, it still doesn’t work 100%. With a manually created entry if you edit it, the invitees to the meeting appear in the embedded Scheduler. When you edit my automated ones, they do not.
Secondly, when I edit one of my documents, and get asked if I want to compose a msg to any invitees, I then get the error msg “no invitees to send notice to”. With a manually created document this works fine.
As I say, I have checked all the fields on the manually created docs and my ones and everything is identical. The SendTo item does not exist (neither does it exist on the manual one). The EnterSend to item is blank (as it is on the manual one). The AltRequiredNames and RequiredAttendees items both contain the names of the invitees (as they do on the manual doc).
And yet even though all the items are the same, they act differently when you open them up and edit them.
I’m looking through the Lotus code to see whats going on but its extremely complicated and hard to follow. Anyone else got this sort of thing working and have any clues for me??
This is a follow on from a previous posting on this subject - Bruce Stapely was kind enough to respond to that msg suggesting that he had done the same thing and got it to work. I got a bit further after that but have now come up again this problem.
Bruce if you see this, could you let me know if you managed to get this fully working - I think you tried something similar?
Thanks for any help you (or anyone) might have.
Richard
Thanks
Richard