[AccessD] Memo Locked - Apparently, but not that I can find!!!

Gustav Brock gustav at cactus.dk
Tue Mar 16 13:38:43 CST 2004


Hi David

I see - it may be a different issue than yours.

Yes, they are sharing two backend files on the server but locking only
occurs in one of the files. They don't run any Access apps on the
server.

/gustav


> Gustav....
> I would dearly love to report we had cracked it too.
> Mmmmm Interesting. 
> Your client may have a different issue.  Our database worked seamlessly in both A97 and A2K.  This problem only surfaced when we migrated into A2003.
> I've only seen it happen on the server, being used as a workstation also. (!)  (It has the reserves!)  We can run it as one shared copy from the server but I've not seen the problem in this way, as
> this database is mainly run on the server, so I've not been able to "make observations" on another PC.  This database almost never runs more than one copy at a time also, so concurrent locking
> shouldn't be an issue!.  As I said we do run concurrent A2003 databases, that are supposedly independent and distinct, (i.e. separate *.mdb file) however I am becoming interested whether this is
> true in A2003.  
> Are they running more than one database on the same server?
> Kind regards
> David Hingston MB ChB MBA
> Director
> Chequers Software Ltd
> Wellington, New Zealand.
> http://www.cheqsoft.com
> CheqSoft is associated with the Technology Entrepreneur Centre 

>   Thanks! Of course I hoped you had solved it but any info is useful.

>   My client is running A97 but I'm not sure that makes much of a
>   difference regarding this.
>   Tell me please, are you running the frontends as separate copies on the
>   workstations or are you sharing one copy on the server? I ask because
>   I've done the strange observation that when running a shared copy the
>   locking issue seems rare ... it doesn't make sense, I'll have to test
>   further here.

>   /gustav


>   > Dear Gustav
>   > We haven't cracked this one yet, it works most of the time and we've had other priorities.
>   > The refresh I referred to was a simple Shift-F9 on the form.  That proved to only sometimes work, as did repairing and or compacting only sometimes loosen the lock.  Only the memo fields lock.  
>   > It may be related to running a second A2003 database simultaneously, I am not sure.
>   > The best fix when all else fails seems to be shut down both databases and reopen.  (!)
>   > Lastly the problem seems to only occur when you have a record you want to urgently edit.   Actually that may be significant, it never is a new record, it is always an existing memo that is being
>   > edited and attempted to save.
>   > Our problem occurs running A2003 on a W2003 Server.
>   > I am sorry I am not able to be more helpful, at this juncture.
>   > Kind regards
>   > David Hingston MB ChB MBA
>   > Director
>   > Chequers Software Ltd
>   > Wellington, New Zealand.
>   > http://www.cheqsoft.com
>   > CheqSoft is associated with the Technology Entrepreneur Centre 


>   >   Hi David

>   >   I have a client fighting with this too.

>   >   Could you be a little more specific on your solution, please?
>   >   What are you refreshing and when?
>   >   Which of the advices mentioned in the forum discussion did you
>   >   implement?
>   >   As I read it, you update (save) the record at the BeforeUpdate event
>   >   of the memo field, then Cancel the update and refresh (requery?) the
>   >   record? 

>   >   /gustav


>   >   > Thanks John,
>   >   > That gave me enough to resolve it.
>   >   > Also Ref http://www.utteraccess.com/forums/access/access605200.html
>   >   > For anyone else simply doing a refresh unlocks it! 
>   >   > Kind Regards
>   >   > David

>   >   >   From: John W. Colby 
>   >   >   To: Access Developers discussion and problem solving 
>   >   >   Sent: Tuesday, February 10, 2004 2:38 AM
>   >   >   Subject: RE: [AccessD] Memo Locked - Apparently, but not that I can find!!!


>   >   >   Memo fields are treated differently than the rest of the fields in a record.
>   >   >   They are simply pointers out to a storage area where the actual memo is
>   >   >   stored.  Memos still have the "page locking" issue where if another user is
>   >   >   editing another memo that resides in the same physical page as your memo,
>   >   >   yours will be locked.

>   >   >   John W. Colby
>   >   >   www.ColbyConsulting.com

>   >   >   -----Original Message-----
>   >   >   From: accessd-bounces at databaseadvisors.com
>   >   >   [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Tortise
>   >   >   Sent: Monday, February 09, 2004 5:24 AM
>   >   >   To: Access Developers discussion and problem solving
>   >   >   Subject: [AccessD] Memo Locked - Apparently, but not that I can find!!!


>   >   >   Hi
>   >   >   I have a database which intermittently reports memo fields as being locked.
>   >   >   However they are not!  Editing the memo field it refuses to update on
>   >   >   attempted save, however text fields still update fine. (!)  It is a database
>   >   >   from A2K, that went to A97, back to A2k and now is running (converted) in
>   >   >   A2k3.  (Over time!)  Repair and compaction makes no difference, neither does
>   >   >   logging off and back on to the windows session.
>   >   >   The same behaviour is exhibited when editing the table as it is from a form.
>   >   >   I'm stumped!
>   >   >   As always any guidance is appreciated.
>   >   >   Kind Regards
>   >   >   David




More information about the AccessD mailing list