Jump to content

Wim Decorte

  • Content Count

  • Joined

  • Last visited

  • Days Won


Wim Decorte last won the day on November 11

Wim Decorte had the most liked content!

Community Reputation

469 Excellent


About Wim Decorte

  • Rank
  • Birthday 12/17/1968

Profile Information

  • Title
    Sr. Technical Architect
  • Gender
  • Location

Contact Methods

  • Website URL

FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform
  • OS Version

FileMaker Partner

  • Certification
  • Membership
    FIleMaker Platinum Member

Recent Profile Visitors

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

  1. As @comment indicated, when using a script you have control over when the calculation is performed and the context and circumstances in which that happens. With calculated fields you have a lot less control. As as @comment hinted at early in the thread, there are definitely circumstances where an ExecuteSQL() can be very slow depending on the user's environment. For a read-up and demo of that, check this blog post: https://www.soliantconsulting.com/blog/executesql-named-buckets/. It contains a powerful example of why you'd want to control the environment before firing an ExecuteSQL(). Also, since you're new to ExecuteSQL(): very quickly adjust to not hard-code your table and field names in the query. The demo contains custom functions that will make the queries 'change-proof' so that name changes in your TOs or fields will not break your query.
  2. The section indicated in red is incorrect. Unlike sending data that is in a variable you cannot do the same for the authorization part. That has to be a real concatenation: "...Authorization: Basic " & $apexBase64EncodedKey & ".... I think the reference to production in the response is a red herring, it's probably a reference to where they authenticate.
  3. Which operating system on the server? The "trigger" part would mean using PSoS (perform script on server) from the client, and not a server-side schedule (which is also an option whereby the user adds a record to a queue table and the server-side schedule processes the queue on a schedule). FMS itself can do server-side PDF generation in either its own temp folder or its own documents folder. If you need to have that PDF then moved to somewhere outside of the server then you'll have to deal with the permissions issues with that and with the mechanism. When using PSoS you'll likely need a plugin to move the file. With a server-side schedule you can use the OS to move it for you (using a script sequence type of schedule).
  4. You could use a text-to-speech web service like the one I used for the 2018 Devcon (https://www.soliantconsulting.com/blog/filemaker-devcon-2018-billy-bass-1/) and have it produce an mp3 file. Once you have it on a container you can use the AV player functionality of the container to start and stop it.
  5. Depends a little on when you fire this calculation. If it will fire each time a user visits the dashboard then some of it doesn't make sense since last month's numbers will not have changed from one visit to the other. So you don't need to recalculate those numbers over and over through SQL, If you feel you need to use SQL because you are constrained to the Dashboard context. You can calculate these numbers at night in a server-side schedule, at the end of the month using non-SQL functionality. The same applies to the current month's numbers, except if the users expect those to be accurate to the minute.
  6. Not anymore it doesn't. Not since Oracle changed its licensing. A standard FMS now does not install anything. When you enable web publishing you are prompted to either use a licensed version of Oracle's java or download the supported OpenJDK. Note the exact supported/tested versions: https://support.filemaker.com/s/article/FileMaker-Server-and-Java-Overview-1503693052471?language=en_US OpenJDK updated its version late October but the latest FMS18v3 requires the previous one (which you can download from their archives). So for best results with FMS, completely remove any pre-existing Oracle Java.
  7. Never seen that one before and install very many FMSes. Is there an install log or anything in any of the system logs? Sounds like this is a dev or testing box? If it is not then move all that stuff that requires Java away from the FMS machine. FMS is extremely sensitive to the wrong version of Java.
  8. Would you exceed 24GB per licensed user per year? That would be a lot... (and container data doesn't count).
  9. The Base64encoded version of the file may be bigger than what the alternative is. The Data API for instance uses the "multi-part upload" mechanism which keeps the upload closer to the actual size the file. Something to keep in mind if speed is off the essence or the internet connection is poor (low bandwidth, high latency,...)
  10. Using the Data API on FileMaker Cloud requires a token based on your FileMaker ID, here's how to go about that: https://www.soliantconsulting.com/blog/data-api-filemaker-cloud/
  11. Yes, you can buy a single license but in reading your intended workflow it strikes me that parts of the work is done in different places at different times. Meaning a hosted solution shared on multiple client machines, some of which are probably going to be handheld devices (for the on-stage work). Since FM is a platform designed for sharing data and collaborating you may find that buying a single license is expensive relative to the entry-level 5-user license-plus-server. And with the single license I think you'll be challenged in putting the proof-of-concept into testing and eventually production. Especially safe-guarding the file and its intellectual property and its data integrity.
  12. Short answer: yes, nothing in your description begins to even remotely push the envelope on the FileMaker platform. Ongoing subscription: once you start building software, you're going to end up with a subscription for the tool you use to write that software. That's not unique to FM, it's just what it is. Since you mention this explicitly as one of of the disqualifying characteristics I wanted to make sure and call it out and set realistic expectations.
  13. A couple of things to check: - the calc context of the RLA calc - in production does the Data API account have the correct priv set attached? - check the data in "ind_sent_to_website"
  14. In as much as it applies, one can use the repetition feature of variables to store windows-specific info. Variable repetitions are numeric but they can be made to work as 'named buckets' by using "Code(<whateer the window name>) so that they can be easy to retrieve by name. Variable reps do not need to be sequential. This doesn't solve the problem of wanting to edit content but a round trip to a global field may solve this.
  15. You can usually find these answers in the Claris FileMaker knowledge base: https://support.filemaker.com/s/article/FileMaker-and-macOS-10-14-Mojave-compatibility?language=en_US The known issues with 16 and Mojave are listed, if you feel these do not apply to you then you can use Mojave. Personally I'd stick with with High Sierra or upgrade to 17/18 if you must have Mojave.
  • Create New...

Important Information

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