[program-l] Re: dataBase Question
- From: "Mick Saltzman" <smickie@xxxxxxx>
- To: <program-l@xxxxxxxxxxxxx>
- Date: Sun, 8 Mar 2009 06:31:12 -0800
Hello George, The Books table does also have a primary key field called Book
Id. No I did not set the properties of the Author Id to allow duplicates or not
allow duplicates. I'm not sure why that would be the problem since I set the
properties of the One to many relationship for Referential integrity.
----- Original Message -----
From: George Bell
To: program-l@xxxxxxxxxxxxx
Sent: Saturday, March 07, 2009 11:26 AM
Subject: [program-l] Re: dataBase Question
Hi Mick,
I may be misunderstanding you here, but cannot have a one to many
Relationship where the Primary Key is the same. The Books table will have to
have its own unique Key which Access can create for you. By default, it used
to be simply a sequential number given to each record added.
Another thought. Is the Books table Author ID property set to "No
Duplicates" or "Allow Duplicates?
George.
From: program-l-bounce@xxxxxxxxxxxxx [mailto:program-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Mick Saltzman
Sent: 07 March 2009 03:35
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: dataBase Question
Hello George, I should explain that I came down with some kind of virus
myself, so it's been a while since I've done anything with my computer, so I'm
still catching up on my e-mail. I guess I should have went into more detail
about the database. With the One Author many books relationship, the Author Id
is the primary key in the Author table, and there is an Author Id field in the
Books table so I can complete the relationship. The other one to many
relationship is the one series Many Books with the Series Id field as the
primary key. As far as the error message it says basically can not save record
because the table series is related to it.
----- Original Message -----
From: George Bell
To: program-l@xxxxxxxxxxxxx
Sent: Thursday, March 05, 2009 2:12 AM
Subject: [program-l] Re: dataBase Question
Hi Mick,
The answer is in the primary key of the secondary (Author's Books) file.
(Which hopefully is the same as the Author details table) You perhaps have two
choices here. Create a secondary key in this file using perhaps the ISBN
number, which in turn would make each record unique. Or, you could allow
Access to create it's own key, which would essentially end up being a
sequential number.
You then need to create a Books sub-form to display books by a selected
author using the author file with a one to many relationship to the Books table.
I could explain this a lot better if I had Access 2003 available to me
right now, but some idiot (me!) has Access 2007 on his system, and somehow have
completely lost the plot with that version. I can get on one later if needs be.
George.
From: program-l-bounce@xxxxxxxxxxxxx
[mailto:program-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mick Saltzman
Sent: 05 March 2009 01:26
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] dataBase Question
Hello folks, I have a database question that might seem simple for most of
you, but I'm having a hard time figuring out what to do. I'm developing a
database for a friend. It contains information on books. My problem concerns
the 2 1 to many relationships. One Author many Books, one series many books. My
problem has to do with not binging able to enter data into my one author many
books form because Access won't let me save the record do to the fact that I
have the related series table. I do have a form, and sub form one series many
books, but my question is is there a way I could create a form that would allow
me to add a record that would include the authors, Books, and series. I am
wondering if I might have to change the relationships so that it uses only the
author table as the one part of the relationship on both relationships. I
should also mention I am using MS Access. Any help would be grate.
Thanks.
Mick
Other related posts:
