After change Delete Rule no Action to Cascade in My Table then save table FK Relationship Has Destryod automatically

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

Error was encored during save process some data object were not saved,

I have some serious issue in my ongoing project

i want to change in my db table(Sql2008R2)

I am trying to change in Key Relationship

Once I go through the change my table Relationship Constraint has destroyed Automatically

Step I explain you Here

Open Table Desing View

Open Relationship

Go to RelationShip and ChangeInsert Update Rule You can Notice that at bottom og pop up
Change Delete Rule No Action To Cascade

then After I am going to save if I select OK Ok Tab then my other relation ship contains Destroyed Automatically..

Plzzzz Help me out Its happen in My ongoing Projecr

Posted 12-Jan-15 0:33am

piyush solanki

Updated 12-Jan-15 0:34am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Phanindra261 · Answer 1 · 2015-01-12T03:15:00

The best option would be to drop the whole table and recreate it again. I would at least do that. If the table contains data put it in a temp table or even an excel(better safe than sorry). Now recreate the table with the new PK-FK Relationship. Better write scripts to do these things instead of using the design view. I have always found it to be more of a hassle than a useful thing. Anyway that was my point of view.