relationship dilemma

[Anti-Rich]

hi all,

i have a problem, and i was hoping someone could help me work through it or around it. i have a table in my database called tblLocation and that stores the names of sites that my company has warehouses at. now, the program i am creating will use the locationid throughout the database. but if i want to remove a site (say, if a site gets shut down), i want to keep all the 'child' data throughout the database (auditable data trail). is there anyway to do this without violating the databases relationships?

im open to any suggestions

cheers
adam

 

[vis781]

For this case (data trail for audit purposes) i would be very reluctant to delete anything from the database but then some of the people i have worked for have been very picky about being able to delete information, they wanted to keep everything!! So if it were me i think i would just have a column that says Active Or InActive.

 

[Anti-Rich]

hi vis

cheers for you reply, i was considering the same thing after i posted. it seems the only way to make all parties happy. ill just stick a bit type in there 0 is active 1 is inactive.


thanks for your feedback

have a good one
adam