<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Code</title><link>https://www.infopathdev.com:443/forums/45.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: end-user management</title><link>https://www.infopathdev.com:443/forums/thread/14319.aspx</link><pubDate>Thu, 23 Feb 2006 02:14:28 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:14319</guid><dc:creator>Shanthi Reddy</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/14319.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&amp;PostID=14319</wfw:commentRss><description>I'm sorry maybe i don't understand the problem fully but it seems to me that you can use Optional sections. This way who ever does not want to enter data for certain areas can just delete that section. If they want to add information into those specific sections they would just insert it back.&lt;br /&gt;&lt;br /&gt;Let us know if you are actually looking for something different.&lt;br /&gt;&lt;br /&gt;Shanthi&lt;br /&gt;InfoPath Dev India</description></item><item><title>Re: end-user management</title><link>https://www.infopathdev.com:443/forums/thread/14318.aspx</link><pubDate>Mon, 20 Feb 2006 15:01:28 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:14318</guid><dc:creator>abadincrotch</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/14318.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&amp;PostID=14318</wfw:commentRss><description>I just found the xdExtension info ... looks like this might be somewhat feasible for us. Still seeking input however, thanks in advance!</description></item><item><title>end-user management</title><link>https://www.infopathdev.com:443/forums/thread/12780.aspx</link><pubDate>Mon, 20 Feb 2006 14:55:01 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:12780</guid><dc:creator>abadincrotch</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/12780.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&amp;PostID=12780</wfw:commentRss><description>Yes, I know InfoPath is supposed to make it easier to design and validate controls for the end user. However, we're hoping to restrict InfoPath's role for the end-user to merely filling out and saving a form. We would still like to be able to enable our end-users to alter the forms, however. At a minimum, we'd like to be able to set up a "universal" form that resides in one of our Sharepoint repositories. An end user, someone who typically carries out pre-sales assessments and the like, would be able to download this form, use our custom management tool, and "knock out" certain parts of the form that are irrelevant to their client, their line of business, their favored products, etc. etc. I know you can't programmatically add elements to the form, but could we programmatically hide elements that the user chooses to knock out?</description></item></channel></rss>