Several months ago, an import was done that ended up to have a significant percentage of bad addresses.  Basically what we want to do is start over, get rid of all of those constituents and import a new list known to have correct addresses.  Our organization is farily new to importing, but I know that in the rules of import it states that a database backup is the only way to recover if an import goes wrong.  Since this was months ago, this is not an option for us.  

Can anyone offer up any ideas as to how we can just delete a large group of constituents who share the source code  and date?  Thanks in advance for any suggestions.

Cozette Savage

League to Save Lake Tahoe    

If you can query on the group then you can delete it.  If they all share the same created on date and source code it sounds like a fairly easy query. 

I would just do some checking to be sure none of these records have gifts, etc that would be lost if you delete the record.

The global delete has a number of flags that you can use to prevent a record from being deleted.  You can choose which flags to use and which to ignore.  I always run a pre-delete report first and use all of the available flags.  After scanning the exceptions, I evaluate which flags I can safely ignore and run the pre-delete report again with the new flag settings.  Sometimes, when the list is very large, I will do this in stages ignoring more flags at each stage.

Drew