6 Replies Latest reply on Apr 18, 2011 11:46 AM by bumper






      I have a home office computer (mac) with filemaker pro 11 and two in field laptops (windows). After a lot of experimenting on what would be the best way to operate as far as web publishing and networks etc. I've decided that the best way forward is to put the filemaker pro 11 app on the field machines. I'm using a trial app to experiment and in the field it performs great and I'm not reliant on internet connection and navigation is much better. At the end of day I've been exporting the days records that were produced on field machine and importing them into home database on mac. This doesn't take to much as I have a home network that allows me to do everything easily. What I've found though is that I have to delete the tables that are on the field machines and copy the updated tables from home office computer back onto field machines. I can live with that but it has a couple minor hangups as far as printing and exact layouts from mac to windows etc. as well as several extra steps. It would be much easier if I could just set up an old fashioned sync with the 3 machines. Is there a way to do this? or is there a better way to do what I'm trying to do.

        • 1. Re: syncing

          By "delete tables" do you mean "delete files"? Don't see why you would want to delete tables, but replacing your old files with the updated copies would be necessary after importing the new records into your central file or group of files.

          You appear to lump together two different problems:

          1) Windows systems require a few more pixels of space for the same text than does a mac system. That can affect the look of some layouts when they are designed on a Mac and then opened in Windows. Once you tweak the layouts to fix this on the windows machine, you can copy the files back to the Mac system and they should then work fine on both platforms

          2) Synching your files. Whether you manually copy the files back across the network to your laptops or use software for this, you'll want to make sure that all files being copied are first closed before you copy them back to your laptops. If Filemaker is open, the copy can be corrupted.


          • 2. Re: syncing

            Yes , I ment delete the files.

            I think I understand What you are saying in regard to moving files between mac and windows. I will play with that a little to see if I can work that out.

            In regard to syncing files; I have been deleting files on windows machine or field machines after exporting daily records and then when all files are updated on mac I would save copy as / name it exact same name / and my home network lets me put it right on laptop where I put my filemaker files. If I understand you correctly this is incorrect as filemaker files on mac would still be open. Operating the laptop I can access closed files in mac through network and drag and drop them into laptop where I keep filemaker files, would this be preferable? 

            • 3. Re: syncing

              Save a copy will be ok. I'm referring to dragging files across the network manually or allowing some kind of "file synch" utility to compare file modification dates and copy files over if they have a newer date. If you use either of those two options, make sure that the files being copied are not open at the time they are copied.


              • 4. Re: syncing

                 If I can permanently fix layout glitch between mac layout and windows layout so I don't have to adjust layouts on field machines so they don't cut off the p's, g's y's etc. that will save me time. It sounds like I can.

                Am I correct in assuming that you think my current mode of operation is probably the best for what I'm trying to accomplish or do you see a better alternative.

                Thanks for the advice.

                • 5. Re: syncing

                  The best method is not to need to "synch" in the first place. "Synching" is one of those major ugly tangles that are best avoided by hosting the file via one means or another if at all possible.

                  In your case, the approach you are describing sounds reasonable if you never modify existing data in the same record on more than one machine at a time. Adding new records can be farely straightforward though care must be taken so that any auto-entered serial number fields include a value unique to the local machine to avoid two records created on two machines from getting the same exact ID value.

                  Where it really, really gets ugly, is if it's possible that one user could pull up a record on the home office machine and change "John Smith" to John Schmidt" while another user corrects the city field from "San Jos" to "San Jose" and a third user notices yet another discrepancy and makes yet a another change to the same record. Merging all those changes back into the record so that the correct changes are kept and the incorrect ones are discarded requires human monitering and intervention each time your system detects a difference between two copies of the same record when both have modification dates that date later than the last "synch".

                  • 6. Re: syncing

                    Sometimes is just easier to have duplicate layouts, one for the mac and the other for windows. Then you trap for the platform in you startup script, set it to a global field and set your scripts to go to the appropriate layout based on the platform.

                    A lot of electrons have been used over in the FM Go forum on the subject of syncing. There really isn't that much difference between syncing from a laptop and an iPad, so if you haven't already you might want to do a search over in that forum. 

                    There is a commercial product by WorldSync that will keep track of changes and do the heavy lifting for you, but I have not personally used it, but those who have swear by it.