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.