Jump to content

dansmith65

Members
  • Content count

    898
  • Joined

  • Last visited

  • Days Won

    26

dansmith65 last won the day on September 12 2016

dansmith65 had the most liked content!

Community Reputation

83 Excellent

About dansmith65

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    B.C. Canada

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    Win 10

Recent Profile Visitors

11,393 profile views
  1. The password I defined in the Web Services Manager.fmp12 file's Operations > Edit Auth Info area contained special characters (like brackets). The FileMaker file worked fine with this password, but the wsdl failed to load in the browser saying it was unauthorized. This is likely because the password needs to be urlencoded in websvcmgr.php line 1217: $userPass .= ':' . $pass . "@";
  2. Quick Find Bug?

    Sorry, I had it backwards this whole time! Now I get why it seemed so strange; it seems strange to me too now. But then again, if you do a regular old find in that number field with the text ASDF3GHJK4QWERTY5, it will match a record with number 345. If you didn't want the text to cause a match in a regular find, you'd have to surround the value in quotes "ASDF3GHJK4QWERTY5", to make it match a phrase.
  3. Quick Find Bug?

    I think the reason it seems so strange is because number fields weren't meant to hold text and when you put text in them, they won't work like a text field. If you convert that field into a text field, your searches would work as you would expect them to.
  4. Quick Find Bug?

    Yes, I believe so. Since that field is defined as a number, it's index will only contain numbers. So the index for that value would contain: 301, which explains the match.
  5. Quick Find Bug?

    @Lee Smith I'm not sure; I'd like to know if it did, though. For the record, here's what I was referring to with the recovery option...
  6. Quick Find Bug?

    The advanced recovery options allow you to rebuild all field indexes, which is what you did on one field when you followed Lee's directions. You could test that. If that doesn't work; it's going to be tedious finding out which exact field is causing the problem. There isn't any easy way to resolve it; you'll have to just be methodical and work your way through it. Not sure which field it's matching against? disable quickfind one field at a time until it stops matching.
  7. Probably not; I hadn't thought of that. I usually don't run scheduled scripts as Administrator, so that hasn't come up. In that case, I would use a script to create the scheduled task. Here's an example: (the options would need to be changed to get it to run as Administrator) # https://technet.microsoft.com/en-us/library/jj649816(v=wps.630).aspx $Action = New-ScheduledTaskAction ` -Execute powershell.exe ` -Argument "-ExecutionPolicy Bypass -File C:\GetSSL.ps1" $Trigger = New-ScheduledTaskTrigger ` -DaysInterval 85 ` -At 1:00am $Settings = New-ScheduledTaskSettingsSet ` -AllowStartIfOnBatteries ` -DontStopIfGoingOnBatteries ` -ExecutionTimeLimit 00:05 ` -StartWhenAvailable $Principal = New-ScheduledTaskPrincipal ` -UserId $([System.Security.Principal.WindowsIdentity]::GetCurrent().Name) ` -LogonType S4U $Task = New-ScheduledTask -Action $Action -Trigger $Trigger -Settings $Settings -Principal $Principal ` -Description "TODO:explain what the task is for" Register-ScheduledTask -TaskName "TODO:task-name" -TaskPath "TODO:optional-folder-name" -InputObject $Task -Force
  8. Great job @Smef! I've been wanting to use Let's Encrypt, but didn't think it was compatible with FileMaker. When I schedule tasks on a FileMaker Server, I prefer to schedule them from within FileMaker Server itself. Since FMS can't run powershell scripts directly, I send this bash script the name of a powershell script to run and any parameters to send to the powershell script, if needed: :: file name: run_powershell_script.cmd :: Created by: Daniel Smith http://scr.im/fmconsulting :: change current directory to script location @PUSHD %~dp0 :: this is the old method that I disabled because of a bug in powershell.exe :: powershell.exe -file %* :: calling powershell.exe with -file option causes exceptions to NOT return an error code to this script :: I implemented a work-around linked to from here: http://stackoverflow.com/a/15779295 :: I am replacing " with ' because, when using the -command option, " does not group data into a single value :: FMS reads an errorlevel of 1 as "aborted by user" and only set's the log level to information, :: I am trapping for uncaught errors and returning 100 so the log level is set as error in FMS :: Since the actual error returned by the powershell script is lost, I'm sending it to a file. SET params=%* SET params=%params:"='% PowerShell.exe -ExecutionPolicy unrestricted -command "& {trap{Out-File -FilePath "..\Documents\run_powershell_script_errors.log" -Append -InputObject $_ ; exit 100} .\%params%}" @POPD EXIT /B %ERRORLEVEL%
  9. Quick Find Bug?

    Have you reviewed the layout to see which fields have QuickFind enabled? Is the serial number field defined as a number, or text field?
  10. Popover Buttons

    No You could have the second popover somewhere else and have a button on the first popover open the second popover by object name. If you did this, the first popover would close and the second one would open.
  11. You might want to check out https://www.geistinteractive.com/products/filemaker-drawing-tool-godraw/
  12. Payload Timing

    @bcooney I'm still not using EasySync in any client application's so I wouldn't have noticed this yet myself, but it does seem to be a limitation of the method used for syncing. I would suggest opening/closing a record instead of setting a field to control this. The problem with setting a field is when a client looses connection in the middle of a sync, or some other error occurs; that flag will remain set to "sync in progress". If you create a record (or table with one record) and open/close it when starting/completing syncing, then that lock will be more likely to clear on it's own. In the case of a client disconnect, for example, that record will be closed when the client disconnects (although I suppose it takes a bit for the connection to time out on the server). The only other possibility I can think of is to store the time the sync start, and the time it finishes, then add one more process at the end of a sync to see if any records were changed between those two times. Then you could run another sync to get the missing parent records. Note, you may need to resolve the following issue before this method works as expected: https://github.com/dansmith65/FileMaker-EasySync/issues/24
  13. "it appear that your connection is slow"

    Check the external file reference in your local file. There should only be one location listed and it should point to your hosted file. That's the most likely issue, if that's not causing it then I'm not sure what is.
  14. image sync speed improvement

    Thanks! I hadn't noticed that yet. I created an issue for it on GitHub.
  15. image sync speed improvement

    I stored segments the same way they were returned by the server, but I combined them, as necessary, in the "Loop over the records" section. So, I loop through all the segments if necessary, until "<record>" is found, adding the result to the $record variable... At least that's what I was trying to do, and I think it's working.
×

Important Information

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