Thanks for responding,
When creating the tables I built the student information tbl first, and then built the Chapter 33 table after that. I didn't copy over the SSN# field, but made it within the Chapter 33 table itself. I did on the other hand copy the entire Chapter 33 table itself and duplicated it changed the name over to lets say Chapter 35 and then went in and deleted and added fields that I needed and didn't need. Each student can only have 1 Chapter 33 record, there will be multiple chapter 33 records but each one will be linked to only one student.
So the way i'm thinking of it in my brain and I hope this makes since is that when filling out a student information form, at the bottom of it there will be a button labeled Chapter 33, when you click on this button it will pull up the chapter 33 form take the SSN# from the student information form and look in the Chapter 33 table to see if a record has already been created if so then it will populate the information in the table to the form, if not then it will create a new record with the SSN# auto-filled from the student information form. I hope this clarifies what i'm trying to do and the issue I'm having.
--- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@...> wrote:
>
> jdrawwr (name?)
>
> I bet you created the Primary Key in the Student table, then did a copy and
> paste of the field into the other table. When you did that, the Unique Index
> property got copied with it, so when you try to create the relationship, you get
> 1-1.
>
> Will you have many records in Chapter 33 for each student? Or will you have
> many students that are under Chapter 33? You may be creating your relationship
> backwards.
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of jgrawwr
> Sent: Thursday, August 04, 2011 1:13 PM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] Relational Issues, Office 2007
>
> I just wanted to start by saying thank you to whom-ever might be able to help me
> out here. I'm a veteran and I work as a volunteer for a Veteran Services office
> for a small community college, being that I'm the most computer litterate person
> in the office I got tasked with building a database to store all of our veteran
> students information. Now I have taken a basic access class before but it was
> quite some time ago and I have largely forgot a lot about relationships and
> such. So on to my problem here, lol, the current issue that I'm having is that I
> have one table set up as a Student information table, this table houses all the
> students information relating to contact info, i'm wanting to make a data entry
> form with buttons at the bottom of the student information form saying something
> like Chapter 33 which is the Post 9/11 GI Bill for veteran students. By clicking
> this button it will take them to the form that I made from the Chapter 33 table.
> When I try to link the 2 tables together via a relationship it is giving me a
> one-to-one relationship, I'm not understanding why this is. I have the SSN# set
> as the primary key for the student information table, and i have tried using the
> student ID as a primary key for the chapter 33 table but still gives me a one to
> one relationship when i'm trying to link the SSN# fields. Pretty much what I'm
> wanting to do is as the data entry person is inputting the info on the student
> info form the click the chapter 33 button and it will pull up the chapter 33
> form searching by SSN# to see if an entry has already been made under that SSN#
> if so it will populate the fields/check boxs if not then it will create a new
> record for the chapter 33 form with the students name and SSN# populated from
> the student information form. I really hope this makes since I'm attaching a
> copy of my database with as far as I've got so far, and I guess we will see what
> happens. Sorry if this is confusing and if anyone needs more info please feel
> free to ask.
>
> I'm going to try and upload my database so those who are willing to help a
> completely lost and out of his element guy, can take a look, THANK YOU AGAIN!
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
Kamis, 04 Agustus 2011
Re: [MS_AccessPros] Relational Issues, Office 2007
__._,_.___
.
__,_._,___
Langganan:
Posting Komentar (Atom)
Tidak ada komentar:
Posting Komentar