Jesse Barnum

360Works
  • Content count

    789
  • Joined

  • Last visited

  • Days Won

    15

Jesse Barnum last won the day on November 14 2016

Jesse Barnum had the most liked content!

Community Reputation

47 Excellent

About Jesse Barnum

  • Rank
    member
  • Birthday

Profile Information

  • Gender
    Male
  • Location
    Atlanta, GA

Contact Methods

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

FIleMaker Profile

  • FM Application
    13 Advanced
  • Platform
    Mac OS X Yosemite
  • Skill Level
    Expert
  • Certification
    7
    8
    9
    10
    11
    12
    13
  • Membership
    TechNet
    FileMaker Business Alliance
    FIleMaker Platinum Member
  1. Please run a sync that demonstrates the problem, and then use the 'report a problem' link from the MirrorSync launch page in your browser. When you submit the problem report, be sure to include: The primary key of the record that has the problem The layout / table name for the record with the problem The value you expected versus the value that was actually written Copy and paste the text from this FMForum post so that whoever works on the issue has some background on it
  2. Hi Stephen - thanks for bringing this to my attention, this is due to changes made to support the setup process on FileMaker Cloud. If you're not using FileMaker Cloud, you can solve this problem by adding an 'exit script' step on line 59 of the MirrorSync setup script - right after the If[ Get(MultiUserState) = 2]. I'll work on a more permanent solution for an upcoming release of MirrorSync.
  3. Great post, Stephen! I've linked to it from our documentation: http://docs.360works.com/index.php/MirrorSync_advanced_topics#Can_I_build_my_own_front-end_for_the_download_link_URL_feature.3F
  4. I've never thought about that before. I'll add it to my feature request list, although it probably won't make it on the 'short' list :-)
  5. Hi Mark! You should set up a one-way sync with Oracle as the hub and FileMaker as the spoke. This will work just fine, except for the 'no deletions' part. By default, MirrorSync will always delete records in the spoke if they are deleted in the hub. The best (only) way to fix this is to sync using a privilege set in FileMaker that does not allow deletions.
  6. Answered via our support ticket, but for anybody else running into the same issue, the problem is probably that you're using JDBC (the default) instead of XML. JDBC is faster and generally more efficient, but to filter records with JDBC, you do it with a custom SQL qualifier in the same screen as the primary key pulldown menus. The MirrorSync customization script is totally ignored on the server when using JDBC (because JDBC cannot call scripts).
  7. OK, not sure why that happened but I'm glad you got it figured out
  8. No, sorry.
  9. MirrorSync communicates with Oracle on Oracle's standard port, 1521, so just make sure to set your firewall to allow access on port 1521 from whatever IP address MirrorSync is running on and you should be good.
  10. MirrorSync communicates with Oracle on Oracle's standard port, 1521, so just make sure to set your firewall to allow access on port 1521 from whatever IP address MirrorSync is running on and you should be good.
  11. P.S. - we just put out 3.15, found some problems with 3.14, be sure to get that.
  12. Yes, you can run the 3.14 update over the existing 3.0408 version, and existing offline files will be able to sync. However, I would recommend updating the MirrorSync script on the server and encouraging your users to get that version when it's convenient, as there have been some improvements in the MirrorSync script. Check the changelog for [items in square brackets] to see what is affected by the new script version.
  13. Cool! :-)
  14. 1) Which exact version of MirrorSync are you running? 2) In the MirrorSync configuration, do you have a foreign key configured from travels to cars? Actually, I just realized that neither of my questions matter, because we always do inserts for all tables, then updates for all tables, then deletes for all tables, so the delete will always happen last. You could edit the 'WillDelete' section for the hub, and in the travel table, you could update the related car record at that point. I don't know whether that will sync the car record back to the client though.