ernst

Members
  • Content count

    549
  • Joined

  • Last visited

Everything posted by ernst

  1. Probably some permission thing that got resolved by de-compressing the folder on the target machine.
  2. I've been using Dropbox for this and suppose Google Drive could also be used. The trick is to add the fmserver user to the privileges of each folder in the path to the final backup location. So if your Dropbox is located at /Users/Admin/Dropbox, you'll have to add the fmserver user with read/write permissions to the Users, Admin and Dropbox folder When defining the path in the 'Edit a schedule...' assistant, you'll have to enter something like filemac:/Macintosh HD/Users/admin/Dropbox/ Hope this helps!
  3. The installer will indeed not run correctly on Sierra, this appears to be due to the installation package not being compatible with the new installer application. One of the symptoms is that the serial number entry part of the installation script is skipped. Installing on a machine with an older MacOS and then dragging the application over to the machine running Sierra seems to work OK though, just like having Filemaker 11 installed before upgrading to Sierra.
  4. I had to migrate a Mac OS Mini Server running Mavericks 10.9.5 and Filemaker Server 13 to Filemaker Server 14.0.4 on El Capitan 10.11.6 today. It turned out to be an unpleasant and tiring operation, so I wrote a little manual that hopefully can help and save time for other people running into this situation. Some steps my not be necessary, but the following list describes the road I took, stumbling from one problem to the next. Rest assured that I left out a lot of swearing and three letter words that were also part of the process ;-) Greetings Ernst Backup your databases, stop and de-install any previous Filemaker Server version. The Filemaker 13 de-installer is located in the Extra’s folder on the Filemaker Server 14 installation disk image. Install El Capitan 10.11.6 + updates Do not install OS X server ( yet ) - see the notes at the end of this little manual. Remove the Java version installed with Mac OS - in my case Java 8 update 111. Steps from the Oracle website: In the Terminal window Copy and Paste the commands below: sudo rm -fr /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin sudo rm -fr /Library/PreferencePanes/JavaControlPanel.prefPane sudo rm -fr ~/Library/Application\ Support/Java Install the version required by the 14.0.4 Filemaker Installer: Java 8 update 60 before installing Filemaker. Installer is called: jre-8u60-macosx-x64.dmg After creating an Oracle account and logging in it can be downloaded from: http://www.oracle.com/technetwork/java/javase/downloads/ - Scroll all the way down and click Java Archives - Click Java SE 8 - Scroll down to Java SE Runtime Environment 8u60 - Click Accept License Agreement - Download jre-8u60-macosx-x64.dmg The Filemaker installer is supposed to install this Java version by itself, but in my case it appeared to contain the Java 8 update 31, causing a loop within the Filemaker installer, repeating the process of installing the wrong version. Get Filemaker fms_14.0.4.412.dmg. Use the full installer! In my case installing an earlier version and running the updater did not work - the updater to 14.0.4 hung during installation. Filemaker also advises this but unfortunately chose not to put the full installer on their website, so I had to Phone Filemaker support and supply the original sales contract number. After providing these details they mailed a link to the 14.0.4 full installer. Install fms_14.0.4.412.dmg Because I was planning a co-install with OS X Server App I used port 8080 and 8443 in stead of the standard 80 and 443 during the setup. Also I did not enable web publishing and ODBC/JDBC during installation because I desperately wanted to get the normal services working. Do not start Deployment when the installer finished but click Quit in the finishing dialog. Next step is to stop the server process via the terminal, as per Filemaker’s instruction: type or paste sudo launchctl stop com.filemaker.fms in a terminal window, enter and administrator password when required. In my case I had to restart the Mac and do this last step again after a fresh restart, before the FileMaker Server 14.0.4b Software Patch wanted to run without complaining about the Server being running. Run the FileMaker Server 14.0.4b Software Patch from http://help.filemaker.com/app/answers/detail/a_id/15575 Note that this installer will update your Java version to Java 8 update 66, in my case this went without any hiccups. Log in to the Admin console using the FMS 14 Admin Console.webloc shortcut placed on the Desktop by the installer. Alternatively point your browser to http://localhost:16001 and click Start Admin Console About co-installing with OS X Server version 5.2 I know the true purist warn against this; in this case the server is under a relatively light load, so performance does not seem to be an issue. Getting OS X Server to co-exist with FM Server proofed tricky though. Initially I had OS X Server app installed before trying the last FileMaker Server 14.0.4b Software Patch which caused the installer to hang again. So I had to command-drag to move the Server App from the Applications folder to the Desktop. After authenticating the Mac detects the removal and presumably stops and repatches all services involved. Then the FileMaker Server 14.0.4b Software Patch installed, after which I could put the OS X Server app back, re-login to server, re-enable the services, restart the Mac and finally login to the Filemaker Admin console. Next time I would leave the OS X Server installation as last step; possibly this will be less work.
  5. Hi Joost, How can a user paste a 0x0 character in a field, and is that somehow visible in a regular layout, or did you have to find out by using the 'Code ( text )' function? Ernst
  6. I noticed that portals with a scrollbar do not scroll when viewed on Filemaker Go, at least on my iPad they don't. Neither by touching the scrollbar to the right of the portal, nor by swiping up/down in the portal list. Anybody else noticed this? Best, Ernst
  7. Hi Lee, thanks for your reply. I checked the FMGo_Training_Tool file and learned that the portal scrollbar actually works, or more to the point, is tappable when zoomed in a lot. Still something FM should improve, and while they're at it also add swiping up & down, because that is the real way one is supposed to scroll on an iDevice. A great change for them to improve this, because they don't have to worry about backwards compatibility! I'll submit a feature request. I hope a lot of other users do this as well! Best, Ernst
  8. Hi Andy, Good morning from the other side of the planet! I've never seen this work. I got as far as delaying the closing of the database by entering a loop, but when exiting the loop the database would close after all. This might have changed with v7, so I'll try again, but I really doubt if FM changed this behaviour. Grtz, Ernst.
  9. Hi Terry, Welcome to the forum! To avoid the extra spaces when printing or previewing your document have a look at the the "Sliding/Printing" in the "Format" menu. This works very well when you print your document in list mode. If your document is printed from a layout with a portal you will need to re-write your printing script to jump to the database that your document-lines are in and then print them as list. Hope this helps, Ernst.
  10. Hi Paolo, >>the globals do not have values entered. does this matter? Actually it doesn't matter. And zero records found doesn't matter either. Just tried both. Sorry for this bad advise. Maybe a corrupted file? Ernst.
  11. Hey Paolo, Could it be that there are zero records found in one of the files? Do the globals have a value entered? Succes, Ernst.
  12. Hi /P If you script navigation between layouts (i.e. do NOT use the layout popup menu in the statusbar) then you could keep track of all the windows you visit by adding an extra script step to each navigation script that appends the new layout's number + a carriage return to a global text field. You het the number of the current layout with the Get(Current layoutnumber) function. The back button would then trigger a script that takes the last value of this list and does a Goto Layout (number by calculation) to take you back to the previously visted layout. The script would then have to remove the last entry from the list in the global field. And if you succeed in getting this to work then you could also start thinking about a 'Forward' button! Happy scripting from, Ernst.
  13. Hi Jana, I think your calculation will actually generate the text flag if the FIRST related record meets the criteria. To achieve your goal you can take (at least) two approaches: - either loop through all related records in the portal and as soon as you find one that does NOT meet the criteria RESET the flag, - or make a calculated field in the related file witha value of 1 (one) if the criteria for that record is met. Then make a calculation (either scripted or a calculation field) in your main file with the following definition: Case(Sum(PurchaseOrders::POStatusFlag) = Count(PurchaseOrders::SomeField), All outstanding PO's are completed") In other words: if the sum of all purchase orders which are completed equals the total of all related records then all outstanding PO's are completed. Hope this helps, Ernst
  14. Hi Wenzel, It sounds like your script emties the field(s) value. It should set the field(s) value to "No Form" Ernst
  15. Hi MJG, You could add field validation to your text field. If you want the user to enter data with 'all caps' then the calculation for the validation would be: Case(Exact(YourTextField, Upper(YourTextField)), 1 , 0 ) You could also use a calculated field, derived from the text input field. For 'all caps' the calculation would be: Upper(YourTextField) Regards, Ernst.
  16. Indexing speeds up the searching. So use it on fields that are regularly used in Find requests. Ernst
  17. Hello and welcome! You could define one table for each documenttype, each table consisting of just one field with an auto-entered serialnumber. The 'Create New' button would then have to create a new record in the table for the corresponding document type, read the serialnumber field and copy it to a serialnumber field of the main document table. Ernst.
  18. A way of doing something like this, is by having a separate Attend Gathering File, with a record for each possible Attend Gathering date (so four records for thursday....sunday). Then define a relation from the Attend Gathering field in this new file to the same field in the existing file. Finally list all folks for each day by using a portal displaying names from the existing file through this relation. Hope this helps... Ernst.
  19. Well, first this way of making serialnumbers is not really recomended because it uses 'meaningfull' serialnumbers. There are several discussion about the disadvantages of that on the forum. If, for some reason, you still want this then you could do something like: -define a calculated field that contains the first three characters from your serialnumber field. -define a 'self ' relation from that calculated field to itself -use something like Count(selfRelation::SomeField) + 1 to get the next serial value. But think twice before resorting to such a construction... Regards, Ernst
  20. Hi Jul, Either use a popup menu in stead of a popup list... ...or use Field validation to have Filemaker generate an alert when a user tries to enter a value that is not in the valuelist. Regards, Ernst.
  21. I think you can only script this if field "f1" is in your main file. Maybe you can put "f1" in a related file in such a wat that all records in the main file that use the same value of "f1" will actually share one related record with a certain value "f1". ?
  22. >> all of the fields with this value update automatically. DO you really mean all of the fields? Or all of the records where a certain field (let's call it 'X') has this value?
  23. >> I guess my problem is that I'm not sure if 'relationship::individualName' in my Substitute Function is >> actually changing with each Portal Row. You could check *that* by adding the 'relationship::individualName'-field temporarily to the portal in the layout.