Decided to go all out and buy both the Mac and iOS versions and am getting down to building the form I need. I have a question on layouts though. The paper versions of the form that I use is based off of an excel spreadsheet as many “entries” have anywhere from 2 to 4 more pieces of data associated with them For example…
Under the camera Section there are 11 cameras listed.
Each camera has it’s own individual Part number, Quantity, Serial Number, and Equipment number.
– Obviously each of these would be their own separate field in the database (camera1SN, camera1EQ, etc)
Is there an easier way to group these into an almost spreadsheet like layout or am I forced into a list of 44 fields (some not always used) for just this one section of the form?
Attachments:
You must be
logged in to view attached files.
I think I’ve found my answer and it lies in sub-forms. Each “equipment” would have it’s own form which would show on the form as a horizontal representation of the data. It’ll mean a LOT of sub-forms, but in the end it’ll exactly what I want it to. :)
Hi Eric,
You would really only need two forms I think. One to hold the common Camera information, such as brand, camera type, etc. Then perhaps a separate form that has maybe a list of attribute types and values. It could be called Camera Attributes. A single Camera record would then link to a list of Camera Attribute records.
I’m not really sure that would be what you need because I don’t know everything about your existing system, but it could work perhaps.
If you turn on the “Show Inverse Relationship” function on the Link to Form field, then from any Camera Attribute record, you could see which cameras have those attributes.
You would probably also want a many-to-many Link Type because perhaps many cameras can share the same attributes, etc.
Thanks,
Brendan
.
