>Any idea why it would work from the query analyzer and not the GUI?

Nope, but I never liked using the old Enterprise Manager either because it was quirkier than Query Analyzer. The old one used SQLDMO and was very slow. I don't know if the new SQL Management Studio still uses SQLDMO or something different, but I've gotten so used to typing T-SQL into Query Analyzer that that is the *only* way I like to do it. Then you know *exactly* what's being run against your tables, not what some GUI *thinks* it should run (along with any buggy stuff that gets thrown in there, as you evidently ran up against).

FWIW, I don't like the new Query windows, unless there's some way that I haven't discovered yet to get them to detach and not be tabbed windows, I like the way the old Query Analyzer worked. I hate when UI changes are sooooo different from what you've been used to doing for years and years.

~~Bonnie




>I trying to delete the row from the SQL Management studio. Cool... I used the delete command from the query analyzer and it worked without a problem. Thanks.
>
>Any idea why it would work from the query analyzer and not the GUI?
>
>>You're doing this from .NET? Care to post your code?
>>Why don't you just do it from Query Analyzer?
>>
>>~~Bonnie
>>
>>
>>
>>>Hi Kurt. No triggers at all on the table. No relations to other tables either. In fact, I'm trying to delete all of the records from the table so that I can add a relation.
>>>
>>>>Do you have a delete trigger on the table? It sounds like something is trying to update another table (possibly a log table) which is generating the error.
>>>>
>>>>Kurt
>>>>
>>>>>I'm trying to delete a row from a SQL Server table, but it is giving me an error below. Anyone know how to solve this?
>>>>>
>>>>>No Rows Deleted
>>>>>A problem occured attempting to delete row 1
>>>>>Error source: .NET SQLClient Data Provider
>>>>>Error Message: String or binary data would be truncated.
>>>>>The statement has been terminated.