Jump to content

Jesse Barnum

360Works
  • Content count

    903
  • Joined

  • Last visited

  • Days Won

    23

Jesse Barnum last won the day on August 28 2017

Jesse Barnum had the most liked content!

Community Reputation

51 Excellent

About Jesse Barnum

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    Atlanta, GA

Contact Methods

  • Website URL
    http://360works.com/

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    Sierra
  1. Keep record modification date

    This is impossible to do using a standard auto-entered modification timestamp, because every time you try to set the modification timestamp, that will cause it to change. It is possible to do this with calculation fields and some flag field to temporarily turn off the modification, as you're describing here, but we don't officially support it with MirrorSync. It might be possible, it might not.
  2. Customize New Database Version Available

    It's going to depend on the number of tables and fields - in my simple test script, it's line 1518
  3. Customize New Database Version Available

    Not easily, unfortunately. I realized this after I had released 4, and it was too late to change it at that point (because it would break existing MirrorSync customization scripts). You can change it by finding it in the main MirrorSync script, but you'll need to redo this change each time the MirrorSync script is copied and pasted. It's in the 'syncComplete' section of the script, which is the 8th section from the end of the script.
  4. Hi Doug - that is a lot of questions to type a reply to :-) Might be better to call us at 770-234-9293.
  5. MirrorSync can do what you want - you could have offline copies for your users to run their reports, and every time they run the sync script, it will push all changes to server and pull all changes from server. If the WPE makes changes, then presumably that will cause the modification timestamp to be updated, which will be picked up by MirrorSync on the next sync. From a pricing standpoint, the first device and first sync configuration are free. Assuming you only need one sync configuration, that means you'll just be paying for devices beyond the first. Prices start at $95/device for 1 and go as low as $40/device for 100, you can find out more by going to http://mirrorsync.com and clicking the 'pricing / buy' button. With that said, it's not how I would solve the problem. Can you switch to using xDBC instead of WPE? xDBC can do everything WPE does except for running FileMaker scripts. It's faster and more reliable. I would also update to FMS 16 and Windows Server 2012r2 or later, installed from scratch on a brand new box, to see if that helps with stability.
  6. Mirrorsync java error after power cut

    Have you tried 'fmsadmin restart adminserver' on the command line? If that's not working, and neither is 'fmsadmin close', then the only thing I know to do is reboot the box, hope that everything opens back up OK, and go to your backups if it doesn't.
  7. Mirrorsync java error after power cut

    Jack, I think you need to reboot the box. If that does not fix the problem, get the contents of your stderr file from /Library/360Works/Internal/logs and send that to support@360works.com
  8. I would still recommend upgrading; I don't remember all the things that have been fixed since then but the list is long. With that said, I don't know of a reason offhand why it wouldn't work on Windows.
  9. That's a very old version of our Email plug-in. High Sierra made changes that broke our old plug-ins. We've updated to accommodate for High Sierra; you need 3.06 or later (current version is 3.08).
  10. Filtering Changes

    Hey Jason! The customizations only need to be made on the server, you do not need to push out new mobile versions.
  11. Please try this dev version and let me know if the problem persists: http://s3-external-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 4.00591.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1517330280&Signature=DPRCUGe5bjSpmlMqoLY4EWb%2ByvY%3D
  12. New error message

    Please file a problem report using the hyperlink on the MirrorSync launch page. That will send us the complete server log file, which has more details that we'll need to troubleshoot this.
  13. Upgrade from 2.6 to 4.0

    Read the instructions that come with MirrorSync, there's a file called IMPORTANT 4.0 update notes.txt that comes with it. The format of the sync data has changed with each major version, so it will be necessary to essentially start over and redo the initial sync. The good news is that you can continue to use all the same sync layouts that you already have, so the configuration process shouldn't take long.
  14. Setup error ?

    Please try with this version to see if it fixes the problem. If it does not, then go to the MirrorSync launch page in your browser and click the 'send problem report and log files' link, so that we can review the MirrorSync log file. http://s3-external-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 4.0053.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1516204246&Signature=JEqxsZcdHtiscxdAO4X4u5Zjb%2BY%3D
  15. Help syncing FMServer --> SQL Server

    You should refer to the Microsoft Sequel Server JDBC driver documentation for details on this. We are using version MS-SQL-4.2.6420.100 of the JDBC driver. This does support integrated authentication. If you can connect with any other JDBC client application, you'll be able to connect with MirrorSync.
×

Important Information

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