Hi there,

I'm pretty new to relational databases, and databases in general, so bear with me.

I'm attempting to create a relational database that deals with the progression from prospective student to student.

I have one table for inquiries and another for enrollment. I'm currently running off a database that has no relational aspects so all inquiries have all the information and layout pages that enrollments get and I don't wish this to be so.

I've figured out how to do one to many relationships via a book, but it said one to one relationships are rare and therefore didn't go into detail on them.

I need a one to one because one inquiry cannot have more than one enrollment and one graduate profile, and one enrollment and one graduate profile can not have more than one inquiry.

Right now the database is set up in a one to many, how do I make it a one to one?

Any suggestions on the entire situation would be very much appreciated.

Thank you.

In a one to one realtionship, you would have youre recordID from enrollment go to a recordID field in inquiries.

Maybe you can post your file so that we can take a look and possibly make some suggestions on a better approach.

That is what I have so far but it shows the relationship as being a one to many.

Does this matter?

Additionally, in my inquiries database, at the top I have <> <> to display the first and last name of the prospective student.

Within Enrollments I would like to do the same thing however writing <> <> only produces that exact text (because, I am assuming, the fields aren't on that layout). I've placed the fields :Inquiry_First Name and :Inquiry_Surname on this layout but still can't get it to reference the fields. How can I go about doing this? I will need to be able to do this in order to supply the first and last name for form letters from within enrollments.

Will I need to create new name fields?

Figured out the field issue, but still wondering about the one to one relation...

A one to one relationship is nothing more than one table relating to another table on one key. If there were multiple entries in the second table with the same key then it becomes a one to many instead of a one to one.

Ok, that makes sense. Is there no way to prevent the other table from having more than one entry?