Josh Ormond

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Josh Ormond

  1. 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
  2. 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.
  3. It may be less work to use a card window. I'm not exactly sure what you are trying to prevent, or not show.
  4. 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.
  5. @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 ).
  6. @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.
  7. I think to purchase concurrent licenses, you need to contact FM Sales.
  8. How many users?
  9. 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.
  10. 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.
  11. 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.
  12. 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
  13. We have millions of records in multiple tables, being hammered on by 100 users... And processing 3-5k records at a time. Rarely takes longer than a few seconds. So I'm not sure what you mean. I'll agree, FM will let you build it so it's slow, but that doesn't mean it can't be faster. And as Jeremy said, performance increases are only beneficial to a point. There are so many variables that can make a process or script perform poorly, it's short-sighted to always blame FM for that. Sometimes, and probably more often than we would like to admit, it is the developer's fault.
  14. This is cute. And completely not the case in reality. I have seen so many "professionals" try to replicate work we have done in FileMaker, and they have been ridiculously unsuccessful. I don't disagree with some of what you mentioned. There are things I would love to see done differently. But that is also the case with every other programming environment I've dabbled in. To be fully honest, they all suck in their own way. Scale? What kind of scale are you referring to? I ask because I see 2 types of people that say this ( note I'm not implying anything about you specifically, just a general observation ). (1) People who built themselves into a corner, and just set up the data model the "wrong way". For them handling a few thousand records is painful. (2) People who want to process 20 million records in a second or two. Constantly. All day. Yeah, FileMaker isn't that tool. Relatively speaking, the number of companies needing to process millions of records a day is kind of small...compared to the companies that only need to handle a few thousand to a few million records a year. So for developers, this is one tool they have in their toolbelt. And they get paid well for the work they do. That's the definition of professional. Many developers I know have more work than they can handle right now. So it's hard to agree with you on that point.
  15. Setting up fmEasyWeb requires some web skills for sure. We Tim stopped working on it, for many reasons, it was limited to basically only showing a basic list or form view. If I recall correctly, you couldn't use it to fill out a form and submit. There were a lot of challenges with that setup, and with time, he may have been able to work out some of them.
  16. Why would you use an export of records? FMS has scheduled backups, FMP can use the "Save a copy..." script step.
  17. It's not a good idea to use the FMS as a workstation. FMS is doing a lot. And if something the user is doing causes the machine to bog down ( or worse crash ), you can potentially damage the files and have data loss. The FMS needs to be it's own separate box. With no one touching it or using it.
  18. It's hard to say without knowing/seeing more about the files you will be running. It's on the low end of meeting the system requirements. It may work if it's literally only 3 users, and that machine does nothing else other than run FMS. You may just have to test it. If the database is doing a lot of hard processes, it could crush that machine. If the database is very efficient and designed well, it should be fine. Just a lot of variables to figuring that out.
  19. This may be helpful. It is definitely possible to do what you are looking for. You may need to tweak this a bit. But definitely not too terribly difficult.
  20. External drives can work. You need to be very careful with them. Two potential issues, include slow throughput to the external drive causing issues with FMS and long pauses and disconnection. Both of which can cause strange behavior with FMS. The safest route, is to save to an internal drive, and then move it to an external drive or network drive.
  21. If you only have a few users hitting it, running FMS on a mac mini should be ok. Or on a Windows Server is great too if you have it available. You can have the backups go to a separate drive, yes. It's best if it is physically connected to the server. Internal is best. You don't want the backup to hang because it's copying the files to a network drive. Backup to a folder on the server, and then use another process to move the file to the network drive.
  22. A hosting service may not be a bad idea, precisely for that reason. Their connection is not slow. If you are going to be trying to get to the database from outside your LAN, hosting it on Pro is not a great idea. There are so many things that can happen that will cause issues with your database. Seriously consider how you host it. Cheap will often get you expensive problems later, especially if that data is valuable to your business.
  23. How are they going to be accessing the file? From inside or outside the office? Installing FileMaker Pro on the mini will require it's own separate license. And make sure that you follow all the best practices. It can be very easy to cause corruption in the database if you don't protect those files from being touched by other processes.
  24. Using Insert From URL may be using a cURL code and sending code inside of code. Which would blow up the syntax. One possibility.
  25. There must be some other transformation at play here. Are there dates involved anywhere? Are you 100% positive the data types are the same on both the local mobile file and on the server.