Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by dysong3

  1. Hi, Here is a custom function that I found on Briandunning.com. The problem is when I try to create a new function with this code, Filemaker refuses it saying The "here" above is situated before the parentheses after "WordWrap" and before "UnprocessedText". Would someone be kind enough to tell what I'm missing here to get this up and running? Let ([ TruncatedText = Left ( Text ; Size + 1 ) ; CountOfSpaces = PatternCount ( TruncatedText ; " " ) ; CountOfReturns = PatternCount ( TruncatedText ; "¶" ) ; PositionOfLastSpace = If ( CountOfReturns > 0 ; Position ( TruncatedText ; "¶" ; 1 ; 1 ) ; Position ( TruncatedText ; " " ; 1 ; CountOfSpaces ) ); AddReturn = If ( CountOfReturns > 0 ; "" ; " ¶" ); ThisLine = Trim ( Left ( TruncatedText ; PositionOfLastSpace ) ) ; UnprocessedText = Right ( Text ; Length ( Text ) - PositionOfLastSpace ) ; Result = If ( Length ( Text ) ≤ Size ; Text; ThisLine & AddReturn & WordWrap ( UnprocessedText ; Size ) ) ]; Result ) Sorry everyone. Please dismiss my post. I just realised that I was trying to include "WordWrap" as a function parameter and as the function name. All's well.
  2. I have a number of scripts that have worked perfectly for years in previous versions of FileMaker, however in FMP 15 they causse FM to crash. They only way I have found to avoid the crash is to use the debugger and to use the "step into" button. That of course is a very cumbersome workaround. You can see one of the culprits below. Anyone have any ideas what's wrong here?
  3. Well the web viewer appears to be the culprit. But that doesn't resolve my problem as I would like the script to work and keep the web viewer. Any ideas on how to do that
  4. No onTimers, but there is a web viewer.
  5. There you go. There are plenty of others should this not be helpful. filemaker crash log.rtf
  6. Hmm Error capture doesn't seem to offer any help. The scripts still work perfectly well in previous versions of FM. I have backups and the oldest backup I could find, more than a year old, behaves in the same manner. The same scripts make FM15 crash.
  7. Sorry for being a dummy, but how do you access the FM crash log? I've just googled it and found nothing. Of course you're right about copy and paste. It just goes to show how old some of these scripts are, they were made before variables were part of FM and I've never got around to correcting them. That is not the reason for the crashing as I've just corrected it and it still happens.
  8. Hello, Stange situation here. After reinstalling FMS15 to resolve an issue, one of my FMPA clients on just one of my computers displays "connection failed" when trying connect to the available databases on the server when trying to connect with the local ip adresse. All while several other computers have no problem doing the same. The FMPA client that has the issue has no problem connect to available databases via an external ip address. I have never seen this before and can't find any meaningful information on this by googling. Would anyone have any idea what's going wrong here? The error appears to be (51) on FMS.
  9. FMPA 14 and 15. Same with both. Sent from my iPhone using Tapatalk
  10. Hello, I have a FMS 15.03 running on Sierra. I recently upgraded the OS from 10.12 to 10.12.2. As soon as I did this Webdirect stopped functioning. The webdirect URL gives a "404 not found" error message. I have tried downgrading the system from Time Machine backups to 10.12.1 but to no avail. I have checked all the troubleshooting items that can be found here. There is nothing I can find that would impede webdirect's functionality. Would anyone have any idea what might be amiss? Or any ideas for getting Webdirect back up and running?
  11. Webdirect stopped working

    Just reporting that redoing the upgrade to OS 10.2.2 and the doing a "dirty" FMS install (i.e. not clean) seems to have resolved the issue.
  12. Webdirect stopped working

    No I don't have OSX Server running. Here is what is using port 80 All this appears to me, (but what do I know) associated with FMS.
  13. Webdirect stopped working

    Hmm. My problem keeps reappearing. When I try to edit deployment the web server fails with the following error message: Any ideas what may be provoking this?
  14. Webdirect stopped working

    Thanks for all that. A clean reinstall fixed the issue.
  15. "save records as PDF" provoking error

    Since migrating from FMSA 13 to FMS 15 and upgrading different versions of FMP 14 and 15 recently, certain layouts are provoking an error with the function, "save records as PDF". This is independent of whether the function is in a script or called manually. The PDF error that now appears is: Would any one have any ideas of how to resolve this. The only workaround I have found is to dig out an old version of FMP 13 and there the "save records as PDF" works fine. I wold like to avoid having to do this.
  16. "save records as PDF" provoking error

    Would you know what the criteria is for creating layouts that work for PDFs. I work on Macs.
  17. "save records as PDF" provoking error

    Thanks for that. But it seems a bit over the top to invest in a plugin just to have a function that standard FMP is meant to deliver.
  18. Hi, I just installed FMS 15 and have found that a couple of my databases won't open in FMS15 once they have been uploaded. I have tried recovering them before uploading but all to no avail. Would anyone have any ideas what might be going wrong here?
  19. some databases won't open

    Thanks so much for that. I knew there had to be a catch ... which would have taken me ages to decypher.
  20. I have successfully installed FMS 15 on AWS (Amazon Web Services) with Microsoft Windows 2012 R2 Standard edition with 64-bit architecture. I have opened ports 80, 443, 2399, 5003 and 16000 and yet I still can't get FMP open remote to communicate with the server. Would anyone have any idea what needs to be done?
  21. FMS 15 installation on AWS

    Of course. Thanks for reminding me.
  22. I am trying to test Cloudmail once again after having endlessly been given the run around by AWS. I am finally up and running with AWS but now when I try an open Cloudmail, I get an endless spinning ball and "Filemaker not responding". On another copy of Cloudmail that does open, I have tried inserting into the settings the data that came from AWS named "credentials.csv". I put "Smtp Username" into the field "Amazon Access key" (I discovered that "Smtp Username" and "Amazon Access key" are identical according to my IAM user data), and I put "Smtp Password" into the field "Amazon secret key". When I click on "Test" I get message below. Can you tell me what I am doing wrong?
  23. Cloudmail not reponding

    I have just created a new access key in AWS and input the data into CouldMail settings and here is the error message I got after clicking on "Test". Where do I go from here? As for the invalid settings in Couldmail making Filemaker crash, maybe you should have some time-out function in the opening script that lets you exit the without making Filemaker crash.
  24. Cloudmail not reponding

    Well now I can't even open the other versions of Cloudmail I have. They all make Filemaker crash with "Filemaker not responding"
  25. web direct in fms13

    I have a setup with fms13 running on a network that is using an Airport Extreme as router, wifi and firewall. It has worked perfectly for years. However it started playing up recently so I tried to setup a new configuration for the Airport Extreme where I opened all the ports that I thought needed to be open for FMS13 to work : 80, 443, 5003, 389. What is weird is that if I install the new setup in the Airport Extreme web direct does not work. I know that it actually functioning in FMS as I can test it locally. If I install the old setup in the Airport Extreme web direct does work, however after a few minutes the Airport Extreme becomes inaccessible, and I fear unreliable, as you can see in the attached image. Would someone know what I am missing here?

Important Information

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