| Andrew J. Kelly 2005-12-17, 8:23 pm |
| Bob,
I don't know what the error is as I haven't seen that before. But I can
tell you that it is not wise to use EM or SSMS to edit or insert data. IN
my opinion the tool is and has never been robust enough for me to trust my
data integrity to and has too many quirks. I advise you to use QA or the
new Query Editor instead to manipulate the data. You will get a much better
feel for any issues that might arise as you will be more likely to see the
actual error message.
--
Andrew J. Kelly SQL MVP
"Bob" <bdufour@sgiims.com> wrote in message
news:edwnRczAGHA.3920@TK2MSFTNGP10.phx.gbl...
> Sometimes when I enter new data in a table row in the Management studio. I
> get an exclamation mark after I entered the data on a row and moved to the
> next row. The message I get when I hover over the exclamation mark icon at
> the left of the row says that the row was committed to the database but
> that I need to execute the query again because something happened when
> returning the values. If I click Execute again all is well. This behaviour
> never happened in sql server 2000 during my testing the tables. Can
> someone explain why this is happening?
> My tables execute insert triggers (for things like Createdby and Createdon
> fields) but nothing else. Its just straight data input with no frills yet
> this happens repeatedly and it gets me worried before I start writing
> code.
> I'll be writing stuff with Visual basic 2005 to call and execute stored
> procedures that will write data to the tables, is the behaviour described
> above something that would require special attention in the VB code in my
> apps?
>
> Any insigth would be realy appreciated.
>
> Bob
>
|