<?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>General</title><link>https://www.infopathdev.com:443/forums/41.aspx</link><description>If you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Setting value of a query field</title><link>https://www.infopathdev.com:443/forums/thread/19605.aspx</link><pubDate>Sun, 06 May 2007 03:39:10 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:19605</guid><dc:creator>Matt Faus</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/19605.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=19605</wfw:commentRss><description>Hi trufooser,
&lt;br /&gt;&lt;br /&gt;
I think it will be easier in this situation to run two seperate queries against the tables, and then link them yourself with XPath and conditional visibility.</description></item><item><title>Setting value of a query field</title><link>https://www.infopathdev.com:443/forums/thread/18030.aspx</link><pubDate>Wed, 13 Sep 2006 15:33:16 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:18030</guid><dc:creator>trufooser</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/18030.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&amp;PostID=18030</wfw:commentRss><description>I think the falls under the category of inconvenience.&lt;br /&gt;&lt;br /&gt;I have two tables with a structure as follows:&lt;br /&gt;&lt;br /&gt;+Table1&lt;br /&gt;     Table1ID&lt;br /&gt;     Table1Fields&lt;br /&gt;&lt;br /&gt;     +Table2&lt;br /&gt;          Table2ID&lt;br /&gt;          Table2Fields&lt;br /&gt;&lt;br /&gt;On the main page, Table2 is a repeating section residing within Table1 (which is also repeating).&lt;br /&gt;&lt;br /&gt;The user runs a query that will return all entries in Table1 and Table2.  &lt;br /&gt;&lt;br /&gt;I have a button located inside the Table2 repeating section that has one rule with several actions which are as follows:&lt;br /&gt;         SetValue of Query Field Table1ID to current Table1ID&lt;br /&gt;         SetValue of Query Field Table2ID to current Table2ID&lt;br /&gt;         Query Main Connection&lt;br /&gt;         SetValue of Query Field Table1ID to blank&lt;br /&gt;         SetValue of Query Field Table2ID to blank&lt;br /&gt;&lt;br /&gt;These rules were supposed to isolate a specific record in the form and prepare the query fields for another query.  While they do isolate a record, and set the Table2ID query field to blank, it does not set the Table1ID query field to blank.&lt;br /&gt;&lt;br /&gt;I have managed to work around this by using one line of code, however, it has greatly slowed down the performance of my form.&lt;br /&gt;&lt;br /&gt;I think this problem could be fixed by allowing the editing of the XPath in the "Field" field in the "Set a field's value" dialog box.&lt;br /&gt;&lt;br /&gt;</description></item></channel></rss>