I've done lots of research on design over the past couple of years. One quote stands out, IMO especially for Fox developers:

“When data is the centerpiece of your object, you assign data to objects before saying what they do. Descriptions of data don’t tell you squat about your objects." http://www.theserviceside.net/articles/content/businessobjects/businessobjects.html

>From my perspective, the first is
>
>What do you want to do with the data you will collect -- is it a data feed to other systems, is it an application (like POS or inventory, etc.).
>
>Then, what data elements do you want (not structure) -- which ones you already have (legacy) and which ones you don't have (new).
>
>Then what functionality -- entry, search, etc.
>
>Then reporting.
>
>Then interfaces (inbound and outbound) -- type and data elements.
>
>The structure and layout is for you to determine in design. They may have some layout (forms) standards, but generally it is up to you to build.