i have attchhed the error in screen shot..pl guide me wats wrong in that..
thanx..
seger 0 Newbie Poster
Lusiphur 185 Practically a Posting Shark Team Colleague Featured Poster
Sounds to me like someone changed one of the columns to require unique values and now, when you are attempting to delete individual rows you're running into a uniqueness error.
Technically, SQL should have prevented the process of setting a unique column while there were non-unique values within it but...
What I would recommend is that you change whichever column has been set to requiring unique values such that it no longer requires this... Delete or change all non-unique values such that all values in that column are unique and then re-create the column rule for uniqueness after that.
While the unique constraint is on the column it will give you that error every time you attempt to remove columns as you will be removing one non-unique row but there will still be other non-unique rows present.
At least that's what it looks like from that tiny screen shot you provided without any additional information to base my assumption on :twisted:
pritesh2010 30 Posting Whiz in Training
i have seen this problem but that error message can occur if there is a constraint which the deletion violates. A common one might be that a field is set to "NOT NULL".
or otherwise check is there any relation ship with other table....
i want to say Primary key and foreign key relationship .
joe28778 0 Newbie Poster
Completely agree with Permalink. the reason why you could receive such error is when you've multiple entries with the same values and you are try to remove only one of them. as per his suggestion backup your information first and try to delete all records linked to it. you need to do it for all entries in that table, then enforce the uniqueness constraint on your entries after you have resolved the problem.
Lusiphur 185 Practically a Posting Shark Team Colleague Featured Poster
Completely agree with Permalink.
Names are to the left, permalink is a link to get the direct link to the post in question :) But thanks for the agreement.
nehacct 0 Newbie Poster
I think, this problem occurs due to the relationship between tables. You should first remove this relationship and then try. I think it should work.
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.