Deleting old import specs

[Paintballlovr]

Is there an easy way to tell which import specs are currently being used and which ones aren't? I have an inherited database that has a bunch of import specs and I'm sure at least some of them are no longer being used, so I would like to clean them up. The reason for the spring cleaning is that I'm trying to export to the specs to another database and I'm getting an error that says "Not all of the import specs could be imported due to name conflicts" Since I need to fix some anyway, I figured I would clean out old ones so I'm not correcting ones that aren't needed anyway.

[JoeM]

Are files imported manually or by Macros or VBA?
If they are imported by Macros or VBA, you could search your VBA code and Macros for all the Import Specification names, and then delete the ones that are not found.

[Paintballlovr]

They are in macros and vba. I guess I can search the vba all at once, but is there a way to mass search macros or do I have to open each of them up? I ask because there are a LOT of macros in the database as well.

[JoeM]

but is there a way to mass search macros or do I have to open each of them up? I ask because there are a LOT of macros in the database as well.

I don't know of any way to search all the Macros at once. You might need to open each one. You should just be able to focus on the import Actions (TransferText).

[Paintballlovr]

Well, I guess I'll roll up my sleeves and dive in. Wish me luck.

[Paintballlovr]

Ok, here's a twist. I starting searching the VBA and I decided to search for acImportDelim and review the import spec and the very first one I find isn't even displayed in the list of import specs. Can there be import specs written somewhere that wouldn't show thru the advanced button on the inport text wizard?

[Paintballlovr]

nevermind, I'm an ID10T. The bogus specs are tied to dead forms or buttons.

[JoeM]

Sounds like that database needs a lot of clean-up!

[Paintballlovr]

I won't throw my predecessor completely under the bus, because a little bit of it is my own doing, but yes it does and most of it was here when I took it over. I have finished my review and here is the breakdown:

12 total import specs
5 being used between macros and vba (that I can find)

I'll make a backup copy and then delete the "extra" specs. Thanks for the guidance JoeM