Thank you for your post.
Since a student can attend more than one college, and since one college can have more than one student, you therefore have a "many-to-many" relationship.
Therefore, create a third table that includes the StudentID and the CollegeID. This will allow you to link a class to a College and a Student. At any time, you can see students attended what college, what students took the same class, what students received passing grades, etc.
Does this help?
ok, so I have the portal working, but how can I filter it?? my table of colleges is over 5000 records and I want them to be able to get to ones that may match by name or part of a name. I have tried to follow directions on setting up a filter by adding a global match field and a match High and Match Low field calculated off the match field but i am not sure if it needs to be in it's own table or if it needs to be in the table with the college info or with the student info??? Thanks for all the help so far!!!!
While this can be done, the design can get extremely complex and cumbersome. You may want to think outside your current box and consider a different approach for helping your users find their desired list of colleges.
1) set up a search page for the user to enter search criteria for the colleges they want. Find request can handle "partial matching issues much easier than relationships.
2) once the user has produced the list of records they want, they could click an "add" button. The script performed by that button would then process your found set of colleges to populate your portal and return them to the original layout.
My apologies for a very general solution description, but if you can work out the details, it may give you what you want.