This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at email@example.com
I have the table Gallery and the table Photo. Gallery can have more pohotos - of course. But I also want to gallery has associated one concrete picture as gallery title image. It would be logical to have it on Gallery table (Gallery -> Photo 1-to1 assoc.) which causes circular reference exception.
So I decided to reverse the association and have the key on table Photo. The bug is comming here, because when I want to have two references into the table Gallery, I need to rename the second reference column (first is Photo.GalleryId column, the second one is Photo.TitleForGalleryId). I use 'Column name' property on association, but designer is still operating with Photo.GalleryId column (he does not see I added Photo.TitleForGalleryId, and when I set Photo.TitleForGalleryId as nullable he still wants to set the nullable attribute to Photo.GalleryId (which is not nullable).
I hope I was clear in my text, if not, write me, I would make a test project.