Synch errors due to not dropping foreign keys?

[Marc Ford]

I consistently have synch problems after altering fields or adding new tables or fields and their relationships. If I delete the foreign keys surrounding the "problem" table in the target database, the synch process will complete successfully. It appears that Workbench needs to learn when to DROP foreign keys so that changes can be made, and then re-insert the foreign keys at the end of the script after the changes have been made.

When I synch 2 actual databases using SQLyog, their script shows this action. FK's dropped at the beginning, and then you seem them being reinserted at the end.

I really love the Workbench ERD tool and don't want to give it up, but synching will become unmanageable soon if I have to constantly delete foreign keys so the synch can take place.

Please let me know if I am in error...