Search Project Mgmt
Search FileMaker Blogs

Releasing An In House FileMaker Project Into The Wild Tips

From Dwayne Wright PMP
Certified FileMaker Developer

TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

Please Note: If you are viewing this page in a news feeder, the images may get munged up a bit or other formatting of the posting may fail. For the best experience, please visit the journal directly by clicking (here).

Seen your posts everywhere online and have been reading your blog. Wondered if you could offer me some tips or advice on the following:
I’ve been asked by my company to help redesign our current project management system that isn’t working too well. I’m self taught when it comes to filemaker and can do some basics but am stuck when it comes to some more advanced techniques. We would like to ideally hire outside for a developer or company to develop this new system for us however my boss just spent $15,000 on a system that our company isn’t using. I stand behind the new prototype I’ve come up with but I don’t know if I have the experience to build it myself. Even if I could get it built I worry about the next steps of putting it on a server version of filemaker and setting up user access rights etc..
Just wanted to get your thoughts and input. Appreciate your feedback J

Well if it helps (and it probably won't), your situation isn't that uncommon at all. I have had some success in these situations  and I'm happy to share some thoughts with you. However, there isn't any magic bullet and you are in for a bit of a grind.

1) Get the prototype on the FileMaker Server sooner than later.
Most professional FileMaker developers will agree that they prefer designing FileMaker files while they are on a FileMaker Server. This will help you with the apprehension you have about FileMaker Server.

2) Get buy off to have weekly code review meetings with key stakeholders
Gearing up to show the progress on a FileMaker project is a great way to empower it. You get regular feedback, you can show the organic evolution of the product and warm individuals up for the eventual switchover. In many cases, users will become eager for the release and you can gain critical momentum!

Another great thing about code review meetings, the stakeholders talk to each other! It is a great opportunity for them to not only talk about the database but about the business!

3) Add a feedback button on all screens!
Build a table that can store user feedback and have it capture data from within your FileMaker solution. The script can capture valued information like the layout, record, user name and such via Get functions. This gives you great design feedback and can be used as source material for each code review meeting.

More info about the author and FileMaker in general, contact me at

© 2011 - Dwayne Wright -

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.
Commenting Disabled
Due to a very high level of spam, I've disabled commenting.