>>>Also...Naomi's suggestion about INSERT INTO...OUTPUT is a good one, especially if that INSERT is inserting multiple rows. The OUTPUT piece allows you to get at the specific value(s) as a result of the INSERT. It's like getting an "echo" of what the insert eventually did. It's a great feature.
>>
>>I read about the difference between @@IDENTITY and SCOPE_IDENTITY and aside from a "trigger" problem they work the same. And I don't have triggers.
>>
>>Until I can "see" that OUTPUT will help, I won't change code that works for 99.99% of the customers. Btw, This "Insert" only one row.
>>
>>Plus, I am using VFP Cursor Adapter and I don't know, yet, if OUTPUT can be applied to the class I created (based on CA).
>>
>>Thank you.
>
>You're choosing between 100% reliable code and 99% reliable. You already got cases where the code failed. Why would you want to keep that code?
Because.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham