I just had a weird problem when creating a new trigger on a custom object in my testing sandbox. I fired up Eclipse and opened my SF project, and all was well. I had added a couple of custom fields to my Contact object, but the schema was updated to reflect that. I had no error messages at that point.

Then I created a new trigger on the custom Membership__c object, setting it to fire After Insert, After Update, After Delete, After Undelete. The purpose of the trigger is to update the custom fields in the Contact object, making no changes to the child (lookup) Membership object.

But then the toolkit gave me an error, preventing me from saving the new trigger to the sandbox: "Conflict found while saving trigContactMembershipInfo.tgr. Remote instance has been updated since last save or sync. Use the Synchronize Perspective to resolve the conflict." I checked in SF, and the new trigger didn't yet exist on the Membership object.

So I tried explicitly sync'g, but the error wouldn't go away. When I deleted the new trigger, everything sync'd fine.

I have admin rights in SF and can author Apex code, so that's not the problem.

The only thing that finally worked was to create it using the toolkit wizard as a Before Insert trigger, then manually change the signature for the events I needed. Then I could save the trigger, no problem.

Any thoughts about why this is happening?

Thanks,
Don