Wim Decorte

  • Content count

  • Joined

  • Last visited

  • Days Won


Wim Decorte last won the day on March 19

Wim Decorte had the most liked content!

Community Reputation

413 Excellent


About Wim Decorte

  • Rank
  • Birthday 12/17/1968

Profile Information

  • Gender
  • Location

Contact Methods

  • Website URL

FIleMaker Profile

  • FM Application
    15 Advanced
  • Platform
    Cross Platform
  • Skill Level
  • Certification
  • Membership
    FileMaker Business Alliance
    FIleMaker Platinum Member
  • Title
    Sr. Technical Architect
  1. don't know that you can... but perhaps if you have a shadow field that uses GetAsCSS() on your original field, that could give you something to work with?
  2. this maybe: https://deskspace.com/ FM Studio never really produced very clean code, that is something to consider with any 'translation' layer. There is something to be said for writing the code from the ground up, using the native tools for the platform you want to go with (ASP.NET, PHP, Ruby,...)
  3. In DNS management. You keep mentioning "www." Your cert will be for "something.com" I'm assuming without the 'www', is that correct? Is it a wildcard cert? Do you want people to have a valid encrypted connection to the website www.something.com? Or are we talking about FMP connections inside the network to an FMS on a machine named someserver.something.com?
  4. That's where your process fails. You don't place the certificate into the 'correct' folder. You use the FMS admin console or the fmsadmin command line to import the certificate. That process takes are of putting the cert where it belongs. See instructions here: http://help.filemaker.com/app/answers/detail/a_id/14174 This sounds like you haven't configured the DNS properly. That's not strictly speaking part of the SSL config process which is why you won't find any instructions on it by searching for SSL help. There is also not a simple answer for this because it depends on your DNS management. If you have no idea how that works then your best bet is to find someone locally with DNS experience.
  5. Same answer. From his information I can't tell whether he is upgrading one copy or a whole set. Regardless; OP shows the same confusion as many others thinking that the new FLT licensing is the only available option, so broadening the conversation a bit is a good thing.
  6. No, you pointed out how to buy individual licenses. For more than one license but in the old concurrency model this is the link:
  7. Even for non-individual licenses you can still buy what is referred to as 'legacy licensing' based on concurrency. The new FLT licensing model is not mandatory.
  8. If your router allows, forward based on DNS names then you can just update your DNS and have all the rest fall into place. Otherwise; yes: you would have to update the port forwarding.
  9. Passing variables is something you do between scripts and has nothing to do with TOs so there is some really fundamental confusion in your mind that needs to be cleared up, otherwise you'll come up with answers that don't fit the question
  10. You can save yourself the pause by looping and waiting until the closing HTML tag appears, that way you'll know the page has loaded and you don't need to depend on an arbitrary pause.
  11. No, it is not a FM script command, it is an OS command. So you'd use it in a batch file or a VBscript or a PowerShell scriptl whatever IT is most comfortable with. In its simplest form (a batch or cmd file) it would look something like this: fmsadmin pause -y -u soliant -p testing vssadmin create shadow /For=D: fmsadmin resume -y -u soliant -p testing soliant / testing would be the FMS admin console credentials, the /For=D: specifies that the D drive should be snapshot.
  12. By design. It treats the "-" as a dash and will increment in the number that comes after.
  13. All or nothing. FMS is not VSS-aware so it is not safe to use unless the FM files are first stopped or paused; pausing can be done without disconnecting the clients, through the command line (fmsadmin pause) so it can certainly be automated. AV requirements can be met through scheduled scans that exclude the live files and by picking a schedule time that does not interfere with FMS own backups. The one thing that can not be on is 'on access' scanning. 3rd party backup that works at the file level can be made safe that way... provided that it does not run when FMS is doing its own backup. Mind the progressive backups if you are using those; you can't control when those run. You can control the interval but they will start when the db engine starts so the exact runtimes are unpredictable from one server reboot to the next.
  14. With "hosted' they probably mean that it is a virtual machine, not a physical server. Just ask; there is no shame in asking. Certainly do ask what they mean by 'hosted'. Is it a physical or virtual machine in the cloud? (Amazon AWS, Microsoft Azure,...?). If it is a cloud machine then all your client connections will become WAN instead of LAN and that could very well impact the user's experience. If you are worried about performance then make sure you have a performance baseline. Turn on the FMS stats.log on the 'logging' tab in the FMS admin console. It is off by default and tracks performance data across the 4 traditional bottlenecks (disk i/o, processor, network throughput and memory). Safe that file when you cut over to Windows. That file will give you something measurable to compare against when you do the same monitoring on the new server. Numbers don't lie. One thing that I would insist on: since you now have an 8-core machine, I would ask for the same on the new machine. That is a more important fight than the memory. The 16GB of RAM is more than enough. Don't kid yourself on the 'optimized for db performance'. The Mac Pro is no no way optimized as a database server. It's beefed up workstation with a waste of GPU power for its role as a server. Don't use this as an argument with IT, you'll lose all credit. If this is a virtual machine changes are that they are using a SAN as the disk sub-system and that it is driven off of SSDs anyway. But ask. Fitch's point about the backups is absolutely vital. FMS is not SQL Server and has different requirements for how backups are done. No 3rd party backup or Anit-virus shoud touch the live files or the backups while they are in progress. These days, Windows backups are usually done through the Windows Volume Snapshot Service and if it is a virtual machine then often through a snapshot of the whole virtual instance itself. When you restore from such a snapshot at a minimum: - the FM files will come back as 'improperly closed' because FMS did not have a chance to put the files in the proper state before the external backup was done - at worst the FM files will not open again because they will be damaged The Windows tools can be made safe by integrating them with the FMS admin command line to first pause the files and resume them afterwards. Not too difficult but requires some work with the IT department. I mentioned anit-virus: many IT departments will configure AV and insist that 'on-access' scanning is on. That can lead to all sorts of problem as the AV tries to scan the files every time FMS writes to them. That should be turned off. There is a FM knowledge base article that you can use here to give to IT.
  15. Reconsider that. There is a huge upshot in keeping field names 'standards-safe and use only a-z, A-Z, 0-9 and the underscore. The 'dot' is the delimiter between a table name and a field name in SQL for instance.