the storage of objects removed from the replicate table the secure location should be separate from the originating database containing the table data to be removed and is ideally an object oriented data environment with very strong access control attributes an example of an object oriented database suitable for this repository would be the strongbox u2122 product available from eaglehawk limited or the objectstore u00ae product available from progress software alternatively the secure location could be a relational or other database type utilizing very strong access control and possibly encryption of data next in step 240 the new primary key is replicated and stored into the secure location as an individual object fig7 shows a secure location 700 where the npk value 710 is stored finally in step 250 user specified data from the replicate table is replicated removed and stored as objects in the secure location for example fig6 shows a replicate table 600 with the data from field two 610 removed leaving a null or specious value as illustrated in fig7 the removed data bbbb is stored as an object in the secure location 700 in the end the contents of the secure location 700 will appear as a disjointed set of values to an unauthorized user the removed data of the replicate table is thus replicated in the secure location ensuring that no obvious relationship exists with the npk value to a user who does not have appropriate access rights the original table can then be deleted or removed from user access when a user or client needs access to the replicate table data including the removed data elements the flowchart steps.