Jump to content
Guy_Smith

Sliding Left Won't Work (for the 2,103rd time this has been asked!)

Recommended Posts

I've read through the previous posts on things not sliding left properly and I've tried all of the known fixes, and I'm still stumped.  Here's my problem:  I'm trying to get a mailing label layout to display a comma and then any suffix that may follow a person's name (such as Ph.D, PE, MSCE, etc.), but if there is no suffix, then I do not want the comma to display.  Should be a piece of cake, right?!  Ummm...Nope!

I have fields for prefix (Dr., Ms., Mr., etc.), first name, last name, and suffix.

I first added a calculation field to combine the prefix, first name, and last name:  = Prefix & " " & First_Name & " " & Last_Name and a second calculation field to combine a comma and the suffix:  = ", " & Suffix.  The comma and suffix field is conditionally formatted to be white if there is no suffix.

When viewed in Browse Mode, it's looks wonky, but, OK, it's sorta supposed to look goofy, so I can handle that - let's switch to Preview mode and see what happens:  There is a gap between the last letter of the last name and the comma - about two letter-width's.  And printing it shows the same problem - way too much room between the last name and the comma. 

I have quadruple-checked the following:  The fields are touching - I've even tried overlapping by a pixel or two just to make sure, to no avail.  All fields are set to left and top, all padding is set to zero, and, yes, I did check the 'Remove blank space by: Sliding Left' checkbox.  And I've tried the above using the original text fields (plus a new text field for the comma), my added calc fields, and merge fields. I'm also not sure why I have a blank label/page between each entry - may be a field is too close to the edge, but I'll worry about that later.

I have attached a copy of the offending file for reference.

I'm sure it's something simple, but I just can't find it - any help would be greatly appreciated!

Mailing_Label_test_1.fmp12

Share this post


Link to post
Share on other sites

I changed the field calculation to show how it should be structure.

Mailing_Label_test_1 MOD.fmp12

Hey Webco, 

I accidentally deleted your topic. The Forum (or me) is showing double postings today, and I thought that it had actually double posted your reply. Please resubmit it as it is a great way to approach the OPs need.

Share this post


Link to post
Share on other sites

LOL Lee...

I just pointed out that if both merge fields are in same text black, this works. The problem was that the second text black had a fixed left point, leading to the extra space (and in other longer names, would cause on overlap...)

 

Screen Shot 2017-02-09 at 11.19.10 am.png

Share this post


Link to post
Share on other sites

Lee and webko:  Thanks so much for your feedback.  The revised calc makes my solution a LOT more robust and will prove useful in making some of my earlier attempts work much better!

webko:  I'm still a bit confused about  "...The problem was that the second text black had a fixed left point, leading to the extra space..."  Where do I find the fixed left point setting?  I've gone through every panel in the inspector, but can't find anything different between the two strings:  The text attributes are the same, there is no padding in either, and all indents are set to zero.  Can I please bug you one more time and have you explain this to me in noob-speak?

Thanks again - you guys rock!

Share this post


Link to post
Share on other sites

A text block has a position on the screen - let's say your original2nd text block with the suffix was left 300px, top 10px, right 400px and bottom 25px. Any text within it will start at 300px from the left. The other left text block may have started at 10px and have about 240px of text. The second block will still start at 300px, leaving a large gap.

It's more obvious over multiple records where the end of the first text block will change, but the second will always start at the same point...

Screen Shot 2017-02-10 at 10.31.19 am.png

Share this post


Link to post
Share on other sites

Thanks for your time and patience on this, webko, but I think I'm even more confused now:  I thought the whole purpose of sliding left was to strip away the extra blank space in the leftmost block to allow for differing lengths of text, such as names.  Is there a better way to merge the fields together to avoid this 'gap-osis'?

Thanks again!

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Arno
      Hi There,
       I’m pretty new with using Filemaker, but still I built a solution that fits pretty all my needs (for now…)
      I’m still experiencing one big problem with my solution for which I would need help.
      Here’s the context : I run a little company. We receive financial reports every quarter.
      All quarterly reports ( Excel file or csv file) have the exact same form.
      I then created a layout based on the table created when importing the csv that works properly.
      My need: as I’m to receive a new financial report on next quarters (Q12018, Q22018, Q32018 etc.), I would like to pull the new data from my Main layout.
      Is there a way of having a layout pull the data from the new table (actually whatever table) to be created each time I’ll be importing a new Financial Report without getting rid of the original data (which I would like to keep in place, for obvious reasons)? Let’s say from a pull down?
      Thank you very much for your help and don’t hesitate to get back to me if my explanations aren’t clear enough.
    • By kolvorok
      I'd get some problems with date formats after installing FMS 15, and I'm trying to solve it by importing to a clone of the original database. But two tables has no layouts and I can't find a way to import these tables without making a layout in the clone or adding a table when importing. The last seems to be the simplest, but how will the relationships behave?
    • By ggt667
      How can I extract content from sub summary layout objects using? https://fmhelp.filemaker.com/help/16/fmp/en/index.html#page/FMP_Help/getlayoutobjectattribute.html
      I'm able to grab the content from the first subsummary, not the remaining however.
      The following:
      set field( output; GetLayoutObjectAttribute( 'header', 'content' ) & GetLayoutObjectAttribute( 'row', 'content' ) & GetLayoutObjectAttribute( 'footer', 'content' ) ) works fine, the bad thing is that only row 1 finds its way to the output-field.
       
    • By Bobby Bradley
      I have a layout for printing on a letterhead and have inserted an image file as the Background Image to serve as the letterhead.  Printing and Save to PDF work as expected, but for the life of me I cannot get the background image to display correctly in Preview mode.
      Not displaying correctly in Preview mode is not terrible except, when the client does a print preview and it doesn't line up, there will be questions...even though it print correctly.
      Basically, it looks like the background image has a pre-determined padding applied to it at the top, but all parts and objects are set to padding 0.
      Has anyone else experienced this?
      Preview mode - letterhead has padding

       
       
       
      Printed PDF - the letterhead is up where it should be:

    • By rainforestjim
      I'm using some script to direct users to different layouts when the access my database via WebDirect. At the moment all users are directed to one of two layouts using the following 
      #t ( Case ( APP__Application::Type = "Long" ; "Application Detail WEB" ; "Application Detail Rapid WEB" ) )
      What I actually need to happen is that when a "reviewer" logs in they are directed to "Application Detail Review WEB" for everyone else the above code is correct.
      Any help would be much appreciated.
×

Important Information

By using this site, you agree to our Terms of Use.