[AccessD] PRB: Jet 4.0 Row-Level Locking Is Not AvailablewithDAO3.60

<<<
 Is checking this option actually ineffective?
>>>
Dan,

It's effective as far as I can understand.
KB article talks about DAO 3.6 being unable to "switch on/off" this feature.
But DAO 3.6 uses Jet Engine 4.0 when it's installed (as in your case).
So the option is effective IMO.
But I have no/can't find reliable tests.

Shamil

----- Original Message ----- 
From: "Dan Waters" <dwaters at usinternet.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Monday, October 17, 2005 12:11 AM
Subject: Re: [AccessD] PRB: Jet 4.0 Row-Level Locking Is Not
AvailablewithDAO3.60


> Shamil,
>
> My system is a straightforward FE/BE configuration where several FE's have
> links to the tables in the BE file.
>
> I've already set the FE & BE to record-level locking in Tools | Options |
> Advanced and the option 'Open Databases Using Record-Level Locking' is
> checked.  Is checking this option actually ineffective?
>
> Thanks,
> Dan
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
> Salakhetdinov
> Sent: Sunday, October 16, 2005 2:37 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] PRB: Jet 4.0 Row-Level Locking Is Not Available
> withDAO3.60
>
> John,
>
> It's a feature by design as stated here "Page-Level Locking vs.
Record-Level
> Locking":
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html
> /deovrpagelevellockingvsrecordlevellocking.asp
>
> Using DAO you cannot set database locking mode at row level - and article
> shows a workaround - you can use ADO to create ADO connection and set
> locking mode at row level. Then all the DAO code will work with row level
> mode until database is closed.
>
> Additionaly if you work with ADO only you can use "Jet OLEDB:Locking
> Granularity" property to have some tables opened with page-level locking
and
> others with row-level mode locking. This property is ignored unless the
Jet
> OLEDB:Database Locking Mode property is set to 1 (row-level locking).
There
> is no way to open a table/recordset with page level locking from DAO if
> database was first opened via ADO connection with row level locking.
>
> Looks clear how it should work from their description and sample code.
> But I must say I have never used it that way.
>
> Shamil
>
> ----- Original Message ----- 
> From: "John Colby" <jwcolby at ColbyConsulting.com>
> To: "'Access Developers discussion and problem solving'"
> <accessd at databaseadvisors.com>
> Sent: Sunday, October 16, 2005 9:21 PM
> Subject: Re: [AccessD] PRB: Jet 4.0 Row-Level Locking Is Not Available
with
> DAO3.60
>
>
> > Boy is THAT just confusing as hell.
> >
> > Does that mean that even if some users have DAO03.6 if SOMEONE (the
first
> > user?) opens it with row level locking all people, whether they have
> DAO3.6,
> > will use row level locking?
> >
> > Does it mean that even if you have 4.0, if the first user does NOT
> > specifically opens it using row level locking, then it opens without and
> no
> > one will be able to use row level locking?
> >
> > It DOES appear to say that if the first user in the DB does NOT use row
> > level locking then nobody can use it.
> >
> > Is it just me, or is that article less than helpful?
> >
> > John W. Colby
> > www.ColbyConsulting.com
> >
> > Contribute your unused CPU cycles to a good cause:
> > http://folding.stanford.edu/
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
> > Sent: Sunday, October 16, 2005 12:18 PM
> > To: AccessD
> > Subject: [AccessD] PRB: Jet 4.0 Row-Level Locking Is Not Available with
> > DAO3.60
> >
> >
> > I was reading the comments in the Access 12 blog, and came across this
> > information.  Does anyone have experience with this issue?  Under what
> > situations does it need to be dealt with?
> >
> > My system uses AXP in a split FE/BE configuration.
> >
> > http://support.microsoft.com/?id=306435
> >
> > Thanks,
> > Dan
> >
> > -- 
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
> > -- 
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com