Search results

I like academic discussions. You come pretty close to how my tables have developed. I have a Customer table and a Site table (they have a many to many relationship) that contain most of the information in the report header. The body of the report comes from the individual report tables. I am...

I agree about normalization. I have been working on my table structure for three months now and have revised almost every table and the relationships at least once. My six reports are truely six very different reports. The only thing they all have in common is the name, location, and contact...

I have been pondering your response. I think I see a different way to solve my problem. I will try to explain. Yes, there are many customers. Each customer receives many reports but each report applies to only one customer. Customer CustomerID (pk) Report1 Report1ID (pk) CustomerID Report2...

My organization performs food inspections and sanitation inspection. anreports for multiple customers. We generate a report for each inspection. The heading and body of the reports are different but the final section, which contains electronic signitures is always identical. I use one-to-many...

Thank you for the reassuring feedback I am working my way through the Access 2997 Insideout book as I try to learn Access. Their join table example has no primary key. That said, they also recommend always having a primary key so adding one makes sense. I use the tbl convention you describe...

My question is similar to balfoura and I think your thread answers it, but I have to ask. I am still in the design phase, so I have yet to enter data to experiment. We provide inspection services to multiple customers at multiple sites. Multiple customers use the same site and multiple sites...