m_fitzgerald

View File Theme Editor At this point in time it is not possible, on Windows, to copy / paste from the Manage Themes dialog. This is a limitation of the FileMaker product on Windows but it means that Theme Editor is, presently, only useful on Mac OS X. Theme Editor allows you to control all of the elements of a theme. It is designed to overcome the limits placed on us by the built-in editing tools for themes. It is now possible, for instance, to do a bulk replace of a font-family. Allowing you to be positive that all objects will use the same fonts. It also opens up elements that could not be modified at all. You can control the size and placement of layout parts; the default chart theme; your color palette selections and the preview image. Having new layouts and parts added at the right size is a huge time-saver and a pleasure. Theme Editor allows you to store themes (it's a FileMaker database) and to generate Themes as required. If you have got the CSS licks to do so, you could use Theme Editor to create a theme from scratch. We hope that future version of FileMaker will include all of these abilities. Until then, you can enjoy using Theme Editor to manage this for you. Submitter m_fitzgerald Submitted 04/23/2018 Category Solutions FM Version 12

102 is the field missing error. It is being triggered. If your table_name is ES_Echanges then look at it. Print out the field list for both ES_Echanges tables and compare them.

EasySync is a great tool for managing changes. Small changes in data transfer easily. It's not really good at loading large data sets over the wire. Do the initial data load on the same network or preload the mobile version with the current data set before sending it to the moblie device. The closest thing you'll get to a schedule on fmGo is using Install OnTimer Script.

Yes, you are on the right track. If the records carry a department ID and you have some way of identifying users and linking them with department IDs you can do that. The general strategy is to put as little as possible onto the mobile device and transfer only what is required. You can control direction too, with push and pull prefixes on your table names. For instance, you orders and order_items should be PUSH only, unless you have some reason for everybody to see orders made by others. For assistance with SQL, Search online for FileMaker and executeSQL resources. SeedCode produced a nice helper tool and Beverley Voth wrote a manual that's available from the FileMaker Hacks site.

Are both tables exactly the same? Have you modified either table in some way?

If you're serious about trying another VM, try VirtualBox. If you're serious about trying another VM, try VirtualBox.

I've used the PHP simpleXML library as the basis of a simple tool for querying the XML DDR produced by FMPA . It's fairly functional and it has the benefit of being fast. Unlike other tools it doesn't require pre-processing of the XML prior to use. I've decided to publish it under the GNU AFFERO licence. If you're comfortable running a PHP script under localhost you can install it on your machine and make use of it. It's available from http://www.notyourhomework.net

It's a thing! Sync tools do not have paranormal psychological abilities. Its up to you to provide explicit instructions to the sync tool that control which records are available for syncing. In practice this is difficult because real world situations are complex. It's much easier to tell people to sync frequently, as the second, third, fourth, etc, sync clears up problems in the first, second, third, etc, sync.

EasySync returns the FileMaker Pro error number that caused the problem in the first place. Error 6 is file is read-only. I've found that it's helpful to send back more information. I've extended the error response. It sends back the last error and the content of variables $table and $field so that debugging problems is easier.

When EasySync encounters an error it passes the error back, which is great. When there is a 102 error it tells us that a field is missing. But from which table? It would help to know where we should start to look. In the Server Side scripts at about line 295 in "Process Payload from Client" I've modified the value of the $LastError variable returned for an 102 error to this: "Field " & $field_name & " is missing from table " & $table_name & ". FileMaker Error Code 102." It provides the user with better information. The result of the error is something like this: Field BranchName is missing from table ES_Memberships. FileMaker Error Code 102.

you can find all of Tim's work at his github repo: https://github.com/timdietrich

I've modified the Sync Check script on the Mobile side. I've set up variables that will split $UUIDs into chunks and loop through them. The script on the server side is unchanged. This is the code that is changed. It's not the entire script, just the significant bit that has changes. #Refresh sync status. Set Variable [ $$EasySync_Status; Value:"Performing sync check with server..." ] Refresh Window # #If the UUIDs exceed max size. Absolute max for a parameter value is 1MB. Suggested max is 0.5MB or slightly more than 13500 UUIDs Set Variable [ $slice_size; Value:13500 ] Set Variable [ $UUID_valuecount; Value:ValueCount ( $UUIDs ) ] Set Variable [ $n; Value:Ceiling ( $UUID_valuecount / $slice_size ) ] Set Variable [ $i; Value:0 ] # Loop Exit Loop If [ Let($i = $i+1; $i > $n) ] Set Variable [ $slice_positions; Value:Let( [ $slice_start = 1 + ( $i * $slice_size ) - $slice_size ; $slice_end = Min ($UUID_valuecount; $i * $slice_size )] ; "" ) ] Set Variable [ $UUID_slice; Value:MiddleValues ( $UUIDs ; $slice_start ; $slice_end ) ] #Send list to Server for analysis. Server will return the diff. If [ $$use_psos_during_sync_check ] #*** Remote Script: Sync Check Perform Script on Server [ “Sync Check” from file: “Hosted_Database”; Parameter: $$additional_sync_check_info & ¶ & $UUID_slice ] [ Wait for completion ] Set Variable [ $error; Value:Get ( LastError ) ] Else #*** Remote Script: Sync Check Perform Script [ “Sync Check” from file: “Hosted_Database”; Parameter: $$additional_sync_check_info & ¶ & $UUID_slice ] Set Variable [ $error; Value:Get ( LastError ) ] End If # #If there was an error... If [ $error ] Show Custom Dialog [ Title: "Sync Check Error"; Message: "The sync check's call to the server has failed."; Default Button: “OK”, Commit: “Yes” ] Exit Script [ ] End If # #Get the DIFF list. Set Variable [ $diff; Value:List ( $diff ; Get ( ScriptResult ) ) ] End Loop Close File [ “Hosted_Database” ] #

I'm getting 513 errors too. The length of my $UUIDs string is 2,343,143. Where did you find the PSOS parameter size limit? It's not in Tech Specs for v13? Tim, Assuming that there is a limit of 1MB for a parameter, that creates an upper limit of 27027 records that can be handled using the current code base. In my situation I have 60,000 records in the table but only one or two will need to be pushed to / pulled from the server. I am guessing that the reason that I'm getting such such large sets is that I haven't done the initial config properly. Otherwise, the mod timestamp would be used to isolate the few records that need to be passed, correct?

I've resolved the first problem. I modified the Sync Utilities script to include an extra option that I called "Configure". It sets both UTC time fields to the current UTC time and sets the last full sync field to get(currenttimestamp). We script the file copy and during the process we set a field value (user_config_required = 1). On start up, when user_config_required = 1 we run a subscript which now includes "perform script[ Sync Utilities; "configure"]. The times are set, and they are more recent than all the records. The user_config_required field is set to empty.