[AccessD] Been Dazed and Confused for so long it's not true.

Jack,

So this clearly states that page level locking is used for 
Memo data.  It does not address whether memos from multiple 
records can be stored on the same page, though I am certain 
that it is.  It also plainly states that both ADO and DAO 
will use page level locking for memos.

Now the problem is that I have built a database to demo this 
stuff and it is NOT honoring the locks when updates are made 
to records with locks in place (records opened and an edit 
begun).

My recordsets attempting to edit a record already being 
edited is allowing the second edit, clear through to the 
data store.

John W. Colby
www.ColbyConsulting.com


Jack and Pat wrote:
> John,
> 
> I did some searching to see if I could find anything relevant. I did find
> this M$oft reference for what it's worth.
> http://msdn.microsoft.com/en-us/library/aa189633(office.10).aspx
> Jack
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Friday, May 30, 2008 2:29 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Been Dazed and Confused for so long it's not true.
> 
>  > If you're setting locks in ADO and editing the table in 
> DAO, you will find differences.
> 
> LOL.  Now wouldn't THAT be cute.  A lock is a lock except 
> when...
> 
> At the moment I am setting locks by editing in DAO and then 
> trying to count the locks using DAO.  That isn't working. 
> The DAO recordset coming along behind to test the locks is 
> not finding any locked records.
> 
> This whole subject is looking very messy.  Hey, does anyone 
> think we should just ignore unnecessary stuff like locks and 
> release a brand new version called 2007?
> 
> Or perhaps 2007 fixed this?
> 
> ROTFLMAOBTC BWAAAAHAAAAAHAAAA
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Charlotte Foust wrote:
>> John,
>>
>> If you're setting locks in ADO and editing the table in DAO, you will
>> find differences.  I ran into that a long time ago, but I've forgotten
>> the details.  I think that's why I was always so careful to limit myself
>> to working in one model or the other at a time.
>>
>> Charlotte Foust