Comments for eX Cetera http://www.excelisys.com/blog Excelisys' exclusive industry spotlight Wed, 25 Apr 2012 06:29:03 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Conditional Love by Michael Rocharde http://www.excelisys.com/blog/2012/04/20/conditional-love/comment-page-1/#comment-32045 Michael Rocharde Wed, 25 Apr 2012 06:29:03 +0000 http://www.excelisys.com/blog/?p=475#comment-32045 There have been a number of reports that CF is causing part of the slowness reported in 12. As yet, I haven't had a chance to test this out for myself but, like everything else, CF should be used in moderation otherwise performance will suffer, especially across a networked solution. There have been a number of reports that CF is causing part of the slowness reported in 12. As yet, I haven’t had a chance to test this out for myself but, like everything else, CF should be used in moderation otherwise performance will suffer, especially across a networked solution.

]]> Comment on Portal Sort Extreme 2 by Christo http://www.excelisys.com/blog/2012/04/02/ortal-sort-extreme-2/comment-page-1/#comment-30580 Christo Thu, 05 Apr 2012 16:18:23 +0000 http://www.excelisys.com/blog/?p=465#comment-30580 Attached is an updated file. I didn't find any issue with the calculations or custom functions. The method is sound. It was just an installation issue. If I had followed my own instructions, I would have unchecked the "do not evaluate" checkbox on the number sort field. That resolved the issue. I also cleaned up some layout elements that were not anchored correctly. Attached is an updated file.

I didn’t find any issue with the calculations or custom functions. The method is sound. It was just an installation issue. If I had followed my own instructions, I would have unchecked the “do not evaluate” checkbox on the number sort field. That resolved the issue.

I also cleaned up some layout elements that were not anchored correctly.

]]> Comment on About that portal, Captain! by Bruce Robertson http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30473 Bruce Robertson Tue, 03 Apr 2012 22:40:29 +0000 http://www.excelisys.com/blog/?p=451#comment-30473 Another vote agreeing with the sense of confusion in this article. An example file might help. At least this isn't one of those sites where you pay to hear somebody drone on for 20 minutes to explain a two minute concept. The FileMaker community needs an editor. Another vote agreeing with the sense of confusion in this article. An example file might help. At least this isn’t one of those sites where you pay to hear somebody drone on for 20 minutes to explain a two minute concept. The FileMaker community needs an editor.

]]> Comment on About that portal, Captain! by Michael Rocharde http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30410 Michael Rocharde Mon, 02 Apr 2012 15:01:04 +0000 http://www.excelisys.com/blog/?p=451#comment-30410 Having re-read the article, Honza, the benefit is explained in the intro paragraph in that it eliminates the ghost row. Having re-read the article, Honza, the benefit is explained in the intro paragraph in that it eliminates the ghost row.

]]> Comment on About that portal, Captain! by Michael Rocharde http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30409 Michael Rocharde Mon, 02 Apr 2012 14:56:06 +0000 http://www.excelisys.com/blog/?p=451#comment-30409 The other problem with this is that you can very quickly have more records than the portal is set up to display so the user can't see the next available row and then has to scroll down to find it. To me, it is much more likely that users will want to see the most recently created records which is why I like having them at the top of the portal. The other problem with this is that you can very quickly have more records than the portal is set up to display so the user can’t see the next available row and then has to scroll down to find it. To me, it is much more likely that users will want to see the most recently created records which is why I like having them at the top of the portal.

]]> Comment on About that portal, Captain! by Michael Rocharde http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30408 Michael Rocharde Mon, 02 Apr 2012 14:52:11 +0000 http://www.excelisys.com/blog/?p=451#comment-30408 Sorry for the confusion; I obviously thought I was being very clear about the reason for using this methodology. Tom, I'm not sure why burning serial #s is of any significance but yes, it is 'magic', as you say Sorry for the confusion; I obviously thought I was being very clear about the reason for using this methodology. Tom, I’m not sure why burning serial #s is of any significance but yes, it is ‘magic’, as you say

]]> Comment on About that portal, Captain! by Tom Fitch http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30246 Tom Fitch Fri, 30 Mar 2012 23:42:25 +0000 http://www.excelisys.com/blog/?p=451#comment-30246 HOnza, I agree it is a confusing article. FYI the empty-global (aka "Magic Key") relationship can in fact create multiple related records, by clearing the global before setting the next key. You don't have to commit each one. And if you revert the parent record, none of the child records will be committed. Magic! (But you will burn serial numbers.) HOnza, I agree it is a confusing article. FYI the empty-global (aka “Magic Key”) relationship can in fact create multiple related records, by clearing the global before setting the next key. You don’t have to commit each one. And if you revert the parent record, none of the child records will be committed. Magic! (But you will burn serial numbers.)

]]> Comment on About that portal, Captain! by Kris http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30235 Kris Fri, 30 Mar 2012 20:07:26 +0000 http://www.excelisys.com/blog/?p=451#comment-30235 if you dont use the commit records you can create a batch of related records. You can then commit them all at once or delete them. Benefit really shows up in multi user situation where you need to create relateds but not let other see you have created them until you commit. Saw a nice presentation at devcon last year that showed this and ive been using it ever since. might have been Todd Geist or Ray Cologon that presented.. yea its a weird but useful phenomenon if you dont use the commit records you can create a batch of related records. You can then commit them all at once or delete them. Benefit really shows up in multi user situation where you need to create relateds but not let other see you have created them until you commit. Saw a nice presentation at devcon last year that showed this and ive been using it ever since. might have been Todd Geist or Ray Cologon that presented.. yea its a weird but useful phenomenon

]]> Comment on About that portal, Captain! by Fabrice N http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30230 Fabrice N Fri, 30 Mar 2012 17:27:31 +0000 http://www.excelisys.com/blog/?p=451#comment-30230 Hi, it looks pretty much like this http://www.1-more-thing.com/Create-related-records-from-a.html Except that this one does not even require a script. Hi,

it looks pretty much like this http://www.1-more-thing.com/Create-related-records-from-a.html
Except that this one does not even require a script.

]]> Comment on About that portal, Captain! by RenĂ© Labadie http://www.excelisys.com/blog/2012/03/23/about-that-portal-captain/comment-page-1/#comment-30215 RenĂ© Labadie Fri, 30 Mar 2012 12:02:53 +0000 http://www.excelisys.com/blog/?p=451#comment-30215 I use the three ways, but when I have to use the relationship method that FileMaker provides, I make the delete button for every portal row to be a calculation, so that, if IsEmpty ( Portal row ID ) don't show the delete button, so the ghost row at the bottom of your portal, don't have a visual delete button, and of course the script that delete portal row just work if the portal row ID is not empty. This method that I've learn make the portal looks like a spreadsheet for the user. No confuse and no user pressing that delete button of the last ghost portal row. I use the three ways, but when I have to use the relationship method that FileMaker provides, I make the delete button for every portal row to be a calculation, so that, if IsEmpty ( Portal row ID ) don’t show the delete button, so the ghost row at the bottom of your portal, don’t have a visual delete button, and of course the script that delete portal row just work if the portal row ID is not empty. This method that I’ve learn make the portal looks like a spreadsheet for the user. No confuse and no user pressing that delete button of the last ghost portal row.

]]>