OK, but this is not ideal. It means that CBSubs will get less and less tidy with loads of redundant plans. Surely it should be a design consideration to incorporate a "clean up" tool to allow administrators to remove old plans completely. If 15 plans are replaced annually, in 4 years you will have 60 redundant plans sitting around. If you equally have 5000 subscribers, then what you have said means an administrator needs to access 5000 members to unsubscribe them. Would you at least offer an SQL construct to remove these entries from the relevant tables cleanly so that plans can indeed be deleted?
If it is not already a design consideration for Plan maintenance, can you please consider this as well? D