mickeyfinn

It works fine in FM9 - but I didn't really doubt that. I'll see if there are any IWP patches for FM7SA and get back to you.

Well, I can move the fields to the same layout, but it's not the best fix. As for the scripting, I have made it so it goes to that specific layout. The problem arises when you move to ANY layout but the current one via a script step. You can move layouts via the FM inspector (the left side panel), but I would like to close this off to web users as it allows them more options than I would like. Is this a known limitation on version 7?

I searched and found the following thread reporting a bug I am seeing in FM Server 7 Advanced IWP. http://fmforums.com/forum/showpost.php?post/115665/ It's from a while ago, and the thread did not get a resolution to the problem. The behavior is this: User in IWP enters find mode (either via the sidebar Find button or by a user defined Find script button). Find mode is entered without issue but the user wants to enter criteria in another layout and uses a button in the layout programmed only with a Go To Layout step. The new layout loads but the fields do not show as active in this layout like in the original when in Find Mode. Clicking in a field on this layout generates the following error (in IE/Safari/Firefox) Bad Request The Server could not process your request due to a missing command: "". Using the sidebar layout change controls, this can be avoided. Is this a known issue/limitation? Is there a script I can put on the layout change controls that can workaround this problem? What is the "missing command" being referred to in the error dialog? Thanks in advance for any help with this issue.

Sorry it took a while to get back to you, I have been doing some testing. In your solution, does this mean I have to populate the global by triggering a script, or is there a way to make a lookup or something else auto-enter the data?

I have 2 main tables, Pages and Services, with a Line Items link table that allows me to assign multiple Services to any number of pages. I have a Qty (number) field in Line Items. I also have a Tasks table, whose records are created from a portal in Services, which also have a Qty field. I want to show a portal from Pages that shows all related Tasks (which I have done) but also contain a calculation of Line Items::Qty * Tasks::Qty. The logic is that each page is assigned numerous services which are each made up of a number of tasks. A page can contain one or more of each service. The user wants to be able to add services to a page, specifying the quantity needed for each. Each service can be applied to any page, and the user wants to see a portal showing the related tasks with the correct quantities for each. If I do a calculation based on the existing relationship, I can get the first instance of the Service in the database to multiply with the correct related task, but as soon as I add that Service to a new page, the calculation does not use the new Line Item quantity, it uses the original one. I was hoping to find a way to create a relationship where the current page being viewed is used as a match field in the Tasks table to Line Items (which contains the PageID foreign key). The problem is that I would like to do this without creating another link table between Line Items and Tasks. I know a link table is the "correct" way to do this, but I only need this one calculation to work - if I can do this, the user interface will be much simpler, rather than having to script the creation of records in the link table.

Sorry I haven't replied quicker. I've been busy at work. I will post a reply once I get chance to check your file tomorrow.

Comment, I realized from what you were saying that my original concern that I was over-complicating things was correct. As you say, the relationship must already exist, if the List function works. As it happens, I had built a TOG with Pages linked to services, and then had a separate Table Occurrence of Tasks which I was trying to link directly to Pages rather than via the Services TO. I should have seen that sooner, but I guess I was getting a little tunnel vision. So I have made the relationship work, without using the calc as the match field. Still, it should have worked, even if I did build it inefficiently. I do have the latest patches installed to the FM7 server, and I did have the ValueListItems calc field set up as you describe.

The Cascade example is great. Thanks very much for doing that. I noticed that you use join tables instead of relating each table directly, something I have not done before (unless you count a Line Items table). What are the advantages of this? As far as the original issue, I am no further to finding a workaround, though I did some more testing. Seems that if I base the relationship between Pages and Tasks on any calculation involving one result (e.g. just the basic Services~Pages::Related Service which shows the first result of this relationship only - no list)the relationship is successful. Likewise, the relationship works if I simply base on a text field and manually type the list of related service keys. However, as soon as I try to base the relationship on any calculation which results a value list, it fails. I was curious about what you were saying about the List calculation: Is there another way to build this? To answer your question as to why I keep mentioning FM Server 7, it's really that it was so frustrating to build a working solution in my FM9 client, only to have it fail as soon as I share via the server. That would be a life lesson I suppose! Always test on the platform you mean to deploy on.

