Access Jet engine locks 2K page whenever the system locks a record.
My problem is the Jen Engine also locks other records together.
Is there anyway to work around this problem?
I just want to lock a particular record.
Hyong
Access Jet engine locks 2K page whenever the system locks a record.
My problem is the Jen Engine also locks other records together.
Is there anyway to work around this problem?
I just want to lock a particular record.
Hyong
No, there is no way to lock only a single record. By default the jet
engine locks the page at the time your application executes the Edit method
("pessimistic" locking). The record stays locked until the Update method
is completed. You can change the default to "optimistic" locking. Using
this option your record/page will not become locked until your application
executes the Update method. This should minimize the time the records are
locked.
The syntax of the command is recordset.lockedits = false
Kim Crompton
CompuHelp, Inc.
Quote:> Access Jet engine locks 2K page whenever the system locks a record.
> My problem is the Jen Engine also locks other records together.
> Is there anyway to work around this problem?
> I just want to lock a particular record.
> Hyong
> No, there is no way to lock only a single record. By default the jet
> engine locks the page at the time your application executes the Edit method
> ("pessimistic" locking). The record stays locked until the Update method
> is completed. You can change the default to "optimistic" locking. Using
> this option your record/page will not become locked until your application
> executes the Update method. This should minimize the time the records are
> locked.
> The syntax of the command is recordset.lockedits = false
> Kim Crompton
> CompuHelp, Inc.
> > Access Jet engine locks 2K page whenever the system locks a record.
> > My problem is the Jen Engine also locks other records together.
> > Is there anyway to work around this problem?
> > I just want to lock a particular record.
> > Hyong
> ---------------------------------------------------------------
> No, there is no way to lock only a single record. By default the jet
> engine locks the page at the time your application executes the Edit
> method ("pessimistic" locking). The record stays locked until the
> Update method is completed. You can change the default to
> "optimistic" locking. Using this option your record/page will not
> become locked until your application executes the Update method. This
> should minimize the time the records are locked.
> The syntax of the command is recordset.lockedits = false
> Kim Crompton
> CompuHelp, Inc.
I understand how optimistic locking works. However, if I use optimictic
locking, other issues will arise. If more than one users try to update at
a same time, how the system will handle such situation?
Someone claims extra flag field may be used to indicate whether a record
is locked by another user. However, the locked (flag field) will not be
unlocked if the application crashed.
Just increase a record size to fill just few records on one page. => Will
consume unnecessary HDD space.
Hyong
1. Jet Database Multiuser Considerations
Hello,
I have a client who has requirements as follows:
13 user network. Visual Basic front end to be used on the 13 clients.
The client has limited budget, so I would prefer to use Jet database on the
back end.
Client wishes to put in graphics of properties in the database (they are an
estate agent)
However, I have no experience of Jet in a multiuser context. My question
relates to performance.
Is 13 clients too many for a jet database?
If it is possible to get acceptable performance with Jet and 13 users what
is minimum hardware
requirement you would recommend for client and server in terms of ram/cpu.
Finally I recall that the latest version of Jet does support graphics in the
database, do these greatly affect
performance?
Thanks
Jonathan Black
2. SQLServer Agent startup in Win98
3. Copying records from jet database to a new jet database
4. Problem using DTS to transfer data from one database to another
5. Help: Jet 2.0 multiuser locking problem
7. VB 3.0 Pro/Jet 2.0 and heavy multiuser environment
8. Big PL/SQL Performance Problems
10. Jet/DAO and multiuser applications
12. VB/JET Multiuser questions
13. Multiuser issue