I'm re-factoring some code and was wondering if it's a 100% safe assumption that after an INSERT whether to a table or view/cursor, that the record pointer is sitting on the new record ( on the very next line of code ), so that code issuing a REPLACE would already be positioned on your new record? I've seen code that issues GO -1 in a buffered view, but that's not great if you have more than 1 newly appended record in a view. So would it be safe instead to omit the go -1 and simply issue a REPLACE? Someone might ask why not just add the fields in the INSERT statement needed, but it's a case of the parent class adding the record initially, and the sub-class enhancing the data stored, so the sub-class needs to issue a REPLACE.
Thoughts? -Steve _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