Thanks for the fast responses, guys. I realize I'm not describing things so well, though bcooney, you are correct in your assessment of how I have this set up, other than the global field storing the active portal record key. I have never found a way to do this, so if you can tell me what the calculation of the global field needs to be that would help my interface immensely. I have tried to do this in the past and was unsuccessful. Presently, the user switches between pages using a value list of related page IDs. The only other difference to how you describe things is that I want the Tasks portal to show all related tasks for that page, so the list does not change when the user highlights different services in the Services portal. This is why I used the List function, because each task can be related to more than one page, depending on the services that have been selected for it. Comment, I tried the ValueListItems function and though it correctly stores the ServiceIDs in a list, as soon as I try a relationship from that list, it will not work on FM7 server. It does work in FM9. I was hoping for a way to do something similar that was FM7 compatible.

Sorry if I'm not picking up your meaning, I'm not as competent with Filemaker as I would like to be. I already have a join between services and tasks by a standard one-to-many key join. Perhaps it is easier to explain what I want to do. I have users assigning services to pages through a portal. Since services are made up of one or more tasks, I'd like to see the associated tasks for all services listed in the portal below. In the interface, I have the users viewing from a grandparent table layout (Ticket). I use a drop down list of related pages to switch between pages of the ticket. This works well for services - each time I choose a different page in the drop-down, I see the associated services for that page. But when I want to see all the associated tasks for all services for the current page, the only way I could make that work was with the List calculation. And it works in FM9, just not via FM7 server. Have I overcomplicated things? Is there an existing relationship between Pages and Tasks that can do this? Also, not sure what you mean by "bottom half" of the relationship. Do you mean that the List calc is in the Task table listing related service keys? Apologies, I do not have access to the db till Monday so I cannot experiment with it until then.

I have a db where I completed the initial build in FM9 Advanced. I have to publish it on FM7 Server Advanced (which is not ideal, but I don't have any other option) and had set up a portal based on a relationship with a match field to a list function calculation (which lists multiple keys so I can have a many to many relationship). This works well in FM9, but though the List function still works on FM7 Server, the relationship fails. Is there an alternate FM7-friendly solution? To go into more detail, I have three related tables, Pages (parent), Services (child) and Tasks(g-child). Each page can contain many services and a service can be attributed to multiple pages (via a related Service Items table), each service contains multiple tasks, and a task can be attributed to multiple services. There may be a simpler way of doing this with an additional table (e.g. Task Items), and I'd really like to not have to script building more related records if I can avoid it. Thanks in advance for all replies.

I have the following calculation to express a percentage in a cross-tab report: GetSummary ( Crosstab value Summary ; Breakfield ) / GetSummary ( Total values Summary ; Breakfield ) I have had to use a calculation to express the summary because using a fraction summary field does not work when the numerator of the fraction is a crosstab result and the denominator is a subtotal (unless someone here knows better). The problem is that often the Total Values Summary will equal 0 when sorted by the Breakfield and this gives me a calc error (I get a ? result). I did this to solve the problem: Case ( GetSummary ( Total Values Summary ; Customer ) ≠ 0 or "" ; GetSummary ( Crosstab value Summary ; Breakfield ) / GetSummary ( Total Values Summary ; Breakfield ) ; 0 ) Is there a better way to achieve this?

Never mind. It looks like the colon ( in my table occurrence name was causing the error. Strange that no other relationships were affected.

I am doing that. The Layout is displaying data from Line Items: List. I have made sure the merge fields are from that table occurrence also. It does not work. The only way it works is if I put the merge field in a layout displaying data from the original table occurrence.

I am trying to have merge fields display correctly on a layout. I can get it to work on layouts that are set to display data from the original table occurrence (the one that was created when I initially created the table), but when I try to get them to display on a different table occurrence (in a different TOG), it just displays thus: <>. I am careful when setting up the merge field that I select from the same table occurrence that the layout is displaying data from but it will not display. Is this a limitation of the application? I can't find anything in the Help files to confirm/deny this. Thanks in advance for all replies.