Re: best practices to support multi-users
From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 11/29/04
- Next message: Wart: "Re: Run query using VB6 and DAO"
- Previous message: Gijs Beukenoot: "Re: Multi-form Database Application"
- In reply to: PA: "best practices to support multi-users"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 28 Nov 2004 19:35:59 -0800
I spend a chapter or two about multi-user issues. Pessimistic locks are one
approach, but they require a thorough understanding of the underlying
mechanism. More commonly developers tend toward optimistic locking as it's
far more scalable. Each approach requires support by the application to
resolve the collisions. I discuss techniques to avoid collisions in the
first place...
see www.betav.com for details.
-- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ "PA" <prasad@epiance.com> wrote in message news:uMyk5260EHA.3840@tk2msftngp13.phx.gbl... > Does anybody know the best practices to support multi-users. In my case I > have a client application installed on several machines which access a sql > server database. > I tried the pessimistic locks. Then if somebody else tries when a data is > being edited the application hangs and after the connection object's > timeout > period it gives an error saying timeout expired. If I get a error I can > tell > the user that somebody else locked the data. Is this a standard method > everybody follows. I don't want to use any sqlserver locks or timeout > properties.I want to solve this problem using vb > > >
- Next message: Wart: "Re: Run query using VB6 and DAO"
- Previous message: Gijs Beukenoot: "Re: Multi-form Database Application"
- In reply to: PA: "best practices to support multi-users"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
