gbrozak Posted February 7, 2006 Posted February 7, 2006 Is there a way to create a numbering system when a layout is sorted by sub-summary? I would like to have 1-whatever appear in my layout, but need the # to restart with each newly-found item (by which the layout is sorted). For example, I want to number INSTRUMENTS (this is the sorted layout). I want to see 1-25 (or how many) flutes, 1-15 clarinets, 1-56 saxes, etc. Thanks! George
LaRetta Posted February 7, 2006 Posted February 7, 2006 (edited) Hi George, I'm trying to envision what you have. I think you just want the items in the body of your report to be numbered ... and adjust the numbering when sorted or a new find is performed? I think if you go to your report body and (using the text tool) type @@ it will give you what you need (which is the internal FM Record Number). If not, post back and we'll help you further. Hmmm, upon re-read, you want the numbering to start over. Is this a report with sub-summaries? It might be possible (using trickery, scripting and possibly a calc) but ... if all you want is to know the total count of each item, you could instead put a Count in a trailing summary part? LaRetta Edited February 7, 2006 by Guest
gbrozak Posted February 7, 2006 Author Posted February 7, 2006 LaRetta, Thanks SO MUCH for your reply. Yes, this is a report with sub-summaries. I had used the "@@" feature to auto-number the layout, but wasn't able to get it to re-start at 1 with each new found sort. This is what I want it to be able to do, if possible. Any thoughts? George
LaRetta Posted February 7, 2006 Posted February 7, 2006 I've never tried that, George and unfortunately don't have the time right now. Sub-summaries at a complex twist. But I feel confident that if it's possible someone will help you through it. Hang in there! :wink2:
Søren Dyhr Posted February 7, 2006 Posted February 7, 2006 You didn't put any restrictions on if it's to be used on found sets only or you just need to serialize by category... if it's the last could it be done like this old template. Try to migrate the .fp3 template here - and be aware that a lot can be made different given the present toolbox - including the taking care of found sets. http://www.filemakerpros.com/SerialCat.sit http://www.filemakerpros.com/Serialize_by_Category.zip --sd
gbrozak Posted February 7, 2006 Author Posted February 7, 2006 Søren, I'm wanting the numbering to take place on each found set. In other words, I want the flutes to be numbered on their sub-summary report (say, 1-15), clarinets (1-26), saxes (1-45), etc. I have used the @@ to get a count, but right now, it's giving me the ENTIRE count (461) instead of as I outlined above. Any ideas? George
Søren Dyhr Posted February 8, 2006 Posted February 8, 2006 Yes but real fields are required - The way I make it, is with a combination of these two methods: http://www.sumware.net/robfm/savingfoundsets.php http://www.onegasoft.com/tools/fastsummaries/index.shtml What I've done is I've made an interface where you sell items by pressing a button next to the line, and the rest will renumber accordingly. To bring it to your summary report, have i left for you to figure out. I have admittingly been a little sloppy with the replaces, which can bother if the found set is whopping. If it's a problem do I gladly provide you a tighter algorithm ...this template is merely showing a concept than being particular fast. Enjoy --sd Warehouse.zip
Søren Dyhr Posted February 8, 2006 Posted February 8, 2006 Now it depends on your situation, but some optimization to the looping could be inplemented if we take the scripted replaces even more casual ...it's obivous that a large set of records screws this up ...but it occured to me how cluncky it would be to filter out the exact subsummary before number tagging. My guess that it would considerable faster within reasonable sets to avoid a fair share of the GTRR(SO) without relational ties. I can't really tell where it tilts and you feel the lack of resposiveness ...into requirering the tightest algorithm that takes care not number tagging some of the fields several times. --sd Warehouse2.zip
comment Posted February 8, 2006 Posted February 8, 2006 How about something simple, for a change? Note: if a secondary sort is required, add a temp serial field and replace its contents with serial numbers (after the sort). Then use this field instead of SerialID in defining the relationship. BTW, there's a demo somewhere here (by Queue, I think) that does this by summary and calc fields only - but it takes no less than six fields to acomplish this. SerialByGroupRel.fp7.zip
Søren Dyhr Posted February 8, 2006 Posted February 8, 2006 Ehm! ...What I thought of at first, but found sets are the name of the game here! --sd
comment Posted February 8, 2006 Posted February 8, 2006 Right you are, how silly of me. OK, then I have no choice but to limit this to version 8. SerialByGroupN8.fp7.zip
Søren Dyhr Posted February 9, 2006 Posted February 9, 2006 The technique as such is elegant, but I've learned sometime in my past that unstored fields referencing other unstored fields is not particular healthy when serving a solution via web or wan/lan. Give yourself the oppertunity to watch the CPU graph when you do simple things (not networked) like clicking somewhere on the windows scrollbar or omit an abitrary record. The word that comes to mind is "spike"! --sd
comment Posted February 9, 2006 Posted February 9, 2006 True, but it is only for a printout. I say let it sweat - the simplicity is well worth it.
Recommended Posts
This topic is 6864 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now