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 kommentar(er)
