Wedding List

[kiteboarderni]

Hi guys, sorry this is a bit of a general question but im looking to create a basic database system to store products onto a list of future weddings.

Ive used access in school at a basic level but i cant really remember some of the basics!

I think I only need to use 2 tables for this, one for customer details along with the wedding info and one for the products. but im unsure as to get the relationships between them correctly and also if i will need another table to incorporate them!

I know this is a general question but i was unsure where i would post!

Thanks!

 

[boblarson]

Actually you should probably start off with the table structure and that would be posting in the Theory and practice of database design category.

And, you are likely going to need more than just two tables.

 

[PNGBill]

You should have at least three tables.

CouplesTable will hold the Bride and Groom's name and contact details, Best man etc.

WeddingTable will hold the actual Wedding Event details and one field will be the CouplesID - One to many in case they have a 2nd wedding!

ProductsTable will have a list of all items, gifts etc and one field will be the WeddingID. again, one to many as many products to one Wedding.

The Couples table could arguably be separated into two. BrideTable and GroomTable and these respectively linked to the WeddingTable to allow for future marriages by the Bride or Groom.

 

[kiteboarderni]

That makes more sense, how can the forms then be set up to allow for products to be added immediately after a new wedding instance has been created?

 

[PNGBill]

You shouldn't need a "Link" table. This is just a simple database even though the outcome may not be

Make your tables and then set the relationships.

Then make your Forms and Queries.

MainForm linked to WeddingTable and SubForm linked to ProductsTable with Properties set to allow Additions and Master Child link on WeddingID

This is the same principal as a sales invoice.

 

[boblarson]

You shouldn't need a "Link" table. This is just a simple database even though the outcome may not be

Make your tables and then set the relationships.

Then make your Forms and Queries.

MainForm linked to WeddingTable and SubForm linked to ProductsTable with Properties set to allow Additions and Master Child link on WeddingID

This is the same principal as a sales invoice.

Bill - how about taking this to the other post which was suggested by me earlier.

http://www.access-programmers.co.uk/forums/showthread.php?t=195189

 

[kiteboarderni]

What will the primary keys need to be in these tabels? will it just be the default autonumbers or will it need to have multiple keys depending on the table?

 

[boblarson]

What will the primary keys need to be in these tabels? will it just be the default autonumbers or will it need to have multiple keys depending on the table?

okay, since people keep answering in this thread, it is now locked. Please go use the other one people.