From Dwayne Wright PMP
Certified FileMaker Developer
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).
A READER ASKS
We are about to embark on a new FileMaker database tool that is going to be used by both web users (via IWP) and traditional FileMaker users. What would you recommend for this mixed bag of operation interfaces?
Great Questions! The first and foremost recommendation would be to design the database with the IWP users in mind first. That way you will reduce the amount of rework you might have to do for IWP incompatibilities.
Be sure to read up on IWP design if you are not familiar with it. I’m not sure where FileMaker puts all their IWP information these days but there is a 46 page guide on IWP design that FileMaker puts out. I think my copy came when I did an install of the FileMaker 10 Server Demo. It is a great guide!
After you have your FileMaker IWP deliverables for the project out of the way, you can look to see about your traditional FileMaker user deliverable needs. You might have to create a separate set of layouts and scripts for your regular users and you might not.
Also remember that FileMaker makes it very easy to see what scripts are IWP compatible by using the Show Compatibility area in the Edit Script dialog box.
© 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.