I'm starting a new job soon which will require me to use Access and I simply can't afford anything but a free way to get some kind of cursory understanding of it. Much appreciated.
Thanks sooo much. I am new to this and sometimes the simplest stuff needs to be spelled out at the outset. I apreciate the effort you have put in to help us out.
@yvonneka For purpose of creating a relationship, AutoNumber is considered a Number and is compatible with another Number column such as our foreign key. So the ID primary key fields are AutoNumber and the related BookID and AuthorID foreign keys in the Authored table are Number data types. AutoNumber as a data type is an Access thing... in other databases, our data type would simply be a number (or integer) and the generation of unique numbers would be result of a sequence or identity property.
@peaches4free I'm not sure I understand your question. Authored is a verb meaning "to be the author of". One of the ways this concept is taught is by using verbs and nouns. Nouns are our tables, while verbs are our relationships. So with a one to many relationship, we have two nouns, book and author, and one verb, the authored relationship. With a many to many relationship, the authored relationship also includes a junction table as part of the many to many relationship. Hope this helps.
@pmsocho You are right, duplicate values could be problem in the authored table. In the 5.3. video in this series, SQL to detect and delete duplicate values is discussed. Your approach is one solution and would create a composite primary key. Another solution might be to create a composite unique constraint. Arguments for any approach would vary based on how you use the columns, performance implications, and the database you are using. And yes, using Camtasia, Premiere, and After Effects.=)
Did you modify the SQL statement to get the result of 3 columns? thanks for the lesson. Without modifying the SQL, it would show extra columns, not only 3 columns as video
@MrWatandoost If you add an author field to the book table, you would have to add duplicate book records when a book had two or more authors. Duplicate data increases the odds of errors creeping into our database. We might also be tempted to add multiple author fields, such as fields named Author1, Author2, Author3, etc. However, this would make it more difficult when we want to query and count the number of authors, plus we would have problems if we didn't create enough new author fields.
Hello! I have a table with a primary key, and want to have it be the 'one' side of a one-to-many relationship with 3 other tables (so one primary key relates to the foreign keys of 3 other tables. When I try to view the subtables in the table format by clicking on the plus sign, nothing shows up. Is it possible to create multiple one-to-many relationships stemming from one primary key in a table? Thanks!
How do you prevent duplicate authorID-bookID entries. The model you are showing allow to add "author 1 - book 1" record and another "author 1 - book 1"record. Am I right or am I missing something. I would place 2 fields in Authored table - AuthorID and BookID and set the primary key on both of them. Would such approach be good or not? BTW, are you using Camtasia for recording :)
I'm stuck with sub datasheet view! for example, I've 3 separate tables. wanna relate them with one junction table. say, number 2 table has a common field ( could be described as the master field ), which is related to two other fields. one from number 1 table and another from number 3 table. after creating the relationship, when u press the " + " sign of the sub datasheet view, " insert sub datasheet " dialogue box appears! why so? I just wanna see related fields to that particular field. why that doesn't happen?
I have a problem, I have two tables, Table A has symptoms1, symptoms2, symptoms3, symptoms4, and Table B has a list of symptoms, I would like to make relationships to all other symptoms in Table A to Table B's Symptoms. How should I do it?????
This is quite possibly the best explanation I have seen on many to many relationships. This helped me a lot with creating a DVD collection database.
Do you still use that database?
The best and most uncomplicated explanation of many to many relationship in MS Access I found on the internet. Thank you so much!
I'm starting a new job soon which will require me to use Access and I simply can't afford anything but a free way to get some kind of cursory understanding of it. Much appreciated.
I was struggling with this for a few days and thanks to your video I was able to get what I needed done on time! Thank you!!!
Thanks sooo much. I am new to this and sometimes the simplest stuff needs to be spelled out at the outset. I apreciate the effort you have put in to help us out.
Perfect review, but probably also good for first-timer. Mostly, I was happily surprised by your author and book lists!
You are teaching me Access for free. Thanks mate!
nice work dear friend , i like
Thank u sir. This is one of the best explanations I have seen.
Fantastic explained. Helped me out a lot in my exam preparation
Perfect explanation . Thanks
excellent video and very helpful
@yvonneka For purpose of creating a relationship, AutoNumber is considered a Number and is compatible with another Number column such as our foreign key. So the ID primary key fields are AutoNumber and the related BookID and AuthorID foreign keys in the Authored table are Number data types. AutoNumber as a data type is an Access thing... in other databases, our data type would simply be a number (or integer) and the generation of unique numbers would be result of a sequence or identity property.
You are simply, the best!!
@peaches4free I'm not sure I understand your question. Authored is a verb meaning "to be the author of". One of the ways this concept is taught is by using verbs and nouns. Nouns are our tables, while verbs are our relationships. So with a one to many relationship, we have two nouns, book and author, and one verb, the authored relationship. With a many to many relationship, the authored relationship also includes a junction table as part of the many to many relationship. Hope this helps.
Thanks! You speak clearly, and this video was very helpful.
very informative video...
@pmsocho You are right, duplicate values could be problem in the authored table. In the 5.3. video in this series, SQL to detect and delete duplicate values is discussed. Your approach is one solution and would create a composite primary key. Another solution might be to create a composite unique constraint. Arguments for any approach would vary based on how you use the columns, performance implications, and the database you are using.
And yes, using Camtasia, Premiere, and After Effects.=)
Thanks very clear information. I appreciate the ZOOM!
again, a really good tutorial. this helped me with my assignment...muchos gracias!
very good job
thanks
very clear explanation. Thank you so much.
Very clear explanation. Thank you.
thank you very much ....
Beautiful tutorial. Nice book list :)
thank you man i take a 10 today .
Did you modify the SQL statement to get the result of 3 columns? thanks for the lesson. Without modifying the SQL, it would show extra columns, not only 3 columns as video
Thank you for the valuable information..
@MrWatandoost If you add an author field to the book table, you would have to add duplicate book records when a book had two or more authors. Duplicate data increases the odds of errors creeping into our database. We might also be tempted to add multiple author fields, such as fields named Author1, Author2, Author3, etc. However, this would make it more difficult when we want to query and count the number of authors, plus we would have problems if we didn't create enough new author fields.
@The4lbe Me 2...Thanks a lot...this is perfectly explained...
This is magic. Thank you!
10 points because you included Neal Stephenson.
thank you so much for this video !!!!!!!!!!
very helpful man!! thanks a lot!
thanks a lot
Hello! I have a table with a primary key, and want to have it be the 'one' side of a one-to-many relationship with 3 other tables (so one primary key relates to the foreign keys of 3 other tables. When I try to view the subtables in the table format by clicking on the plus sign, nothing shows up. Is it possible to create multiple one-to-many relationships stemming from one primary key in a table? Thanks!
How do you prevent duplicate authorID-bookID entries. The model you are showing allow to add "author 1 - book 1" record and another "author 1 - book 1"record.
Am I right or am I missing something.
I would place 2 fields in Authored table - AuthorID and BookID and set the primary key on both of them.
Would such approach be good or not?
BTW, are you using Camtasia for recording :)
I'm stuck with sub datasheet view! for example, I've 3 separate tables. wanna relate them with one junction table. say, number 2 table has a common field ( could be described as the master field ), which is related to two other fields. one from number 1 table and another from number 3 table. after creating the relationship, when u press the " + " sign of the sub datasheet view, " insert sub datasheet " dialogue box appears! why so? I just wanna see related fields to that particular field. why that doesn't happen?
Many thanks
Thx man !!!
so so helpful !!! thanks!!! :D
What do you mean when you call the new table "Authored"?
Thank you :)
Thank you, it was really helpful :)
thank you very much!
thanks man!
Thanks!
did we have to remove the association table in query design or not please hlp
I have a problem, I have two tables, Table A has symptoms1, symptoms2, symptoms3, symptoms4, and Table B has a list of symptoms, I would like to make relationships to all other symptoms in Table A to Table B's Symptoms. How should I do it?????
If I want to see books in a subdatasheet under their author and also authors who created abook in a subdatasheet under that book, how can I do that ?
@MrWatandoost search on Normalization
But why do you need a primary key in the relationship table?
thank you
thank you so much :D
I'm a beginner, where can i find complete tutorial for access 2010
sou kanw like
I need help with a database I'm designing is there someone I can email with my specific questions? That would be greatly appreciated :)
I say... Good show old chap! Jolly good of you; what?
Do multiple one-to-many relationships constitute a many-to-many? Anyone who knows why please explain, thanks!
why didn't you put both authorid and bookid in the new table as pk ?! when i do it it works !!
God! Not again :( What are those creepy sounds (like in 0:11)??? Such a great video I'm afraid to watch :) :(
Nevermind, the answer is obviously yes. Derp.
i feel sick becouse of moving camera all the time
Author wasnt a good idea, you are confusing me
He whistles too much when he talks.
To fast