OBP:
Unfortunately I do not understand the nuances between databases “cemetery” and “cemetery v0.1” in the example you submitted wherein the latter will enable photo sharing. Perhaps it is easier to describe our desires to you for your recommendations.
Our homeowners association need is: (1) store each individual home improvement request (complete with all ancillary data; i.e., date, description, approval, etc.), (2) scan a maximum of four .jpg documents (written and/or visual) submitted with each request, (3) query the database on any desired address for all the requests submitted for that residence---then report the attendant tabulated data and the corresponding visual entries for each request. By assigning an unique number for each improvement description, one could also query on specific improvements.
Lakewind Final (Lakewind ACC.7z) is the basic design thus far created. I allowed for four attachments to accompany each request improvement entry. The four attachments associated with the 1 December 2003 4301 RR data entries were arbitrarily numbered 10023-10026. I scanned the four actual documents that accompanied that particular request (only 10024.7z included), renamed them 10023-10026.jpg, and stored them in a separate (not database) file folder. The goal is to query any residence for all the data and documents (jpg) associated with each improvement request for that address.
Attached are the above zips using 7zFM (I trust these can be opened with any zip software). I would appreciate any suggestions, improvements, changes, etc. to achieve the desired results. I appreciate your kindness in pulling me through this dilemma.
Peace be with you and yours.
Bob Heinrichs
Austin, TX