A READER ASKS: Design Overload And Simplification

From Dwayne Wright - Certified FileMaker 9 Developer
WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright

A READER ASKS
Ok, so just tell me if this thinking is along the right track, cause I am second guessing myself. I was starting with Contacts -> Open House, but it's not really. Listing Agents have Properties, Properties have Open House's, Open Houses have Contacts,

Listing Agents -> Multiple Properties
Properties -> Multiple Open Houses
Open House's -> Multiple Contacts

And my head is blowing up trying to correlate how that would work into an initial interview where I take in their needs in a property.

I think I need to make a flow chart

-------
DWAYNE RESPONDS
A flowchart or even a documented needs analysis might definitely help. If you are wanting to explore coding, process and needs analysis, you might want to take a step back and spend a hour or so working on an independent prototype. Just create a new database with just the bare minimum code you need to prove the code design. Don't make it pretty and don't spend anytime outside of the barest skeleton. It should be extremely lean and still perform the action you need.

After testing it and happy with your results, you can then take a fresh look at the project you are working on and take another stab at it. Since you are using FileMaker Advanced, you can likely copy and paste the code from the prototype into your production database.

=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

© 2009 - Dwayne Wright - dwaynewright.com

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.

ADVERTISEMENT ==================
Help support this blog by considering a donating to its ongoing growth. For more details, please visit /donate.html