I was able to solve my problem by :
 - downloading the calendar to a local ics file
 - writing some code to remove duplicates from the file
 - deleting all events on my wife's primary calendar
 - importing the clean file

I have code if anyone is interested...

Franko


On Aug 30, 8:06 am, DrW <[EMAIL PROTECTED]> wrote:
> It's now Saturday and I am getting the same error on her account.
>
> I added some duplicate events to my account and the code cleaned them
> up with no problems.
>
> I wonder what is happening with her account?
>
> Franko
>
> On Aug 29, 3:35 pm, DrW <[EMAIL PROTECTED]> wrote:
>
> > My wife is having major problems with her google calendar.  Most of
> > the events on her calendar are duplicated multiple times...I think
> > this is a goosync issue.
>
> > I wrote a simple python program using the gdata api to delete
> > duplicates. It gets a list of events by day and deletes the
> > duplicates.
>
> > When I put it in test mode, it seems to be working fine. It finds the
> > duplicates and prints out "delete event" (in test mode, it doesn't
> > actual call "DeleteEvent(href)". )
>
> > When I take it out of test mode, it dies when it tries to actually
> > delete an event. I get a :
> >   403 : "User has modified too many events today. Please try again
> > tomorrow." exception.
>
> > I have only been test it for an hour or so. To the best of my
> > knowledge I have only deleted 1 or 2 events using my program.
>
> >  - Does anyone know a work around?
> >  - Does anyone know how many events you can "modify" on a given day?
> >  - Is there already a tool out there that works to delete duplicates?
>
> > Thanks
> >    Franko

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to