It looks like the relationship in the database is reversed, which means that Primary Key table in the 1:1 association is the ForgetPassword table, that is why when you try to insert a record in the Account table, the server throws Foreign Key violation because in the ForgetPassword table there is no entity with the Id of the new Account entity.
If you revers the relationship in the SQL server, so the Account table to be the Primary Key table and then the association created in the Domain Model, everything should be fine. If you are in Model First scenario, you should first reverse the association in the Domain Model and then Upgrade the Database.
I hope that helps. If any other questions arise, do not hesitate to contact us again.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map