Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


rivet last won the day on July 18 2016

rivet had the most liked content!

Community Reputation

39 Excellent

About rivet

  • Rank
    < = >

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    Hight Sierra

Recent Profile Visitors

6,333 profile views
  1. Thanks LaRetta. I just posted a subtle update (v2)
  2. I rewrote a timepicker I liked (originally lifted from calendar5 by Readdle). It is now 'tableless', I almost had it 'scriptless' but could not get a refersh to happen, regardless, enjoy RIVET timepicker.fmp12.zip
  3. Here is a nice UI element that I lifted from another app. RIVET expanding popover.fmp12.zip
  4. Thanks Fitch for taking a look at this. I sensed it might be over built but I still need an extra step. The schedules are monthly, bi-monthly and quarterly. So I would only want to start the list once the calculated date is on or after startDate. i.e. startDate of May1 - monthly schedule would start month 5 and onward - quarterly schedule would start month 7 and onward.
  5. Hi CFD, longtime user, first time builder! I need to build a list of dates, from a starting date, up to the 1st of the month after Get ( CurrentDate ). Each date will start on the 1st, and will spaced by an interval of so many months. EXAMPLE ƒ serviceSchedule ( Date ( 5 ; 1 ; 2017 ) ; 1 ) //monthly = 5/1/2017, 6/1/2017, 7/1/2017, 8/1/2017, 9/1/2017, 10/1/2017, 11/1/2017, 12/1/2017, 1/1/2018, 2/1/2018, 3/1/2018 ƒ serviceSchedule ( Date ( 5 ; 1 ; 2017 ) ; 3 ) //quarterly = 7/1/2017, 10/1/2017, 1/1/2018 I have the loop start on January of the startDate year, and loop from there. I do get the results but the behavior of the CF is peculiar, which I am guess might be use of local variables ($). Attached is a test file, try the function in the data viewer and note that you have to click evaluation twice to get the result. // serviceSchedule ( startDate ; interval ) Case ( // Initialize not $loopStopDate ; Let ( [ $itvl = interval ; $sd = startDate ; $startYear = Year ($sd) ; $cd = Get ( CurrentDate ) ; $loopStopDate = Date ( Month($cd)+1 ; 1 ; Year($cd) ) ; $loopInterval = 1 ; $dte = Date ( 1 ; 1 ; $startYear ) ]; serviceSchedule ( $dte ; $itvl ) ) ; // Ignore and up date startDate < $sd ; Let ( [ $dte = Date ( 0 + $loopInterval ; 1 ; $startYear ) ; $loopInterval = $loopInterval + $itvl ]; serviceSchedule ( $dte ; $itvl ) ) ; // Add to array up date startDate < $loopStopDate ; Let ( [ $array = case ( isEmpty ($array) ; "" ; $array & "¶" ) & $dte ; $dte = Date ( 0 + $loopInterval ; 1 ; $startYear ) ; $loopInterval = $loopInterval + $itvl ]; serviceSchedule ( $dte ; $itvl ) ) ; // END startDate > $loopStopDate ; Let ( [ result = $array ; $array = "" ; $cd = "" ; $dte = "" ; $itvl = "" ; $loopInterval = "" ; $loopStopDate = "" ; $sd = "" ; $startYear = "" ]; result ) ) serviceSchedule.zip
  6. Most of my medium to heavy scripts are now performed on server. To give the users some feedback while they wait, I wanted a method that was simple and subtle. In this example I ; added a popover button with '+' icon set the feedback message in the popover title bar formatted, sized and positioned the popover added a OnObjectEnter script tigger to the popover in the script I add a PSoS step with Wait for completion set to 'On' last step of script is Close Popover
  7. Yes thanks, for showing that video and introducing the party model to me, definitely some good take-aways in it. I am partly there with two main tables company and profile, which have their related; vendor, client, agency, contact, artist tables etc. But to go full 'party model', I will be curious to see how he pulls it off in FM. Yes denormalize at the invoice. Yes Docket is same as project. The verdict is out on the advantages but if I did do it, I would have a server-side script bursts the json into a table for printing. The quote system is already like that. Whenever the user edits a quote, a server-side script creates 300 records/template rows and populates the quoted items in about 3 sec, its not that bad. So I was only toying with the idea of not having all those un-awarded, never to be reported, line items, weigh down the system. thanks again.
  8. If I am still on track with you; I have a table occurrence quote_agency ( quote::id_agency = partner::id AND quote_one = partner::type_agency ) so when the client does a search in field quote_agency::company, it will only return partner records that are agencies. (NOTE I forgot to mention the partner fields in initial post; type_agency, type_production, type_billto ) What if the company that was invoiced in 2015 has a name change in 2017, What name should show on the 2015 invoice after the change? yes just finished video thanks, and saw that ignore Interesting I have be debating about storing all quote line items as json until the quote is awarded, at which point I would burst into line items. Am I thinking old school on this one? There can be multiple invoices and quotes on a single project, what binds them, just a docket#? thanks again.
  9. Thanks for reply, I will have a look at the video. I do have a role table for unlimited team members ; director, producer, writer etc. But in this case for searches etc I think the fix foreign key is best an still flexible if another partner type does come into play. company name field is for historical reasons. If the company name changes at some point in time, I need to have an accurate history on past invoices etc. yes just a single contact and a single email contact field, similar reason as the company field. Also it can be used as an open field that allows any name typed in, with no relationship to any table. yes a quote can have revisions docket. to clarify; an approved quote will open a new docket in the docket table.
  10. I am building a new system ground up. There are three section ; - quote - docket - invoice In each section there are three relationships going to the table partner ; - production (company) - agency - bill to table : partner fields: id, id_company, company, address, phone, contact, email quote turns into a docket and docket will then have related quotes and invoices. Once the partners are established in the initial quote, they are unlikely to change in all three section for the duration of the project. Regarding keys, this is what I am thinking and I am just looking for a 'brain check'; My thought is I want to maintain/relate the initial three partner records across all section unless there needs to be a deviation. In each section I will have three child keys for partner::id: - id_production - id_agency - id_billto By having a child key for each; - I can place the fields on layout without a portal - searches will target exact partnership type - I believe it will allow for easier modification/deviation of a partners record Thoughts, pitfalls?
  11. Help, for some reason I can't get this to work when MacOS region is set to Canada.
  12. for those using lauchbar's wonderful snippet feature, here are all the functions for the BaseElement plugin BaseElements_snipits.zip
  13. Hi Brendan, I recently ran into the same issue. I typically use ExecuteSQL function to get my data for charting. There are some limitations of this function but with some help I was able to bend the data into shape. Have a look: https://community.filemaker.com/thread/166294. Hope that helps
  • Create New...

Important Information

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