Here's a question: If I want to re-name a membership level (as in the three-character code), I know it needs to be changed in T_MEMB_LEVEL and TX_CUST_MEMBERSHIP (because you can’t change it in the front-end). But there’s a foreign key constraint that catches you if you change either one of those. Is there a quick and easy way to get around that?
Cheers,
Matt
Hi Matt,
Theran MacNeil from Tessitura suggested the below which I am going to give a try. I will let you know how I make out.
---Arthur
Of course, if you have the SQL skills in-house, you could move all memberships that would be affected by the level code change out of TX_CUST_MEMBERSHIP and into a local table. With these memberships out of TX_CUST_MEMBERSHIP, you would then be able to update the level code(s) on the membership level(s). Then you would update the level codes on the memberships in your local table to the new value(s). Once the level codes in the local table match the new values, you can insert the memberships from the local table back into TX_CUST_MEMBERSHIP.