Jump to content

IdealData

Members
  • Content Count

    2,673
  • Joined

  • Last visited

  • Days Won

    14

IdealData last won the day on November 18 2019

IdealData had the most liked content!

Community Reputation

27 Excellent

About IdealData

  • Rank
    IdealData

Profile Information

  • Gender
    Not Telling
  • Location
    Leeds, UK.

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    14 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    Yosemite

Recent Profile Visitors

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

  1. So, now you know how to add TOs to your file then why not establish a relationship to it? Relationships can be sorted, so you can get a reverse sorted table to access the end of the table first. AFAIK FM relationships can be cached, however SQL is never cached. The report to XLSX is fairly slow, try CSV instead.
  2. Or even consider HOSTING options - there's plenty around, just google "filemaker hosting". Your single file requirement and low user count is ideal for this.
  3. I have been victim of this may times too. As far as I understand it FMS runs the http service with settings that are generated during the FMS install. Sadly, when macOS updates then the http service may be left incompatible with the FMS settings. You mention that the WPE doesn't start automatically is one I have witnessed too. Ultimately this needs a re-install. Personally I turn off OS-updates and Java updates too. Purists might reckon I'm leaving the machine "exposed", but I don't really want to be a slave to the machine! I've also managed to work out manual starting of the web services, but they also fail eventually. Incidentally, if you plan to upgrade to FMS18 then be prepared for the Java changes - after FMS 18.2 Java is no longer included with the installer so check the installation notes thoroughly; ideally trial run on a spare machine.
  4. Quite right comment. For the OPs benefit I was showing how to write the code in a simplified form which is easier to read and therefore debug.
  5. Here is your case statement on a line-by-line basis Case ( IsEmpty ( DatePaid ) or DatePaid>Due Date ; AmountDue*.05 ; 0 ; Due_Date<Get (CurrentDate) ; AmountDue*.05 ; 0 ) All I have done is put in some returns to separate the individual cases Notice that case #2 starts with "0". This is not a comparative but will always be true and will yield either 0 or 1 based on Due_Date<Get(CurrentDate) Should your statement actually be... Case ( IsEmpty ( DatePaid ) or DatePaid>Due Date ; AmountDue*.05 ; Due_Date<Get (CurrentDate) ; AmountDue*.05 ; 0 )
  6. 49 files is obviously not a simple solution - determine if you really need to consolidate first. I've been running a 30 file solution for 20 years and have considered the consolidation route also. Originally I had nearly 40 files to deal with but I did consolidate some of them because they were merely "utility" files. I even created a new file to hold all the "contacts" from 5 other files simply from an interface perspective only (it makes sense in this instance). One of the benefits of a multi-file solution is that you can develop in different files at a time and deploy them individually. Possibly important if you have more than one developer! Some years ago I had a chat with a very experienced developer that retails a significant application; he said it nearly killed him and actually migrated a 30 file solution in 2 consolidations because he had to maintain a deliverable product. Break the problem down to smaller chunks that you might deliver as "modules" (like my contacts?) Factor in your migration path too - you need to get the data from your production system to the new version ultimately. The final product will likely be somewhat different to the end-user current experience so, once again, consider delivering in smaller units to take the pressure off yourself and ease the users into the new world.
  7. Devin You said WebDirect requires Safari or Chrome with JavaScript and popups enabled.
  8. Hi All Apparently FMI knows about this, and their advice is as follows The problem for me is I don't have an SSL certificate and am using the in-built FM certificate. I would have thought the in-built certificate would at least let me import from the hosted file, especially as I did this from the desktop of the server. The script doing the import has not changed for many years and still runs fine on pre-18 servers. Other than purchasing an SSL has anyone get a solution, without resorting to downloading the hosted files and running locally (I'm trying to avoid that step). Thanks
  9. I experienced something similar with FMS16. I was calling PSOS and after 30 or so runs the FMS script engine fell over and needed a restart. It never locked up the whole server though. Eventually I traced it down to using the Save As PDF during the PSOS, because when I removed the PDF generation then there was no failure.. Because I still needed the ability to run PSOS I built a server side "robot" to perform the scripting - thereby removing the PSOS from the whole scenario. The server side robot calls the script using standard method. As I say, it only appears to affect PSOS calls that involve a Save As PDF - everything else seems fine. Try using the command line tools to restart FMSE rather than reboot the server.
  10. Have a look at Custom Web Publishing - using XML. https://fmhelp.filemaker.com/docs/18/en/fms18_cwp_guide.pdf Nothing much changed since FMS16.
  11. If it did exist I suppose the script trigger would be OnWindowSelect The existing script triggers could be leveraged with the right techniques: OnLayoutSizeChange, OnModeEnter, OnModeExit, OnViewChange however all of these require some kind of action WITHIN the window. I don't think FM can determine that you have brought the window to the foreground.
  12. Look more carefully at the help. It is organised into 2 sets of options; one for Windows, one for Mac. It is a Mac specific feature.
  13. Hi Have a look at the "Install Plug-in File" script step. If you save the plug-in to a container you can use the above step to install the plug-in. Great thing about this is it works in all FM applications (except FM Go) and you don't have to worry about where to store the plug-in. HTH
  14. Hi First, get the Linux version of the plug-in. FM Go does not support plug-ins so you need to process your script on the server, e.g. PSOS. Merely installing the plug-in on FMCloud does not grant the plug-in features to FM Go. To install the plug-in on FMC create an FM file with a container that holds the plug-in and upload to FMC. Write a script to run on PSOS to use the "Install Plug-in" script step. That should install the plug-in on the server (because it ran server side!). You need to enable plug-ins on the server first, of course, on the Connectors tab. You will appreciate the beauty of running plug-ins server side when you realise you then don't need to install plug-ins for the client! HTH
×
×
  • Create New...

Important Information

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