data protection vs historical data help!!!

[handyman1]

I need help

I created a tblcustomer/ tbljobs database for a charitable handyman service to record customer's details their multiple jobs and handyman. This worked fine until new reporting system was requested. and data protection issues were raised.

In order to differentiate between current active customers and old inactive customers in the database I used to flag in/active customers and this was okay.

Now I have been asked to remove personal identifying information from old customer records but still allow the customer id,sex,age,joindate,local authority and job types,dates,handyman,timetaken etc. to be analysed for regular reports.

I am wondering about using a history table updated by query that would keep all non identifiable active and inactive customer/job records used for reports seperate from the customer table used by the receptionist to book jobs and find customer info.

I could then use the history table to create reports on service use etc.

Can anybody tell me how to set this up. I have tried several ways but run into trouble when a deceased client is deleted from the active customer table I cannot get the history table to hold on to the info.

Paul the handyman

 

[neileg]

If you're in the UK, I don't see how there is a difference in data protection terms between active and inactive customers?

However, if you want to mask the identity of inactive customers but retain their related data, then you should find it easier to overwrite their personal details rather than deleting the records.

 

[handyman1]

Masking unwanted data excellent thanks

I spoke to my boss about the data protection issue, something about only keeping personal info that is relevant and once customer has moved out of area or deceased (inactive) their personal info is not needed to compile reports for funders etc. but we need to analyse their age groups, sex, local authority, ethnicity etc.

What I have done is split the customer table in two, personal info tbl, and reporting info tbl both are accessed via a form based on a query that rejoins both tables, an inactive customer can be masked deleted whatever from personal info but stays in the reporting info tbl for monthly quarterly reports and historical comparison

works so far, lets see what happens when i rebuild the forms and reports

paul the handyman