I know this gets asked a lot, but in my case, I feel like it shouldn't be an issue. My table has 2 foreign keys that allow for nulls, so I should be able to leave them blank, right?
My insert statement:
INSERT INTO Child (ChildID, FirstName, MiddleName, LastName, Gender, DOB)
VALUES (@ChildID, @FirstName, @MiddleName, @LastName, @Gender, @DOB)
I was hoping it would just leave the final 2 columns blank, for them to be filled out later, but all it does is give me an error.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK__Child__ChildGuar__2B3F6F97". The conflict occurred in database "ChildCare", table "dbo.ChildGuardian", column 'ChildGuardianID'.
I can re-work the database a little, if necessary.