ALDSP vs. Renaming Tables

I renamed a table in an SQL table and then used Workshop's 'update metadata' function to try to synchronize an ALDSP project that used the renamed table.  So now I had two physical data services for the renamed table, one for the old name and one for the new name.  The new data service had none of the relationships, presumably because ALDSP was not smart enough to find the foreign keys that involve the existing tables (fair enough).  So, I tried some hand surgery to copy the relationships from the old data service into the new.  Bad idea.  ALDSP kept trying to second guess me and started modifying (and even commenting out!) data service functions all over the place.  It got so tangled up that my only recourse was to blow away all the physical data services and rebuild them from scratch.  Ouch.  Moral of the story -- when you rename a table, hand edit the corresponding physical data service to match.