Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


IdealData last won the day on November 18 2019

IdealData had the most liked content!

Community Reputation

27 Excellent

About IdealData

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
    Leeds, UK.

FileMaker Experience

  • Skill Level
  • FM Application
    14 Advanced

Platform Environment

  • OS Platform
  • OS Version

Recent Profile Visitors

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

  1. In your child file you need to capture the script parameter. Are you doing that? Set Variable [$sp = Get(ScriptParameter)]
  2. If your object is appearing on all panels then it is not inside the slide control at all. A quick test is to move the slide control and if the object moves with it then it is inside the slide control, otherwise it is outside. I have found that when you drag/drop an object then it will place it inside the slide control, however other methods of object movement (alignment, setting the position manually) do not place the object inside the slide control - merely at the position specified. I suppose FM can't determine which control panel to place the object in if you simply specify the position because all the panels occupy the same coordinate space. Use the Layout Objects tool to see a heirarchy of all objects on your layout. It really explains a lot.
  3. Aaaahh... of course you're executing an SQL command however it will use the fmapp privilege set because you're not going through the ODBC driver, it is actually an FMP command, but using the plugin. So, ODBC not required. Must be a permissions thing. Interesting you can access the security setting but not the script workspace - custom menus??
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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 )
  9. 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.
  10. Devin You said WebDirect requires Safari or Chrome with JavaScript and popups enabled.
  11. 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
  12. 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.
  • Create New...

Important Information

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