<?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>Browser Forms</title><link>https://www.infopathdev.com:443/forums/40.aspx</link><description>For browser form specific questions</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Infopath 2010 - SP List - Multi Select List box - Guidance Needed</title><link>https://www.infopathdev.com:443/forums/thread/76766.aspx</link><pubDate>Thu, 22 Mar 2012 17:15:42 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:76766</guid><dc:creator>Anson Hidajat</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/76766.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&amp;PostID=76766</wfw:commentRss><description>&lt;p&gt;Filtering can be done on two levels: at the DB level and at the SP/InfoPath level.&amp;nbsp; There are advantages to both.&amp;nbsp; Typically I would recommend at the DB level since this will only access the necessary data from the DB instead of all the entries.&amp;nbsp; If your data set is very large, I would definitely recommend this approach.&amp;nbsp; The SP/IP level could be advantageous&amp;nbsp;if your data set is small to optimize for performance.&amp;nbsp; This would prevent multiple round trips between the form and the DB, but will require pulling in all the data at form load time.&lt;/p&gt;&lt;p&gt;I would recommend a single SP list and using filtering.&amp;nbsp; This will allow maintaining the list simpler than if you have 3 separate lists to manage.&amp;nbsp; It would also mean less data connections which is cleaner.&lt;/p&gt;&lt;p&gt;I believe filtering requires a postback in most cases, so I&amp;#39;m not sure if there is an easy workaround for this message.&amp;nbsp; You mentioned that you set the control to never postback, so that doesn&amp;#39;t seem to be a good solution.&amp;nbsp; Loading all of the data at form load might solve the postback, but not entirely sure.&lt;/p&gt;</description></item><item><title>Infopath 2010 - SP List - Multi Select List box - Guidance Needed</title><link>https://www.infopathdev.com:443/forums/thread/76693.aspx</link><pubDate>Wed, 21 Mar 2012 13:10:56 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:76693</guid><dc:creator>MStick</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/76693.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=40&amp;PostID=76693</wfw:commentRss><description>&lt;p&gt;New to Infopath and Sharepoint - have relational db background, that habit may need to be broken&lt;/p&gt;
&lt;p&gt;Using infopath 2010 browser form, sharepoint 2010 enterprise&lt;/p&gt;
&lt;p&gt;I have a sp list with fields: description, category, and status&lt;/p&gt;
&lt;p&gt;On the form are three multi select list boxes&amp;nbsp;that use the sp list filtered on category and status.&amp;nbsp; Status is being used to only pull the &amp;quot;Active&amp;quot; items in the list.&amp;nbsp; Is this type of historical integrity check needed in SP&amp;nbsp;or best left&amp;nbsp;in the db world?&amp;nbsp; Is this a &amp;quot;bad&amp;quot; practice?&amp;nbsp; &lt;/p&gt;
&lt;p&gt;The list boxes are being filtered on the control properties data connection.&amp;nbsp; Would it be a better practice to have three unique SP lists and remove the filtering?&lt;/p&gt;
&lt;p&gt;Each item selected in the list box forces a postback to the server and the &amp;quot;Sending data to the server&amp;quot; message displays even though the control browser setting is set to never postback.&amp;nbsp; How do you work around this?&lt;/p&gt;
&lt;p&gt;Appreciate any guidance.&lt;/p&gt;</description></item></channel></rss>