Steven,

The way I addressed that problem on an application was as follows: I made a screen called 'Data Purge' or something like that. On that screen the users could check several checkboxes, then they press a button called 'Execute'. When Execute procedure ran it would go through sections of the application identified with each check box and literally take records out, and put such records instead into tables in an 'Archive' directory with tables in itidentical to the regular tables. Of course you have to have standards as to decide what records to purge out. Records older than some amount of time plus all related records I suppose. Then I made it so that Users could look at old archived data in screens in read-only fashion if they desired. When users did this once or twice a year it keeps table sizes down.

Wally