ISO FileMaker Magazine

No matter what FileMaker solution you're working on, you probably won't be leaving full admin access on the file. You don't want just anyone doing anything they want in the database - especially hacking up your beautifully crafted scripts.

So you'll be going through a process of re-logging into the database while both developing and testing. This can be accomplished using an easy or hard way. The harder way is to do what might come naturally, simply double-click the file after closing it down.

The problem is, any frequency of this activity and you'll quickly wish there was a better way. Fortunately, you can script most anything possible within FileMaker. This means you need a solid way of making this happen without making your solution insecure - which will certainly happen if you include vital credentials within the file itself.

You can always store a username/password combination in the file, while developing, and then remove them when you deploy, but this becomes an issue when you need to log in to make small fixes when the file is live - if you tend to do that type of thing.

The solution is to simply create an efficient method for switching accounts on the fly. That's exactly what this video has to offer!