Ocean West Posted February 26, 2010 Posted February 26, 2010 Here is an organizational concept for organizing the Relationship Graph. mwI5BYEZ1Yg
bruceR Posted February 26, 2010 Posted February 26, 2010 This also allows you to do things like easily save record sets. Purchase_Orders2.fp7.zip
genevieve charbon Posted February 26, 2010 Posted February 26, 2010 Seems to me it will be a performance killer ?
Fitch Posted February 27, 2010 Posted February 27, 2010 There is a certain amount of overhead in adding TOs to the graph. But I think used judiciously, this could be a useful approach. CPU cycles are cheaper than developer cycles, and sometimes making development more manageable is more important than shaving a millisecond here or there. Stephen said he hadn't noticed any performance problems. Where do you see it being a performance killer? (Not trying to start a fight, just looking for information.) Thanks for sharing, Stephen!
bruceR Posted February 27, 2010 Posted February 27, 2010 (edited) Seems to me it will be a performance killer ? Barely measurable if you look hard. Did a looping find test, 500 iterations, across several different levels of this technique. 11 seconds contacts->phones 13 seconds contacts->contact_link1->phones2 16 seconds contacts->contact_link1->contact_link2->contact_link3->phones3 Edited February 27, 2010 by Guest
bobearl Posted February 28, 2010 Posted February 28, 2010 Very handy, good idea. A very small suggestion: one thing that might save you just a bit of time (and maybe fidelity) with this is instead of recreating all of the relationships, option drag all of the tables that you'd like to create the sub-group from. That will keep all the relationships intact and save you from having to reconnect those TO's. Thanks very much for sharing the tip! Cheers, Bob
Søren Dyhr Posted March 1, 2010 Posted March 1, 2010 Seems to me it will be a performance killer ? Eventhoug I not agree with Genevieve's multimapping imports to pull off stuff ... might there be some issue in this: http://www.joelonsoftware.com/items/2009/09/23.html That fits here as well - fully aware of tips usually should be used with hessitation and critique, while I can't say where the weak spot is here yet. It's just the notion that something must be ... not quite as it ought to be! Things happens unexpected when we try to do clever stuff, because we get blind angles when depositing our energy in being clever. David Kachels warning about the cute and clever should be memorized by all filemaker developers. Bobbearl's option dragging is clearly (to me at least) an evidence of such a blind angle... unless the urge deliberately from Steven has been to pin things out in simple maneuvers? --sd
bruceR Posted March 1, 2010 Posted March 1, 2010 Sorry, that is all way too vague to have any relevance IMHO.
bruceR Posted March 1, 2010 Posted March 1, 2010 File demonstrating the technique, also showing saving and restoring record sets. CFReporting.fp7.zip
LaRetta Posted March 2, 2010 Posted March 2, 2010 (edited) Things happens unexpected when we try to do clever stuff, because we get blind angles when depositing our energy in being clever. Exactly, Søren ... things happen when we try to do clever stuff and many of the unexpected results are the discovery of great ideas or even ideas not-at-all relating to what we were attempting in the first place. Bruce, thanks for the great example files!! I believe Søren's post was relevant and worthwhile, Bruce, and I appreciate his reminder of caution and balance. Stephen, thank you for presenting this concept. It opens my horizons. UPDATE: Stephen, your chart disappeared. Edited March 2, 2010 by Guest
Ocean West Posted March 2, 2010 Author Posted March 2, 2010 @laretta looks like You-Tube was down. http://mashable.com/2010/03/02/youtube-down-march-2/
Cortical Posted March 4, 2010 Posted March 4, 2010 which would drop all script refs, calcs, layout fields defined against the TOC would it not? unless none of that is built yet.
Recommended Posts