>Hello FoxPro Developers:
>
>I have two tables, OFFICES & OFFICE TITLES that I have joined together in a one to many relationship. OFFICE TITLES is the parent and OFFICES is the child. The logic behind the join is that I can have one office title (mayor for example)and many associated offices (example: mayor of Sacramento, Mayor of Detroit).....just in case that was important to reply to my question.
>
>
>The primary key I have set up in OFFICE TITLES is ntitle_id
>I set up an indexed key in OFFICES called ntitle_id.
>
>I have the indexed key in OFFICES set up as a "regular" indexed key.
>
>When I join the two tables, everything is fine in in my database designer. The join is set up as a one-to-many.
>
>* The problem is that I don't want to have my indexed key (ntitle_id) in the OFFICES table set up as a regular index. I want it to be a candidate key. I do not want to have duplicate values. From what I understand, a regular index is geared towards sorting those fields marked as regular before all other non-indexed fields. Also, regular indexes allow dupes.
>
>However, when I set up my child table (OFFICES) with a candidate key and join it to my parent table (OFFICE TITLES), FoxPro tells me it is a one-to-one join.
>
>Why is it doing that? I can't seem to change it to make it one to many. This is a problem for me in other tables as well, not just the table I am giving this example in.
>
>I would appreciate any insight into why I am not being successful in joining a primary key to a candidate key in a one to many join.
>Please keep in mind I am very new at this!!!!!
>
>Thank you for any assistance
>jcd

Primary and candidate keys are essentially the same in regard to duplicates: they both disallow them. So, you should have regular tag on many side just because you may have several record in Office table with the same 'ntitle_id' i.e. duplicate values. I don't quite understand what bothers you in regard to sorting: it should not be any problem here.