Wolfe, Stephen S YA-02 6 MDSS/SGSI wrote: > What are the 'valid' reasons for getting an update conflict when you are > using a remote view to a MSSQL table back end? The view carves out > selected records and computed values from a single table. Activity on > the table is typically very, very low. Like maybe a few transactions > per second would be considered a heated exchange. The norm is more like > a transaction per 10 - 15 seconds. >
The one that most often bites me is inadvertently changing a field value, and then trying to move the record pointer without first issuing an update (and, sometimes, a requery()) Good luck - those messages drive me mad. I often give up and just rewrite it as a SPT :( _______________________________________________ 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.
