LaRetta

Welcome to FMForums, Wella! Why not just serve up a copy of your live file for testing? Then if you update a Client during testing, it won't change the live file. I realize I don't have a full picture of your needs yet, so fill us in a bit more and we can help further!

Yes it is! And I get no flash or jumping, at least using FM21 on Sequoia (attached). I'm glad you attached a sample. This will indeed come in handy at times! popoverContentTest.mp4

So close!! Select the image popover (in layout mode). Notice that you lack the object name for the popover (attached). And sorry to tell you but ... your concept of placing the popover in the exact location will still fail if you resize the window. This just reminds me of why I was so glad when card window feature was added! Some of these old techniques were kludgy so your mileage may vary. Slide control may allow a bit more control (using anchors) and you can play with anchors on the popovers as well but it will all still be a bit messy.

There IS a way to do it, Frank, but it's a bit of a hack. Attached is an example. Place the popover buttons instead to each side at exactly the middle number of the combined height. In the example, I left them yellow and remove their arrow icons. Object-name the POPOVERS themselves (left to 'Image' and right to 'Image2'. The popover (yellow) button widths can be just a few pts (left wider for demo so you can see them) and can be shorter but place them on the horizontal center. Set them to Hide by typing a 1. Resize the popover so each popover encloses entire area as you've indicated. Then place buttons below. You can replace my ugly grey buttons with your little red arrow icons. And you'll have to play around to get the size exact as you want it. AUSCOIN MOD.fmp12 Ah, I see Michael mentioned the method I displayed! 😃

I suspect you are right, Michael!

Hi Frank, if I understand correctly, you need to put the Image field ON the popover. Also set on the data tab at the bottom (data formatting) to enlarge the image. I've attached what I think you want. RECIPES MOD.fmp12 This is what step I followed to accomplish it. I copied the Image from the layout and pasted it onto the popover and then changed its attribute in the Data tab.

Welcome to FMForums! 😄 In addition, you can generate a report from your LineItems table. Create a new layout and select 'Report'. It will walk you through the options. Group by PO# and sort by PO# and possibly Item# (or date added?) then print specifying 'new page BEFORE each occurrence' of PO# and restarting page number as well. Let the process create a script for you. You can also then perform a find in the LineItems table for the date range (or company) desired and automate the Report script by providing User the search fields and add those steps to the top of the report script, pausing the find for User input.

Hi Bob, if you click a tab and it changes layouts then you will never see anything you put ON a tab except for the first (default) tab. Button bar is the tool you seek! 😃

Hey Mark, we have no understanding of your relational structure which makes it impossible to offer solutions. To start, I suggest you post a screenshot of your graph but far better is to post the file itself. You can post a clone: File > Save A Copy As > Empty Clone or create a new small demo file with only the tables & fields necessary to show your issue. In FileMaker, perspective is everything (well, at least MOST things, LOL).

Hey Mark, on second thought ... if you want to add the books in the portal to an Invoice LineItems table by creating new records with those charges then we can do that as well. We'll need to make sure you have a normalised structure though so fill us in. 👆

Hi Mark! 😃 To properly advise, we'll need to understand your structure but let's see if we can move you forward a bit: You currently have a relationship from the parent table (the table your main layout is based upon) to the Books table (portal of Books). So, while on that parent layout, you click a button called 'proceed' above, it can fire a script with: Go To Related Record: From table: Books Using Layout: your new layout and probably Show Only Related Records This is a far as we can go unless I see your graph or understand your structure. I would question why you are jumping to another portal of Books instead of a simple list or card layout based upon the Books table. What is critical for us to understand is 1) the table name the layout is based upon and 2) the table name a portal is based upon and what is the relationship between the two (how are they joined in the graph). The easiest thing to do is suggest you attach your file.

On displaying the parent name in the Child 2 portal ... in FileMaker, perspective is everything so you can handle it a few ways. The simplest, I suspect, would be to create a value list based upon the Jobs table ParentID and also display second field 'name' and check 'only display second field'. It seems you've already started one that can be modified. Format it as pop-up menu, uncheck display arrow and turn off entry to field. You can change its style to match your other regular non-entry fields so Users know that it is not enterable. Let us know how this works out for you, Human! 😀

I'll take a look later when I have more time (most likely tomorrow) but, on the conditional formatting on the pending field in the left portal, you need to include the child ID in the calc so it only fires if there is a related child record. It would look similar to (adjust to match your field/table names): not IsEmpty ( Child::ChildID ) and Child::Pending = Child::Flag

Hi Human, I too am confused by your request but ... the first thing you need to do is fix your example file you posted. In your portal ( tracks 2 ), the fields within that portal are improperly pointing to tracks. Select each field in that portal and change them to point to tracks 2. That is a common mistake that I've fell into many times over the years. Once you change the fields, see what displays for you and then maybe we can pin down your needs. Hang in there; we'll help you through it. 😁

Hey Human, it sounds like you haven't included the Job# in the same relationship. Check again what was shown that you need to create in the simple connection. Make special note of the NOT EQUAL in the Job# line.