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.

I need some troubleshooting ideas.

TIA

v/r
 

//SIGNED//

Stephen S. Wolfe, YA2, DAF
6th MDG Data Services Manager
6th MDG Information System Security Officer
Comm (813) 827-9994  DSN 651-9994


_______________________________________________
Post Messages to: ProFox@leafe.com
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.

Reply via email to