<?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: Power Users Beware &#8211; Part Two</title>
	<atom:link href="http://www.bentousers.com/20091006-power-users-beware-part-two/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bentousers.com/20091006-power-users-beware-part-two/</link>
	<description>WRITTEN BY BENTO™ USERS FOR BENTO USERS</description>
	<lastBuildDate>Fri, 03 Feb 2012 17:46:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Florian</title>
		<link>http://www.bentousers.com/20091006-power-users-beware-part-two/comment-page-1/#comment-795</link>
		<dc:creator>Florian</dc:creator>
		<pubDate>Wed, 07 Oct 2009 20:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.bentousers.com/?p=653#comment-795</guid>
		<description>Thanks Max (for short),
this is a wonderful tip! Extremely useful, and I understand exactly what you are saying. It&#039;s still very annoying, especially in my case. I only decided to duplicate the form when it already contained several objects and text boxes.
I didn&#039;t mean to convey that it was a Bento 3 bug specifically, but I definitely call it a BUG, because it really shouldn&#039;t be that way!! And it goes beautifully with Bento&#039;s duplication bug which is a problem everywhere. Please keep helping us out whenever you feel like it!</description>
		<content:encoded><![CDATA[<p>Thanks Max (for short),<br />
this is a wonderful tip! Extremely useful, and I understand exactly what you are saying. It&#8217;s still very annoying, especially in my case. I only decided to duplicate the form when it already contained several objects and text boxes.<br />
I didn&#8217;t mean to convey that it was a Bento 3 bug specifically, but I definitely call it a BUG, because it really shouldn&#8217;t be that way!! And it goes beautifully with Bento&#8217;s duplication bug which is a problem everywhere. Please keep helping us out whenever you feel like it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bento to the Max</title>
		<link>http://www.bentousers.com/20091006-power-users-beware-part-two/comment-page-1/#comment-793</link>
		<dc:creator>Bento to the Max</dc:creator>
		<pubDate>Wed, 07 Oct 2009 20:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.bentousers.com/?p=653#comment-793</guid>
		<description>&quot;Recently I duplicated a form, because I wanted to make slight changes for displaying the final record of a collection. The duplicated form is supposed to be a separate entity. But in this case Bento 3 maintained some kind of a link between the forms. I made my changes to the duplicate and when I went back to the other form, it was messed up. SOME of the changes to the duplicate had also effected the original!&quot;

This is NOT a new Bento 3 bug.  This bug has been around since version 1 and I reported it to FileMaker way back then on the Bento forum.

It is perhaps not a bug, just an anomaly.  What you cannot do, when you want to duplicate a form, is to duplicate a form with OBJECTS or TEXT BOXES.  Because if you duplicate such a form, the objects and text boxes on the forms are not true copies, they are SHARED.  You can never change any of those objects or text boxes, because if you do, it will change the ones in the other form.

This does not happen with fields.  You can move and delete fields freely and it doesn&#039;t affect the other form.  But if there is a common OBJECT or TEXT BOX, change one and the other will be changed, delete one and the other will be deleted.

It might confuse you at first if you had already changed around a lot of the fields on one form, that when you finally delete a &quot;shared&quot; object, it will ripple the formatting of the fields of that other form to where it might not be easy to see what the heck happened.  But it is simply this:  
-- NEVER DUPLICATE A FORM THAT ALREADY HAS ANY OBJECTS OR TEXT BOXES IN THEM
however, it is okay to:
-- DUPLICATE FORMS PRIOR TO PLACING ANY OBJECTS OR TEXT BOXES IN THEM and you won&#039;t risk affecting either form later.</description>
		<content:encoded><![CDATA[<p>&#8220;Recently I duplicated a form, because I wanted to make slight changes for displaying the final record of a collection. The duplicated form is supposed to be a separate entity. But in this case Bento 3 maintained some kind of a link between the forms. I made my changes to the duplicate and when I went back to the other form, it was messed up. SOME of the changes to the duplicate had also effected the original!&#8221;</p>
<p>This is NOT a new Bento 3 bug.  This bug has been around since version 1 and I reported it to FileMaker way back then on the Bento forum.</p>
<p>It is perhaps not a bug, just an anomaly.  What you cannot do, when you want to duplicate a form, is to duplicate a form with OBJECTS or TEXT BOXES.  Because if you duplicate such a form, the objects and text boxes on the forms are not true copies, they are SHARED.  You can never change any of those objects or text boxes, because if you do, it will change the ones in the other form.</p>
<p>This does not happen with fields.  You can move and delete fields freely and it doesn&#8217;t affect the other form.  But if there is a common OBJECT or TEXT BOX, change one and the other will be changed, delete one and the other will be deleted.</p>
<p>It might confuse you at first if you had already changed around a lot of the fields on one form, that when you finally delete a &#8220;shared&#8221; object, it will ripple the formatting of the fields of that other form to where it might not be easy to see what the heck happened.  But it is simply this:<br />
&#8211; NEVER DUPLICATE A FORM THAT ALREADY HAS ANY OBJECTS OR TEXT BOXES IN THEM<br />
however, it is okay to:<br />
&#8211; DUPLICATE FORMS PRIOR TO PLACING ANY OBJECTS OR TEXT BOXES IN THEM and you won&#8217;t risk affecting either form later.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

