Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About folks

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
    Grantham's Landing, BC, Canada

Contact Methods

  • Website URL

Recent Profile Visitors

1,221 profile views
  1. EasySync Error 201

    "EasySync supports both "push-only" and "pull-only" tables. To indicate that a table is to be pushed from the mobile device, but not pulled, use an "ES_PUSH_" prefix for the table occurrence's name. To indicate that a table is to be pulled from the host, but not pushed from the mobile device, use an "ES_PULL_" prefix for the table occurrence's name." Try using all caps in your naming of these tables.
  2. I wonder if the storage for the images remains at the size of the original image taken by the iPad camera in spite of the replacement of that image by a much smaller thumbnail. From the isolated tests below ( with attached example db ) it looks like some of the storage in FMGo14 is recovered but not all, double what it should be. Also the overhead per container record appears to grow in a non linear manner on both FM OS X and FMGo14. Adding photos directly in FM on OS X appears to recover much of the storage that was not recovered in FMGo14. Unfortunately, only when another photo is added. In my solutions all photos are added in FMGo14 so storage size grows quite rapidly : ( The thumbnails are typically smaller than 1.1MB while the storage consumed for each image within the database appears to be average to 3.67 MB If this theory holds water how to I get the extra storage back as this is causing some real problems with sync times. calculation for container field // If the content of the container is an image shrink without distortion so max dimension is 1920 // if it is not an image then return self. This would apply to audio, files and music // if image has a largest dimension that is less than 1920 then just use image do not attempt to enlarge image. If ( PatternCount ( GetContainerAttribute ( Media;"filename" ) ; ".jpg" ) or PatternCount ( GetContainerAttribute ( Media;"filename" ) ; ".png" ) or PatternCount ( GetContainerAttribute ( Media;"filename" ) ; ".bmp" ) or PatternCount ( GetContainerAttribute ( Media;"filename" ) ; ".gif" ) or PatternCount ( GetContainerAttribute ( Media;"filename" ) ; ".tif" ) ; GetThumbnail ( Self ; If ( GetWidth ( Self ) < 1920 ; GetWidth ( Self ) ; 1920 ) ; If ( GetHeight ( Self ) < 1920 ; GetHeight ( Self ) ; 1920 ) ) ; Self ) Isolated Tests Created ContainerPhotoTest filemaker db with a single table and single field Media with GetThumbnail calculated result Move to iPhone 5s FMGo14 take photo ContainerPhotoTest 197 k with no photo ContainerPhotoTest 1.7MB with single photo Export Photo to desktop from Container Photo Size 467 KB But the database storage size has increased by 1.699 MB Add 8.6MB .jpg from the desktop in a second record ContainerPhotoTest 1.3 MB in size Drag photo to desktop from container Photo Size 623 KB ( 197 k + 467 k + 623 k ) = 1287 k 1,300 k - 1287 k = 13 k extra space used. What is happening here. So it looks like it works fine on OS X but perhaps not on iOS Try again with iPad Air 2 iOS • ContainerPhotoTest 1.3 MB in size • Take photo from FMGo14 Container • Take similar photo on iPad camera app • Photo Size 2.6 MB • ContainerPhotoTest 2.1MB in size • photo 800 k size increase • Photo size 467 k • Close and reopen FMGo14 • ContainerPhotoTest 2.1MB in size So it seems that in iOS some space is recovered on the photo re-size but not all. Final Test on OS X • Create new record and. • ContainerPhotoTest 2.1MB in size • drop similar photo 2.2 MB into container from desktop • ContainerPhotoTest still 2.1MB in size, no increase in size... • Quit and re open database • ContainerPhotoTest still 2.1MB in size • drag new photo to desktop 467k ( 197 k + 467 k + 623 k + 467 k ) = 1754 k 2,100 k - 1754 k = 345 k extra space used So it looks like something different is happening on OS X and FMGo I need to gather data including photos on FMGo and in practice as noted in the initial description of the production solution where no photos are added in OS X file size grows quite quickly. ContainerPhotoTest.fmp12
  3. Noticed that a record created by the Field db on iOS sync'd without problem to the Management db on the Mac... uhmmm... memories of a method used to solve the round trip problem. Perhaps that is what I am tripping over.
  4. Strangely, changing this one character not only fixes the SQL problem in table Form 3 but also enable the next table to sync also. So the problems illustrated in this example are now resolved. Thank you, amazing the difference that a single character can make.
  5. OK, Table named Form 3 has a field containing a non-conforming SQL Character, sigh changed from "Bank erosion|collapse" to: "Bank erosion collapse" So, Table Form 3 syncs correctly now, at least in this framework.
  6. Does not hang. Just keeps receiving segments, as if never reaching a termination condition. Happens with the FMSurvey sample database when setup for EasyDeploy.
  7. "Unable to connect to server"

    FMEasySync Demo FM_Surveys now working fine on the Server. There were two redirects on the router for the server, one for wifi and one for ethernet port. May have been a conflict there. Removed the wifi leaving only the ethernet reference. Re-selected the server file in the External Data Source, now visible, and it works : ) However still issues with my database Resolved: Error 5 was coming from OnRecordLoad: Check Layout ( Server )
 Disabled the if statement in the script for now and this issue goes away and we move on with the sync. Now works although it does complain: “The Pull request has failed. No Payload was received from the server.”
 All tables are push there is no pull table defined for FMEasySync in this solution … but that is another issue : )
  8. Yes.” You can combine the server and mobile components into a single database, and script it so that each instance is aware of whether it is serving as a host or client. Evidently this works fine. Just rename the two scripts in Mobile and Hosts that have the same name to "script name server" and "script name client". Be sure and do this when after Server scripts are imported but before Mobile scripts are imported, then for the Mobile scripts, to preserve script references correctly in other scripts. You can also see this done in FileMaker Magazines Tutorial and EasySync Recipe, where the changes are pre-done for you. Watch the

Important Information

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