There are several ways I can think of that would do this, each has it's own merits. The method I would first try is by using a DTS object. In it's simplest version, it would first back up the database, then pull out the data to be archived and then delete the archived data from the live set. You can do a lot more sophisticated things than this: this only serves to demonstrate my preferred approach to your situation.

HTH

Ken

>Lynda,
>
>Are you using SQL Server or native tables? You could keep the data all in the same physical location and change your views/indexes as required.
>
>Renoir
>
>>That's not very practical from a business standpoint. History data is used in separate forms (only one field can be edited for example), used in different reports and has more and different indices. With about 15 years' worth of data to store, we really don't want it in the active transaction tables. We're trying to keep them "lean and mean" for the benefit of everyone, but especially remote users who only have dialup access <g>
>>
>>I've looked at BCP but it's a bit of a pain to have to drop and rebuild the indices each time. I thought there might be other options.