when should I use "insert" in SQL?

[jhardman]

I know this question deals with a lot of SQL, but I am applying it to ASP, so I think this is the best place for it.

When I learned SQL, I saw the "insert" command as very useless. It tries to do so much that it often gives errors, since any part of it wrong generates an error. I always use "addnew" which allows you to add each entry on a new line. Although this may generate errors, you can easily handle the errors or use the error to troubleshoot. If youhandle the error well, you can still perform the "update", essentially posting most of the data, just missing the part that gives you errors. Does this make sense?

On this forum I have seen "insert" used by default in the majority of cases and many poor newbies pulling their hair out trying to figure out were the error is. I even saw one who was trying to use "insert" to change a single field in an existing record. It doesn't make sense to me to use "insert" in this way, but maybe I am missing something. Please explain to me, when would you use "insert" rather than "addNew" or any of the other SQL key words?

Jared

[sani723]

The AddNew method creates a new record for an updateable Recordset object.
After you call this method, the new record will be the current record.

while

The INSERT INTO statement is used to insert new rows into a table.