Search results

"The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship" That's a good thing, surely? It means I can't accidentally add the same item twice, to the same transaction. There's a ProductTransactionQuantity...

Some of you may be pleased to know that I've scrapped the child table and am just adding the Notes field, as is, to the junction table. If it helps anyone with their projects, this is how the database is structured wrt to the transactions: tblTransaction: { TransactionID (PK), TransactionDate...

I'm sorry everyone, but I feel I've slighty misled you. Firstly though, Stopher, thank you for that thorough explanation. It was less about saving space and more about keeping the database looking ‘tidy’. An immature oversight on my part, perhaps. I feel I've misled you because the...

Mr. Wells, I hope I'm not over-stepping but I think I love you. Thank you, thank you and thank you. That example database was perfect to help me understand not only how and where composite keys should (and more importantly should not) be used but also to help me understand what a Primary key is...

I finally tried testing this setup and I'm having some issues. I highlight all three fields in the Design view of the junction table and click the Primary Key button at the top. However, when I try to make a relationship between the Autonumber PK in the junction table and the Number PK in the...

Yes. Also, when you made any additions to the subform, it would update the table. Think of it like like grouping everything under the EmployeeID. It makes everything a lot easier.

The reason you'd relate tables together is because, when you have a main form for the Employees, the Payroll subform would need to know which Employee it was showing the details of, which would be done by relating it using the EmployeeID.

Thank you all for your replies, there is some fantastic discussion happening here. I ended up opting for Lagbolt/Mr Hartman's suggestion of an autonumber PK field, which links to the child table holding the notes. So the junction table ultimately now has 3 PK's: the 2 composites and the...

Hi, I hope you're well. I'm new to these forums and have an issue I hope you can help me with. Suppose you have 2 tables: tblEmployee (PK: EmployeeID) tblCustomer (PK: CustomerID) [Attached as zip file] Each employee can sell to many customers, each customer can purchase from many...