There are a lot of extra things to prepare for if you want to make Server a permanent part of your work environment - things that aren't necessary if you don't use Server for development. It is true that Server won't hang when a script on local desktop goes loopy, but there have been cases where badly designed PSOS scripts have compromised and slowed Server too. If a file is being written to just at that critical moment - it's bad news, regardless. Incidentally, regarding your mention of crash protection/prevention, a power glitch will hit FMServer just the same as it will Desktop FMPAdvanced. I just worry that you might be scaring people (or making them feel less diligent or compliant or guilty) if they don't exclusively use Filemaker Server for development. On the other hand, I do occasionally use Server as a proofing tool, because it is necessary to prove a file works as expected when subsequently hosted. I never have to think about any potential "connection" concerns because my file is directly open In Filemaker. I know it's good to be educated and aware of the power of command line tools, but it's an extra thing to "do right". I never have to concern myself about IP addresses (if they change), or starting or stopping it, or computer sleeps. In fact you demonstrate some of the reasons why. I do have the Developer version at my ready here, and have used it from time to time, but consider it more trouble than it's worth. I prefer NOT to use Filemaker Server for development. One can also drown in sea of backup copies, and that's where I appreciate the ease with which local copies (when no longer of value), can be found and put in the trash.Īs for automatic backups, I have occasionally used Filemaker's buit in onTimer to create a schedule the simplest being a daily backup (if the file is left open) and a backup that runs on last window close. These Backup copies are readily available (easy to find), unlike Servers method of poking down through a complex web of paths to find the one you want. This the beauty of Filemaker's Save a Copy command. etc.Īs a matter of safety, before venturing out on any potentially risky script or crazy idea, I will test on a throw-away (scratch) file and prove something there (like a test-bed). By having many "versions" from frequent backups, I can step back in time and review or compare etc. When developing, I make frequent backups, not just for safety, but because it gives me a reversion trail should I go down a path which becomes over-complicated (or not a good move). If the Report doesn't show an absolutely clean result, I will use a recent Backup.īacking up in Filemaker Pro/Advanced could not be simpler. Should Filemaker crash - due to a power outage say, or a runaway script, and I need to force quit, I will always check the file using the Recover command. In fact the only time I tested and found a file corrupted, occurred with somebody else's file (and then I subsequently discovered that file was "faulty" when I first received it). Over all those years, I can hardly recall the rare occasion that Filemaker has crashed and if it has, the even more rare occasion the file has been corrupted. I've been developing in Filemaker for many years and for most of that time I have successfully and happily developed "locally". You can, however, with a few setup changes, make your local development machine use FileMaker Server in order to facilitate the ideal development environment. One possible issue is that FileMaker Server has be structured for a production environment and not for a development. If you're still developing locally with just a copy of FileMaker Pro Advanced then this video should be especially appealing.Īlso, if you're a developer on-the-go and you can't be tied to a local network, and may not have WAN access, then running a local FileMaker Server is a great solution. When FileMaker Server is within your development environment it provides crash protection, automated backups and other learning benefits which you simply won't get if you only upload your FileMaker file to a host and simply work that way. For FileMaker development, the solution to this problem is to always develop using FileMaker Server. It's like you're constantly looking over your shoulder waiting for the next FileMaker crash. Having that looming fear that your application or file may crash at any time is not a happy place. The worst feeling in the world, while developing, is one of instability. Unless you're in the process of learning a new environment, not that many developers are keen to spending a bunch of time re-configuring their development environment. Whether you're a hobbyist developer or a full-time professional, it's important to make sure your development environment is both stable and reliable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |