Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


LaRetta last won the day on October 14 2018

LaRetta had the most liked content!

Community Reputation

499 Excellent


About LaRetta

  • Rank
    Lifelong FM Student

Profile Information

  • Title
  • Industry
  • Gender
    Not Telling
  • Location

FileMaker Experience

  • FM Application

Platform Environment

  • OS Platform
  • OS Version
    High Sierra

Recent Profile Visitors

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

  1. Why use auto-enter (text) field instead of straight calculation? The only reason you might wish to use an auto-enter text field would be if the User must make a change to it but since this is only searching, it wouldn't matter. By making it a calculation, it would adjust if the User changes the field text. Otherwise, with auto-enter, you would need to remember to specify REPLACE existing value. Just a thought. Also, I just tested this and unless I'm mistaken, you can place that calc off screen and it will still be searched by Quick Find. That is kinda cool! 🙂 Wow, I didn't know about this: I'll need to add that to our word separator exceptions list!
  2. You might also consider a more generic approach. This 'on-the-fly' method of specifying global value lists is very familiar to Mr. Vodka as well. Having this trick in your tool kit is VERY handy (attached) and would work nicely in your situation, John! Global_VL.fmp12 By the way, if you do need to restrict values by removing those years already assigned, you can do that as well, right within the Let() statement itself. I wasn't clear if that was part of your need.
  3. Actually, I don't see a value of using JSON here and it means looping twice. I appreciate the attempt anyway!
  4. BTW, I want to restrict the x axis if over a certain number since the date range is open-ended. I realized I could use: 12 * ( Year ( EndDate ) - Year ( StartDate ) ) + Month ( EndDate ) - Month ( StartDate ) ... a calculation provided by Comment awhile back instead of the twisted calc I started to use in generating the x axis zeros (in the disabled section of my script).
  5. Thank you, Jeremy. I have used the method of specifying empty values before, picked up from Michael Horak (Comment) a few years back but it was when setting a flat 12-month (predictable) period where I could also hard-code the x axis (monthNames) but since I wanted an unspecified number (and names) of x axis, I was of course stuck! Just before you posted, I finished including an unspecified number of 0s but I disabled it instead deciding to include it in the loop itself (result is attached). I look forward to studying your creation since I'm just getting my head deeply into JSON and the more methods I understand, the better. 😀 Note: I decided to use true dates when incrementing through the months because then I wouldn't have to test whether I crossed a year boundary. It seemed simpler for me. InspectionsMOD2.fmp12
  6. Hi everyone, I have a simple chart which displays month's totals but some months have no data. I'm trying to adjust the script to set the 'empty months' in the date range to 0. Does anyone know if that is possible? I've attached sample of the script, chart and data. Date range is october, 2017 - current date. Notice there is no March 2018. Can I make that empty year/month 0? Thank you for ideas! I'm unsure whether best to set the $description ahead of time with all 0's then replacing the value or whether I should track the month number as I go and add the 0 when current month doesn't match prior or whether there is a better technique to either approach. I worry because I'll be crossing year boundaries so a simple + on month number will not work. Inspections.fmp12
  7. Comment, your CrossTabR.fmp12.zip file is extremely lightweight and easy to implement! Thank you for providing this - it absolutely ROCKS! 😀
  8. What still amazes me is that LotusSuite (Approach was their database) had crosstab functionality in 1998 and I used it all the time in designs yet FileMaker still has nothing similar.
  9. To suggest a new feature, post your suggestion here: Product Ideas But be prepared to answer the same question Comment is asking. 🙂
  10. Thank you for letting us know, Stephen. I will miss him too.
  11. I can understand inheriting a mess; believe me. But if someone quoted you $100,000 to fix your solution, they saw you coming. 😱 Seriously though, have you even checked with a few reputable GOOD Developers on how you might improve your solution? I suspect not. I've switched out many highly-complex systems that were twisted for under $10,000, making substantial changes from flat-file to relational and simplifying their lives (reducing 600 fields to under 100) and there are many Developers who could help you with it. Nobody says you need a complete rewrite but you'll never know how it can be improved if you don't check. Anyway, I wish you well with your project.
  12. PSOptATx_Additional_1, PSOptATx_Additional_2 ... and more. Whenever you see multiple fields named the same but followed with a 1, 2, 3 ... etc, it means you probably should be using related records instead. The fact that you have this type of complex calculation and the fact that you have a single script with 572 steps, all points to an overly-complex solution. You will continue to have a nightmare developing in such a structure and I (again) highly recommend that you step back and seek professional assistance in fixing your issues once and for all (and no, I'm trying to drum up business because I am not available right now anyway). I say it only because somebody needs to provide you with a reality check. We would be providing a disservice if we did not tell you the truth here. 😐
  13. Why are you using nested IFs? In even the most complex solutions, I've never needed to write something that ... strange. added ... BTW, that isn't a script step, that is a calculation. You have fields with different numbers at the end ... prime example of a structure in deep trouble.
  14. Or a woman will get married and change her name and all her records will break. 😃
  15. Hi Amy, So you have a single job record with a field holding multiple reps assigned? It might help to see your structure because it sounds like a join table would be worthwhile. If you ever wanted to generate a report by sales rep, showing their jobs (for example), you would be unable to do so since a single job record could not appear in two sub-summaries (reps). If you use a join table, reports would be generated from there and the parent job would display under all reps. If I'm not understanding your structure and your reps are not multiline in single field, you can ignore my response.
  • Create New...

Important Information

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