You've just created a new content type and re-used some of the existing fields from an existing content type for your new content type. Shortly thereafter, you've discovered the custom reporting queries to built based on your old content type don't work anymore. That's because CCK moved them to a new table. It's more efficient, right? Maybe not if you have to go modify all your existing queries in the sake of not duping a field in your database.
This module helps automate the reversal of the CCKism that splits fields into a separate table when you re-use an existing field.
Here is your second chance to move the fields back to their original table and re-create the fields on the new content type anew, like you should have in the first place.
This also spawned, the minimally maintained Anti Existing Field module.