Restricting user access in part of single template

cliffhanger

Hi,
We're using TS6.1. We have a shared template where multiple user groups have write access to different parts of the template. When the template is initialized- I check their usergroup and give appropriae access. Problem begins when they add a replicant, since there's no event to track addition of a replicant, all the fields become editable regardless of which group the user belong to.
Does anyone has any suggestion about how to handle this situation better??
I am thinking of adding onITemChange event for each field, but afraid of the overhead it would cause. Any expert analysis how severe the effect can be on performance?
Thanks
-cliffhanger

Adam Stoller

Do you have any hope of being able to upgrade to 6.5? 6.5's FormAPI contains a number of enhancements that should make this much easier for you (check out the webcast that was recorded earlier this week - it's pretty informative about the new features)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com