Wim Decorte

  • Content count

  • Joined

  • Last visited

  • Days Won


Wim Decorte last won the day on May 23

Wim Decorte had the most liked content!

Community Reputation

430 Excellent


About Wim Decorte

Profile Information

  • Gender
  • Location

Contact Methods

  • Website URL

FIleMaker Profile

  • FM Application
    15 Advanced
  • Platform
    Cross Platform
  • Skill Level
  • Certification
  • Membership
    FileMaker Business Alliance
    FIleMaker Platinum Member
  • Title
    Sr. Technical Architect
  1. You make it really hard to help you. Whether you want to use portals or not is totally irrelevant at this point. You first have to articulate what it is you want to do. Saying "something like CDBABY" is meaningless to us, and so is posting only screenshots without explanation. The only thing we can do with that is infer meaning and make assumptions about what it is you want. We shouldn't be making assumptions to help you; you need to explain exactly what it is you want to see and exactly what you should happen when the user goes through your UI.
  2. I have no suggestion because you have not explained what you want to achieve and why. Start by explaining what the UI should do.
  3. Why don't you explain how CDBABY works or what about it that you really like or that your users expect? Pretty sure that repeating fields are not going to be the answer.
  4. don't know their api but you are missing the async key. Perhaps they require it?
  5. Of course it is working, for most people under most circumstances. Since this is an integration there are always a lot of different variables involved that can run interference especially in a Citrix environment that multiplies the number of moving parts. Do a search on this forum and other forums for 'server busy'; it is something that has come up for other people.
  6. to expand on that; you have this isEmpty ( Sub9First_Semester or Sub9Second_Semester) this part: Sub9First_Semester or Sub9Second_Semester will result in a boolean result; 0 or 1, so it will never be empty
  7. You may consider at least getting FM16 and getting familiar with all the features; because at some point you'll have to switch strategies and when you must, that would be a particularly bad time to have to catch up on what there is...
  8. Try to format your formula so that it is easier to read and follow: Case( Sub1E1 = ""; ( Sub1Q1 + Sub1Q2 ) / 2; Sub1Q2 Sub1E1 = ""; Sub1Q1; Grade_Level ≥ 11; ( Sub1Q1 * .4 ) + ( Sub1Q2 * .4 ) + ( Sub1E1 * .2 ); Grade_Level < 11; ( Sub1Q1 * .45 ) + ( Sub1Q2 * .45 ) + ( Sub1E1 * .1 ) ) The 2nd test in there: is "sub1q2 sub1e1' one field name?
  9. @comment mentioned the solution already; since you don't care when you increment; just a have a scheduled script that runs on January first and increments the age field by 1. If you want to use that new field you just created then create a nightly schedule that does the same but just for those records where that date field is exactly a year ago. Do a search on that new date field for Date( month(<your date field>) ; day( <your date field> ) ; year(<your date field>) - 1 ) If you find records then loop through those. If no records are found, exit the script.
  10. You have a 'parcels' key/node that is not correct. It should immediately start with an array as per their API, you start it as another piece of JSON with another 'parcels' key name
  11. and if you want to keep it more readable and at the same know what options are supported in FM, you can use this: https://community.filemaker.com/docs/DOC-8177
  12. If you take that piece of your code and put in the data viewer it will tell you what is wrong. Look at the output and compare it to what is required. Some quick ones: - you don't need the ampersand after the first -H - you don't add spaces between the different sections
  13. Agreed. It usually does not take 360 attributes to describe something. And having that many calculated fields will end up being some performance problem somewhere along the line. So instead of helping you do that; describe what that table is all about and we can probably help you with a better solution.
  14. What kind of unproductive statement is this? You do realize I hope that this just antagonizes? I'm assuming that you are frustrated; if so then say that instead of making these kind of statements. Having said that, of course there is beta testing. But beta testing is no guarantee that there will be no bugs or unintended behaviors.
  15. We'd need more information about the actual call, the configuration, the FM file, etc. I did a test a few weeks ago to compare the new FMS16 Data API to the XML API for speed and was asking for 10,000 records. No errors. So I don't think it is the # of records necessarily that is causing this. What is the result if you just use the -findany command?