Jump to content

LaRetta

Gold
  • Content Count

    11,008
  • Joined

  • Last visited

  • Days Won

    154

LaRetta last won the day on October 16

LaRetta had the most liked content!

Community Reputation

512 Excellent

2 Followers

About LaRetta

  • Rank
    Lifelong FM Student

Profile Information

  • Title
    Developer
  • Industry
    Software
  • Gender
    Not Telling
  • Location
    Everywhere

FileMaker Experience

  • FM Application
    18

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. And here's your file sample_button_barMOD.fmp12 added ... your latest script would probably work also but I think you can see how it works now (and only one refresh object[] needed). By the way, I really like how you provide a sample file and clear explanation of your need for those assisting you. It shows you respect the time of those who contribute here. πŸ™‚
  2. Hi Randy! Yes, a single script with script parameter on each button followed by refresh object works well. Nice to see you around again! πŸ™‚
  3. If the prefix might be a variety of character lengths, you can use this to pull only the text values: Filter ( PrimaryKey ; KanjiNumeral ( PrimaryKey ) ) gleaned from Daniele Raybaudi years ago. I suspect now would be a good time, as Comment suggests, to split the prefix aside or at least use a new indexed calculation for all future requests such as sub-summarizing etc. This would only work if there are no other text characters in the serial or at the end (which I would guess is true in this instance).
  4. I commend you for your curious spirit and desire to learn. πŸ™‚
  5. Ah. I had forgotten. CTRL-return submitted my post! Thanks, Michael!
  6. It can be helpful to export the name field and attach that file here. The reason it isn't as clean and easy is because your data can look like: Mary Jo L Simpson Mary L Smith-Cunningham ... etc ps how in heck to get a single line carriage return here?
  7. https://support.claris.com/s/article/Execute-FileMaker-Data-API?language=en_US This? I think it just came out. πŸ™‚
  8. Yep, they forgot it: https://support.claris.com/s/article/Execute-FileMaker-Data-API?language=en_US
  9. Welcome to FMForums, CatLady! There is nothing wrong with being a novice - we ALL were at one time or another and still are on many subjects. This is the best forum for help and you're getting assistance from one of the best. πŸ˜ƒ
  10. I normally ignore periods in file names as habit but I served one up today to FMS18 including the file's version (for testing) as Master 1.18.1.FMP12. It uploaded fine, opened file, was accessed from desktop fine (10.13.6) using FM18 and the Web Direct file list showed the file (Chrome 80.0.3987.163) but when I opened via Web Direct, message said, "Database not available." Correcting the file name allowed it to be opened via Web Direct. Another good reason to NEVER use dots in file names. πŸ€“
  11. I was suggesting you NOT wrap $layout in quotes. That would be a common mistake. Did you view Comment's file? I suggest you take a look. You can drop all that extra stuff. hahah! We all posted simultaneously! Don't say we aren't quick at assisting folks here on FMForums! πŸ™‚
  12. Hi Steve, How about you create a simple file showing exactly how 1) you are setting that $layout script variable and 2) your Go To Layout[ by calculation] example? Are you wrapping quotes around $layout? πŸ™‚
  13. Hi Steve, you've been receiving advice from two of the top Developers and their suggestions are sound. Using a portal with related records is a VERY SIMPLE technique and process once you grasp the concept. I highly suggest you just take a few moments to understand how a relationship works by reviewing Comment's file. It would take far less time and effort than using AppleScript and it is a basic understanding of FileMaker. I wish you well on your project. πŸ™‚
Γ—
Γ—
  • Create New...

Important Information

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