Recent content by drkhelmt

saleItemID would be the primary key saleItemID would be the primary key for the saleItem table. The field saleItem.saleID woudl be the foreign key to the sale table and saleItem.RegNo would be the foreign key to the stock table. Hope this clarifies.

it should It should. You can add a record to the table on the 1 side of a 1:M relationship, but it does not work vice versa. Hope this helps.

saleId probably shouldn't show in the stock table My thoughts on the design so far as the stock relating to the sale is that the stock should not relate to a sale, but rather the stockID should be in a saleItem table. Then the saleItem is related to the Sale. stock items can have multiple...

Well, I'd need to know the what the message about integrity says. I might check the datatypes behind the values. If they are not the same, you would get an error message. On the grander scheme, I would not use real data as a primary key. It appears that all is well except for the stock...

I would do something a little different Not to knock the previous reply or your own design, but I think I would approach this a little different tblContact pkcontactID (autonumber) firstname lastname nickname tblAddresss pkaddressID (autonumber) fkcontactID address city state zip... tblPhone...

Greetings y'all! I'm hoping someone can give me some advice on the best way to do this. I work at a fence manufacturing company that does custom jobs. A job can be built, but need additional work done by outside companies. So Company XYZ: Posts $x per linier foot if width is xx $y per...