Hi all, I need to develop an application/service that does 2 things: 1.Syncronize a calendar in an exchange 2003 public folder to an SQL database. 2.Syncronize contacts from an sql database to exchange shared contacts. I've been looking at the sdk and see there is a section on WebDAV replication. From what I can tell exchange can work out based on the "<R:collblob> field if anything has changed since the last time exchange was queried. After running the "Fetch an Update Manifest" example i get: 1 resources changed, deleted, or new... Resource changetype: new Resource URL: http://fridge/public/SourceCalendar/Testing%20new%20calendar-46633 6846.EML Status: HTTP/1.1 200 OK Property name: a:displayname Property value: Testing new calendar-466336846.EML Property name: a:href Property value: http://fridge/public/SourceCalendar/Testing%20new%20calendar-4 66336846.EML Property name: e:importance Property value: 1 Property name: d:resourcetag Property value: rt:6c635c592ab4f84397568646ea28221500000000b40d6c635c592ab4f84397568646ea28221500000000b612 Status: HTTP/1.1 404 Resource Not Found Property name: e:size This is great because I can modify this to get the information i need to do an update to the sql database. The only issues i have is the collblog didn't update. So next time i make changes I will the next stuff and the stuff that changed last time. I'm just a little confused about how this works. Would someone be able to explain? Btw, if you can think of a better way to do this please let me know. -- ********************** Jacob
With the collblob you need to stored the value you receive after the initial query and then the next time you make a request submit this collblob value you stored you will then receive an updated collblob (if anything has changed) which you then need to store again and submit with the next query and so on. The thing to watch when your dealing with calendar items is that you always need to submit a fixed query eg you can cant keep changing the time window in your query because this will just keep generating a new collblob. The other problem is if you then submit a query of a calendar without a time window you'll find that recurring meeting wont expand. cheers Glen "Jacob" <junk@hfws.net.nospam> wrote in message news:4DA02E53-532B-4BB6-9F99-572D1CDE756D@microsoft.com... > Hi all, > I need to develop an application/service that does 2 things: > > 1.Syncronize a calendar in an exchange 2003 public folder to an SQL > database. > > 2.Syncronize contacts from an sql database to exchange shared contacts. > > I've been looking at the sdk and see there is a section on WebDAV > replication. From what I can tell exchange can work out based on the > "<R:collblob> field if anything has changed since the last time exchange > was > queried. After running the "Fetch an Update Manifest" example i get: > > 1 resources changed, deleted, or new... > Resource changetype: new > Resource URL: > http://fridge/public/SourceCalendar/Testing%20new%20calendar-46633 > 6846.EML > Status: HTTP/1.1 200 OK > Property name: a:displayname > Property value: Testing new calendar-466336846.EML > Property name: a:href > Property value: > http://fridge/public/SourceCalendar/Testing%20new%20calendar-4 > 66336846.EML > Property name: e:importance > Property value: 1 > Property name: d:resourcetag > Property value: > rt:6c635c592ab4f84397568646ea28221500000000b40d6c635c592ab4f84397568646ea28221500000000b612 > Status: HTTP/1.1 404 Resource Not Found > Property name: e:size > > This is great because I can modify this to get the information i need to > do > an update to the sql database. The only issues i have is the collblog > didn't > update. So next time i make changes I will the next stuff and the stuff > that > changed last time. I'm just a little confused about how this works. Would > someone be able to explain? > > Btw, if you can think of a better way to do this please let me know. > -- > ********************** > Jacob >
Hello, an additional constratint is, that the timeframe cannot exceed 732 day (two leapyears). Best regards, Henning Krause "Glen Scales [MVP]" wrote in message news:ekKNPvGVHHA.1432@TK2MSFTNGP02.phx.gbl... > With the collblob you need to stored the value you receive after the > initial query and then the next time you make a request submit this > collblob value you stored you will then receive an updated collblob (if > anything has changed) which you then need to store again and submit with > the next query and so on. The thing to watch when your dealing with > calendar items is that you always need to submit a fixed query eg you can > cant keep changing the time window in your query because this will just > keep generating a new collblob. The other problem is if you then submit a > query of a calendar without a time window you'll find that recurring > meeting wont expand. > > cheers > Glen > > "Jacob" <junk@hfws.net.nospam> wrote in message > news:4DA02E53-532B-4BB6-9F99-572D1CDE756D@microsoft.com... >> Hi all, >> I need to develop an application/service that does 2 things: >> >> 1.Syncronize a calendar in an exchange 2003 public folder to an SQL >> database. >> >> 2.Syncronize contacts from an sql database to exchange shared contacts. >> >> I've been looking at the sdk and see there is a section on WebDAV >> replication. From what I can tell exchange can work out based on the >> "<R:collblob> field if anything has changed since the last time exchange >> was >> queried. After running the "Fetch an Update Manifest" example i get: >> >> 1 resources changed, deleted, or new... >> Resource changetype: new >> Resource URL: >> http://fridge/public/SourceCalendar/Testing%20new%20calendar-46633 >> 6846.EML >> Status: HTTP/1.1 200 OK >> Property name: a:displayname >> Property value: Testing new calendar-466336846.EML >> Property name: a:href >> Property value: >> http://fridge/public/SourceCalendar/Testing%20new%20calendar-4 >> 66336846.EML >> Property name: e:importance >> Property value: 1 >> Property name: d:resourcetag >> Property value: >> rt:6c635c592ab4f84397568646ea28221500000000b40d6c635c592ab4f84397568646ea28221500000000b612 >> Status: HTTP/1.1 404 Resource Not Found >> Property name: e:size >> >> This is great because I can modify this to get the information i need to >> do >> an update to the sql database. The only issues i have is the collblog >> didn't >> update. So next time i make changes I will the next stuff and the stuff >> that >> changed last time. I'm just a little confused about how this works. Would >> someone be able to explain? >> >> Btw, if you can think of a better way to do this please let me know. >> -- >> ********************** >> Jacob >> > >
