Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


jaboda last won the day on April 18 2011

jaboda had the most liked content!

Community Reputation

4 Neutral

About jaboda

  • Rank

Profile Information

  • Location
    Findhorn, Scotland

FileMaker Experience

  • FM Application

Platform Environment

  • OS Platform
  • OS Version
    Windows 10

Recent Profile Visitors

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

  1. I don't think that's strictly correct. For example I may allow users to delete records, but I don't want them to use the 'delete all' menu item and possibly delete thousands of records at once. As it happens I generally restrict record creation/deletion to my scripts (and therefore check the validity of the action within the db) as per your third point, but as users can edit records they can perform an import and update many records at once. This will have unintended consequences and probably cause some data corruption. I do not want them to be unable to edit records, but want them to be
  2. I've made some progress on this. Take a copy of jwpc.jar in FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\fmi\WEB-INF\lib and rename it to jwpc.zip. Unzip the contents. In the archive are the following xml files, which can be edited to remove the Import Records (or any other) menu item: com\filemaker\jwpc\iwp\ui\statusarea\menubar\main-menu.xml <menuitem name="IMPORT_RECORDS"> <menuitem name="FILE_DOT" /> </menuitem> <separator /> com\filemaker\jwpc\iwp\ui\statusarea\menubar\menu.xml &
  3. I don't know how short the minimum is but I assume that whatever it is .001 should cover it. The main problem is if the user interacts during the pause. The Yellow bar can be suppressed by using the following script: You may not need the Refresh Window, dependent on your use case. As with most things of this nature testing is important, especially as it might change with new Web Direct versions (though this has been fairly stable as far as I recall).
  4. I suspect it is a font issue, but how can that be rectified in Web Direct? The only way I can think is to use a web viewer which would cause massive slowdown in this solution. Also I couldn't get the Emojis to display correctly in Chrome in https://typezebra.com, though they did in Firefox so not sure that'd even fix it.
  5. I think I've found the issue. On Chrome/Edge those Emojis don't display properly - even though they do in Emojipedia, and in Firefox. Not sure if there's a workaround apart from using different Emojis that work 😒.
  6. Yes it does and it's working now I've upgraded to 19.2.1.
  7. This is a strange one. I use Emojis in WebDirect and I thought it was working when I developed it but testing it again and it doesn't. The '⬅️' and '➡️' Emoji work fine but the '↔️' and 'ℹ️' Emojis look very different (like they do in FileMaker Pro on Windows). I'm using FileMaker Server 19.2.1 accessed via Chrome 89. Any ideas?
  8. WebDirect usually does not update the window when scripts are running, and far less reliably than FileMaker Pro. Refresh Window also usually doesn't work - instead I use a Pause/Resume script step for 0.001 seconds and this fixes many issues.
  9. Found a small bug with this export. When exporting the fields the above examples either use the Quote function or add \" to add a double quote to the start and end of fields. Unfortunately if the field contains double quotes this is not compliant with RFC-4180, which specifies that they should be escaped with a ". The above examples either leave them as is or use the FileMaker standard of \". The fix is easy though - use the following custom function instead of the Quote function:
  10. My reply perhaps wasn't clear. Yes if the self-extractor created 'FMS' instead of 'FileMaker Server 19' that would resolve many of the issues if it's run from a folder without a space in it (for example 'C:\users\admin\Downloads'). However if it's run from 'C:\Users\John Smith\Downloads' or 'C:\FIleMaker Installers' then it would still fail. Therefore they should fix the original issue. 19.1.2 worked properly so why not 19.2.1?
  11. That wouldn't resolve the issue - if the installer is extracted in a folder with spaces in the name then it would fail. I suspect they've missed out quotes when referring to the FMS msi package, which is just bad testing.
  12. After an e-mail exchange with Claris they provided a fix which might be useful to others. By default the installer extracts to "FileMaker Server 19". However the Setup in that folder won't work if there are any spaces in the path name. To fix the issue move the contents of that folder to somewhere without spaces in the name (for example C:\users\admin\downloads\FMS not C:\users\admin\downloads\FileMaker Server 19). I am amazed and quite annoyed that this simple issue got through testing. I expect better from Claris. However thankfully the fix is simple.
  13. I'm trying to install FileMaker Server 19.2.1 on Windows Server 2019 (a Microsoft Azure VM). However when I run the install it installs the prerequisites then shows the setup options dialogue (attached). I've seen some people had the same issue on the Claris forums, but mainly with FileMaker Pro (which installed no problem). None of the suggested fixes worked. If I try to install it once FileMaker Server 19.1.2 is installed it stops the installation from working and I have to run setup again with 'repair' to fix it.
  14. I noticed my server didn't have http 2 enabled and thought it was because I was on Windows Server 2016. I have just installed a new VM with Windows Server 2019 and http 2 is still not enabled. Any ideas why this would be? According to Claris it shouldn't require any configuration. I am using FileMaker Server 19.1.2 (as 19.2.1 wouldn't install for some reason). Edit: Think I found the issue - it requires 19.2.1, which I couldn't install as the installer didn't work. Oh well - hopefully sort it soon.
  15. That's great, thanks. I would suggest adding compatibility to the Change Log.
  • Create New...

Important Information

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