<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Dynamic Forms</title>
	<atom:link href="http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/</link>
	<description>An online database resource and viewpoint from QuickBase on how online workgroup applications are improving the way we work. We cover advice and tips to help you get the most from QuickBase, relevant broader market trends, and what we are doing at QuickBase.</description>
	<lastBuildDate>Wed, 08 Feb 2012 03:33:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Matt</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-5616</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 14 Dec 2008 16:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-5616</guid>
		<description>Stumble upon this blog posting while looking for info about QuickBase&#039;s lack of support for formula and lookup fields in rules, etc. The posting was back in 2006. It&#039;s almost 2009. Any progress on this front? It is vitally important that I have this ability in my db -- not an absolute killer, but the hacks around the issue are painful to maintain.</description>
		<content:encoded><![CDATA[<p>Stumble upon this blog posting while looking for info about QuickBase&#8217;s lack of support for formula and lookup fields in rules, etc. The posting was back in 2006. It&#8217;s almost 2009. Any progress on this front? It is vitally important that I have this ability in my db &#8212; not an absolute killer, but the hacks around the issue are painful to maintain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-18633</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 14 Dec 2008 16:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-18633</guid>
		<description>Stumble upon this blog posting while looking for info about QuickBase&#039;s lack of support for formula and lookup fields in rules, etc. The posting was back in 2006. It&#039;s almost 2009. Any progress on this front? It is vitally important that I have this ability in my db -- not an absolute killer, but the hacks around the issue are painful to maintain.</description>
		<content:encoded><![CDATA[<p>Stumble upon this blog posting while looking for info about QuickBase&#8217;s lack of support for formula and lookup fields in rules, etc. The posting was back in 2006. It&#8217;s almost 2009. Any progress on this front? It is vitally important that I have this ability in my db &#8212; not an absolute killer, but the hacks around the issue are painful to maintain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Bernstein</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-228</link>
		<dc:creator>James Bernstein</dc:creator>
		<pubDate>Tue, 12 Dec 2006 14:08:10 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-228</guid>
		<description>How do I collect data from emails from prospects and put into my lead management database. Thus far all I can do is cut and paste. Very tiresome.
</description>
		<content:encoded><![CDATA[<p>How do I collect data from emails from prospects and put into my lead management database. Thus far all I can do is cut and paste. Very tiresome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Bernstein</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-18632</link>
		<dc:creator>James Bernstein</dc:creator>
		<pubDate>Tue, 12 Dec 2006 14:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-18632</guid>
		<description>How do I collect data from emails from prospects and put into my lead management database. Thus far all I can do is cut and paste. Very tiresome.</description>
		<content:encoded><![CDATA[<p>How do I collect data from emails from prospects and put into my lead management database. Thus far all I can do is cut and paste. Very tiresome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sal Estrada</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-227</link>
		<dc:creator>Sal Estrada</dc:creator>
		<pubDate>Fri, 26 May 2006 21:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-227</guid>
		<description>I would like a way to generate row numbers in views so I can reference the row number when reviewing printed views with my clients.
</description>
		<content:encoded><![CDATA[<p>I would like a way to generate row numbers in views so I can reference the row number when reviewing printed views with my clients.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sal Estrada</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-18631</link>
		<dc:creator>Sal Estrada</dc:creator>
		<pubDate>Fri, 26 May 2006 21:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-18631</guid>
		<description>I would like a way to generate row numbers in views so I can reference the row number when reviewing printed views with my clients.</description>
		<content:encoded><![CDATA[<p>I would like a way to generate row numbers in views so I can reference the row number when reviewing printed views with my clients.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-226</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 08 May 2006 15:16:28 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-226</guid>
		<description>Sounds great.
One thought:
In this section you wrote...
---------------------------
In the When section you specify When the rule applies.  Currently we anticipate the choices here being:

when a field is a particular value
when a field is not a particular value
when a field changes
when a field changes to a particular value
when a field changes from a particular value
when the form loads
when the form is saved
In the Additional Conditions section, you&#039;ll be able to specify one or more conditions that must also be true in order for the rule to apply.  The choices here will probably be:

when a field is a particular value
is not a particular value
is greater than a particular value
is less than a particular value
---------------------------
I trust this will also support field conditions of blank and non-blank as triggers, in addtion to the ones you have listed. e.g. If a field is blank, send the user a message. Then I can use the message to explain not only that the blank field needs a value, but why, etc. This will be a big help over and above the current simple &quot;required&quot; condition.
</description>
		<content:encoded><![CDATA[<p>Sounds great.<br />
One thought:<br />
In this section you wrote&#8230;<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
In the When section you specify When the rule applies.  Currently we anticipate the choices here being:</p>
<p>when a field is a particular value<br />
when a field is not a particular value<br />
when a field changes<br />
when a field changes to a particular value<br />
when a field changes from a particular value<br />
when the form loads<br />
when the form is saved<br />
In the Additional Conditions section, you&#8217;ll be able to specify one or more conditions that must also be true in order for the rule to apply.  The choices here will probably be:</p>
<p>when a field is a particular value<br />
is not a particular value<br />
is greater than a particular value<br />
is less than a particular value<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
I trust this will also support field conditions of blank and non-blank as triggers, in addtion to the ones you have listed. e.g. If a field is blank, send the user a message. Then I can use the message to explain not only that the blank field needs a value, but why, etc. This will be a big help over and above the current simple &#8220;required&#8221; condition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-18630</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 08 May 2006 15:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-18630</guid>
		<description>Sounds great.
One thought:
In this section you wrote...
---------------------------
In the When section you specify When the rule applies.  Currently we anticipate the choices here being:

when a field is a particular value
when a field is not a particular value
when a field changes
when a field changes to a particular value
when a field changes from a particular value
when the form loads
when the form is saved
In the Additional Conditions section, you&#039;ll be able to specify one or more conditions that must also be true in order for the rule to apply.  The choices here will probably be:

when a field is a particular value
is not a particular value
is greater than a particular value
is less than a particular value
---------------------------
I trust this will also support field conditions of blank and non-blank as triggers, in addtion to the ones you have listed. e.g. If a field is blank, send the user a message. Then I can use the message to explain not only that the blank field needs a value, but why, etc. This will be a big help over and above the current simple &quot;required&quot; condition.</description>
		<content:encoded><![CDATA[<p>Sounds great.<br />
One thought:<br />
In this section you wrote&#8230;<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
In the When section you specify When the rule applies.  Currently we anticipate the choices here being:</p>
<p>when a field is a particular value<br />
when a field is not a particular value<br />
when a field changes<br />
when a field changes to a particular value<br />
when a field changes from a particular value<br />
when the form loads<br />
when the form is saved<br />
In the Additional Conditions section, you&#8217;ll be able to specify one or more conditions that must also be true in order for the rule to apply.  The choices here will probably be:</p>
<p>when a field is a particular value<br />
is not a particular value<br />
is greater than a particular value<br />
is less than a particular value<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
I trust this will also support field conditions of blank and non-blank as triggers, in addtion to the ones you have listed. e.g. If a field is blank, send the user a message. Then I can use the message to explain not only that the blank field needs a value, but why, etc. This will be a big help over and above the current simple &#8220;required&#8221; condition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Taylor Jr.</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-225</link>
		<dc:creator>David Taylor Jr.</dc:creator>
		<pubDate>Wed, 03 May 2006 17:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-225</guid>
		<description>Thank you Quickbase for making these enhancements.  I know that I had discussed this with you guys for our particular account.  I am also glad that you tested the formulas on our account and they work.  I look forward to the release in June.
</description>
		<content:encoded><![CDATA[<p>Thank you Quickbase for making these enhancements.  I know that I had discussed this with you guys for our particular account.  I am also glad that you tested the formulas on our account and they work.  I look forward to the release in June.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Taylor Jr.</title>
		<link>http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/comment-page-1/#comment-18629</link>
		<dc:creator>David Taylor Jr.</dc:creator>
		<pubDate>Wed, 03 May 2006 17:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://quickbase.intuit.com/blog/2006/03/17/dynamic-forms/#comment-18629</guid>
		<description>Thank you Quickbase for making these enhancements.  I know that I had discussed this with you guys for our particular account.  I am also glad that you tested the formulas on our account and they work.  I look forward to the release in June.</description>
		<content:encoded><![CDATA[<p>Thank you Quickbase for making these enhancements.  I know that I had discussed this with you guys for our particular account.  I am also glad that you tested the formulas on our account and they work.  I look forward to the release in June.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

