Josh Ormond

Moderators
  • Content count

    769
  • Joined

  • Last visited

  • Days Won

    21

Josh Ormond last won the day on May 20

Josh Ormond had the most liked content!

Community Reputation

87 Excellent

1 Follower

About Josh Ormond

  • Rank
    Director of Structural Entropy

Profile Information

  • Gender
    Male
  • Location
    Rochester, NY

Contact Methods

  • Website URL
    http://fmrift.wordpress.com
  • Skype
    jmormond

FIleMaker Profile

  • Profile Updated
    02/13/2016
  • FM Application
    16 Advance
  • Platform
    Cross Platform
  • Skill Level
    Expert
  • Membership
    TechNet
  • Title
    FileMaker Developer
  • Industry
    In-house

Recent Profile Visitors

14,699 profile views
  1. Try using Send Mail [ ] and just see if it works. This setup does work. So that can at least narrow down if the problem is the IMAP setup, the company account, or something else.
  2. What settings are you using? Should be: Gmail IMAP server address: imap.gmail.com Gmail IMAP user name: Your full Gmail address (e.g. "me@gmail.com") Gmail IMAP password: Your Gmail password ( app passwords require the spaces ) Note: Use an application-specific Gmail password if you have enabled 2-step authentication for Gmail. Gmail IMAP port: 993 Gmail IMAP TLS/SSL required: yes Important: For the Gmail IMAP settings to work in your email program, IMAP access must be enabled in Gmail on the web. For outgoing ( SMTP ): Gmail SMTP server address: smtp.gmail.com Gmail SMTP username: Your Gmail address (e.g. example@gmail.com) Gmail SMTP password: Your Gmail password ( app passwords require the spaces ) Gmail SMTP port (TLS): 587 Gmail SMTP port (SSL): 465 ( this is the one I used ) Gmail SMTP TLS/SSL required: yes
  3. I have it working using FM's native Send Mail [ ] step. You made sure you have the spaces in the from the app password included, correct? When you copy/paste, it doesn't pick up the spaces.
  4. I get exactly where you are at. My first dive into development was taking a system from FMP 4...and reworking the workflow, and adding a ton of features. With the capabilities of the modern versions of FM, there may be some opportunities to consolidate that down into a single UI file that reaches out to the other files and uses there data. Classic separation model use-case. Good luck with whatever you decide to do, and if you need tips or have questions. You know where to find us!! lol
  5. I spent 8 of my 10 years developing on Windows. So I am familiar with the pain. It may just be a difference in development. I almost never have the user have more than one window open. Unless it's a temporary, comparison driven task, or a customized dialog style window. You open up a lot of record locking issues with so many windows open. Other than that, the I close windows as the user moves to something else. There are some versions of FM that are just a performance hog. If the windows the user has open are from multiple files, FM is obliged to update the cache files on the local machine for as long as they are open. So for any records that FM has touched, or thought about, or needed to calculate something, it was downloaded to the local cache. When another user updates a record you have downloaded to the cache, FMS sends that record to the local cache. That can become a very chatty network, indeed!! In addition to the performance impact. Just some thoughts. Not dismissing that it is a big change. But it is one that most users have been asking for, for a long, long time.
  6. It may be less work to use a card window. I'm not exactly sure what you are trying to prevent, or not show.
  7. 1. Nothing has said XML and PHP CWP will be deprecated. At some point, I'm sure it will. But I don't foresee that anytime soon. The scale of use is simply too large. 2. There absolutely will likely be a licensing model for the REST API...FMI said that. In fact, the licensing model actually gives them incentive to keep the PHP CWP options ( and likely XML ) for a while. Since the licensing will likely affect all CWP connections. The hope is that it is an all on or all off model. But unlimited connections, or don't use it at all. A tiered model would just be more confusion to an already confusing licensing structure. 3. Running scripts is already on the product Roadmap. And they are heavily vested in the REST API, and each version will see more and more added to it.
  8. @IdealData - commercial hosting was not banned. It was simply restricted, for security reasons, to a single customer running on a single instance of FMS. No more multiple customers on one server license. @rwoods - Custom Web Publishing is still an open route for anonymous users. It works well, but WebDirect is simply not designed for that purpose, and put significantly more load on the server than CWP connections ( which are not persistent ).
  9. @adduartes - I think you are in the slim minority of fans of that 'feature'. I think, as time moves on, you won't miss it.
  10. I think to purchase concurrent licenses, you need to contact FM Sales.
  11. How many users?
  12. Consumer-grade Windows OS is lacking many of the optimizations that a true server has. Along with vast differences in prioritizing of services and processes, it is truly a different kind of beast. As Wim said, you may get it to work. You may get it to partially work. It may put your data at risk. Or it may fail completely. At that point, you have no support options with FMI. They won't help you until you get it onto a supported OS. Some important things to keep in mind should you continue down that route.
  13. The expression evaluation has only ever existing in the data viewer. The change in 16 was two-fold. Add in the auto-complete that has existed everywhere else in 15. Update the expression evaluation to allow for automatic evaluation. With the option to turn it off.
  14. They are being sent out in batches. Takes a few days. Globally, we are probably talking about millions of emails. I've heard several people say they haven't gotten theirs yet.
  15. There are 3 new extended privileges in 16 that are off by default. So you need to check them to make sure they are enabled, if needed. fmrest - Access via FileMaker Data API - FMS only fmextscriptaccess - Allow Apple events and ActiveX to perform FileMaker operations fmurlscript - Allow URLs to perform FileMaker scripts