<?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 for The Philadelphia FileMaker User Group - serving the Pennsylvania, New Jersey and Delaware Region</title>
	<atom:link href="http://www.phillyfilemaker.org/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.phillyfilemaker.org</link>
	<description>We’re a FileMaker User Group serving the Pennsylvania, New Jersey and Delaware Region</description>
	<lastBuildDate>Thu, 09 May 2013 13:26:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>Comment on Filemaker Tips and Tricks: To Maximize or Not to Maximize by Colin Keefe</title>
		<link>http://www.phillyfilemaker.org/index.php/2009/09/filemaker-tips-and-tricks-to-maximize-or-not-to-maximize/comment-page-1/#comment-21849</link>
		<dc:creator>Colin Keefe</dc:creator>
		<pubDate>Thu, 09 May 2013 13:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=712#comment-21849</guid>
		<description>Hi John,

Yeah, it’s a pity that it isn’t manipulable.  Hope this article helped!

Best
Colin</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>Yeah, it’s a pity that it isn’t manipulable.  Hope this article helped!</p>
<p>Best<br />
Colin</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Filemaker Tips and Tricks: To Maximize or Not to Maximize by John G. White</title>
		<link>http://www.phillyfilemaker.org/index.php/2009/09/filemaker-tips-and-tricks-to-maximize-or-not-to-maximize/comment-page-1/#comment-21833</link>
		<dc:creator>John G. White</dc:creator>
		<pubDate>Wed, 08 May 2013 21:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=712#comment-21833</guid>
		<description>Interesting helpful article. I came across it while searching for a way to control the MDI window via script step — doesn&#039;t look like it&#039;s possible, which is too bad, because it means you don&#039;t really have control over the size of your document window content area.</description>
		<content:encoded><![CDATA[<p>Interesting helpful article. I came across it while searching for a way to control the MDI window via script step — doesn&#8217;t look like it&#8217;s possible, which is too bad, because it means you don&#8217;t really have control over the size of your document window content area.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s so great about the Modification Date? by Colin Keefe</title>
		<link>http://www.phillyfilemaker.org/index.php/2010/01/whats-so-great-about-the-modification-date/comment-page-1/#comment-18539</link>
		<dc:creator>Colin Keefe</dc:creator>
		<pubDate>Wed, 13 Mar 2013 14:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=753#comment-18539</guid>
		<description>No worries, I usually have to wait until after my coffee’s brewed before I make any sense!</description>
		<content:encoded><![CDATA[<p>No worries, I usually have to wait until after my coffee’s brewed before I make any sense!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s so great about the Modification Date? by Brian Randolph</title>
		<link>http://www.phillyfilemaker.org/index.php/2010/01/whats-so-great-about-the-modification-date/comment-page-1/#comment-18488</link>
		<dc:creator>Brian Randolph</dc:creator>
		<pubDate>Tue, 12 Mar 2013 16:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=753#comment-18488</guid>
		<description>Sorry. Please ignore my previous post. I should learn to wait until morning before asking questions...</description>
		<content:encoded><![CDATA[<p>Sorry. Please ignore my previous post. I should learn to wait until morning before asking questions&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s so great about the Modification Date? by Brian Randolph</title>
		<link>http://www.phillyfilemaker.org/index.php/2010/01/whats-so-great-about-the-modification-date/comment-page-1/#comment-18460</link>
		<dc:creator>Brian Randolph</dc:creator>
		<pubDate>Tue, 12 Mar 2013 05:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=753#comment-18460</guid>
		<description>Hi Jerry and Colin,

Thank you for this post. This seems like the perfect solution to an issue I&#039;m trying to resolve. The only remaining issue is that if the field is cleared, the timestamp disappears.

My issue is precisely what you&#039;ve described above. I have a script that runs nightly (an ultralog archive script in fact) and the mod stamp is always the same. I also have a MySQL database that a web portal uses for its data source. I need a way to push data from FM to MySQL on an hourly basis without having to go through every single record.

Any ideas on how to track a field being cleared as well with this solution?</description>
		<content:encoded><![CDATA[<p>Hi Jerry and Colin,</p>
<p>Thank you for this post. This seems like the perfect solution to an issue I&#8217;m trying to resolve. The only remaining issue is that if the field is cleared, the timestamp disappears.</p>
<p>My issue is precisely what you&#8217;ve described above. I have a script that runs nightly (an ultralog archive script in fact) and the mod stamp is always the same. I also have a MySQL database that a web portal uses for its data source. I need a way to push data from FM to MySQL on an hourly basis without having to go through every single record.</p>
<p>Any ideas on how to track a field being cleared as well with this solution?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Window Dressing by Doug Alder</title>
		<link>http://www.phillyfilemaker.org/index.php/2012/09/window-dressing/comment-page-1/#comment-15894</link>
		<dc:creator>Doug Alder</dc:creator>
		<pubDate>Mon, 15 Oct 2012 04:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=2651#comment-15894</guid>
		<description>Here is a variant of this technique, combining the rename window function with an OnObjectModify script trigger: 

http://hbase.net/2012/01/06/window-names/</description>
		<content:encoded><![CDATA[<p>Here is a variant of this technique, combining the rename window function with an OnObjectModify script trigger: </p>
<p><a href="http://hbase.net/2012/01/06/window-names/" rel="nofollow">http://hbase.net/2012/01/06/window-names/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tips and Tricks: Self Tooltipping Fields in Filemaker 10 by How to use Field Comments as Tooltips. &#124; HomeBase Software</title>
		<link>http://www.phillyfilemaker.org/index.php/2009/01/self-tooltipping-fields-in-filemaker-10/comment-page-1/#comment-15666</link>
		<dc:creator>How to use Field Comments as Tooltips. &#124; HomeBase Software</dc:creator>
		<pubDate>Fri, 31 Aug 2012 20:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://phillyfilemaker.wordpress.com/?p=163#comment-15666</guid>
		<description>[...] August 31, 2012 by Douglas Alder 0 Comments   Good tips for tooltips. I had seen this before but couldn’t remember how to do it. Thank you Google. Thank you Philly FileMaker. [...]</description>
		<content:encoded><![CDATA[<p>[...] August 31, 2012 by Douglas Alder 0 Comments   Good tips for tooltips. I had seen this before but couldn’t remember how to do it. Thank you Google. Thank you Philly FileMaker. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Building robust error logs in FileMaker 11 by Pablo Ruiz</title>
		<link>http://www.phillyfilemaker.org/index.php/2010/09/building-robust-error-logs-in-filemaker-11/comment-page-1/#comment-15534</link>
		<dc:creator>Pablo Ruiz</dc:creator>
		<pubDate>Sat, 11 Aug 2012 01:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=1455#comment-15534</guid>
		<description>Thank you. This is a lot of information. I&#039;m studying it and implementing this in an already working solution. There&#039;s a lot of work to be done but this will help me troubleshoot error when they happen. It&#039;s an invaluable tool and I&#039;m pretty sure I&#039;ll use this as one of many &quot;Starting points&quot; when I make any new database or project on FM.

Thanks again.</description>
		<content:encoded><![CDATA[<p>Thank you. This is a lot of information. I&#8217;m studying it and implementing this in an already working solution. There&#8217;s a lot of work to be done but this will help me troubleshoot error when they happen. It&#8217;s an invaluable tool and I&#8217;m pretty sure I&#8217;ll use this as one of many &#8220;Starting points&#8221; when I make any new database or project on FM.</p>
<p>Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s so great about the Modification Date? by Jerry Salem</title>
		<link>http://www.phillyfilemaker.org/index.php/2010/01/whats-so-great-about-the-modification-date/comment-page-1/#comment-15025</link>
		<dc:creator>Jerry Salem</dc:creator>
		<pubDate>Fri, 29 Jun 2012 19:46:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=753#comment-15025</guid>
		<description>Dan

The reason you need the &#039;if(field1&amp;field2...&#039; structure is below;

The best way to think of it is the references force the calculation to refresh.
If you enter or change the value of field1, then the calculation will fire.
If you change a value of a field not related then this calculation won&#039;t fire.

For a better way to track changes of one particular field, see my post on UltraLog (http://www.phillyfilemaker.org/index.php/2011/07/tracking-changes-in-your-database/) from a couple months ago.

Jerry</description>
		<content:encoded><![CDATA[<p>Dan</p>
<p>The reason you need the &#8216;if(field1&amp;field2&#8230;&#8217; structure is below;</p>
<p>The best way to think of it is the references force the calculation to refresh.<br />
If you enter or change the value of field1, then the calculation will fire.<br />
If you change a value of a field not related then this calculation won&#8217;t fire.</p>
<p>For a better way to track changes of one particular field, see my post on UltraLog (<a href="http://www.phillyfilemaker.org/index.php/2011/07/tracking-changes-in-your-database/" rel="nofollow">http://www.phillyfilemaker.org/index.php/2011/07/tracking-changes-in-your-database/</a>) from a couple months ago.</p>
<p>Jerry</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s so great about the Modification Date? by Dan</title>
		<link>http://www.phillyfilemaker.org/index.php/2010/01/whats-so-great-about-the-modification-date/comment-page-1/#comment-14992</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 28 Jun 2012 19:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.phillyfilemaker.org/?p=753#comment-14992</guid>
		<description>Cool tip, what&#039;s the logic behind the if(field1&amp;field2&amp;field3.... working?  Is it just verifying each time the record is committed that the fields are not null or something?</description>
		<content:encoded><![CDATA[<p>Cool tip, what&#8217;s the logic behind the if(field1&amp;field2&amp;field3&#8230;. working?  Is it just verifying each time the record is committed that the fields are not null or something?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
