Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!
  1.   Become a Supporter    ::   Make a Contribution   
    Target (Recurring Monthly): $200 :: Achieved: $98

Could not Save;Currently locked by another user

Discussion in 'Information Technology' started by MartyO, Jul 28, 2006.

  1. MartyO

    MartyO
    Expand Collapse
    Guest

    We have MS Access 2003, SP1 and SP2 users, user FE's linked to BE on a
    server.

    Two users accessing the same record, we're getting "Could not Save;Currenlty
    locked by another user", instead of getting the friendly message that lets
    you handle record locking gracefully. It's a memo field that they are
    editing.

    The strangest thing is that we are only getting this message on one
    particular record. I've rebuilt the form, the table, deleted the record and
    copied it back in.

    Any ideas?
    Thanks in advance for your help.
    Marty
     
  2. Loading...

    Similar Threads Forum Date
    India Raid finds several schools locked Breaking News Sep 23, 2012
    Sikh News Jagdish Tytler's UK visit blocked over 1984 Sikh Massacre Breaking News Nov 6, 2009

  3. Jerry Whittle

    Jerry Whittle
    Expand Collapse
    Guest

    Open the database and go to Tools, Options, and Advanced Tab. Check that the
    Default Open mode is Shared and the Default Record Locking is Edited Record.
    (While you are in the Options area, go over to the General tab and turn off
    Compact on Close and Name AutoCorrect. Trust me on this.)

    Possibly it's a corruption issue. Memo fields corrupt too easily. Have you
    tried a compact and repair?

    Tony Toews has an excellent web page on database corruption.
    http://www.granite.ab.ca/access/corruptmdbs.htm

    Allen Brown also has excellent info on corruption.
    http://allenbrowne.com/ser-47.html

    I have a white paper in a Word document named Fix Corrupt Access Database
    towards the bottom this page:
    http://www.rogersaccesslibrary.com/OtherLibraries.asp
    --
    Jerry Whittle
    Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


    "MartyO" wrote:

    > We have MS Access 2003, SP1 and SP2 users, user FE's linked to BE on a
    > server.
    >
    > Two users accessing the same record, we're getting "Could not Save;Currenlty
    > locked by another user", instead of getting the friendly message that lets
    > you handle record locking gracefully. It's a memo field that they are
    > editing.
    >
    > The strangest thing is that we are only getting this message on one
    > particular record. I've rebuilt the form, the table, deleted the record and
    > copied it back in.
    >
    > Any ideas?
    > Thanks in advance for your help.
    > Marty
     
  4. MartyO

    MartyO
    Expand Collapse
    Guest

    Thanks Jerry. These are good articles. I've tried almost all of the
    suggestions but nothing is working so far. I'll keep at it.

    Question: If I converted my backend to SQL Server, would that be a step in
    the right direction in taking care of record locking errors, and memo field
    woas?

    Thanks!
    marty

    "Jerry Whittle" wrote:

    > Open the database and go to Tools, Options, and Advanced Tab. Check that the
    > Default Open mode is Shared and the Default Record Locking is Edited Record.
    > (While you are in the Options area, go over to the General tab and turn off
    > Compact on Close and Name AutoCorrect. Trust me on this.)
    >
    > Possibly it's a corruption issue. Memo fields corrupt too easily. Have you
    > tried a compact and repair?
    >
    > Tony Toews has an excellent web page on database corruption.
    > http://www.granite.ab.ca/access/corruptmdbs.htm
    >
    > Allen Brown also has excellent info on corruption.
    > http://allenbrowne.com/ser-47.html
    >
    > I have a white paper in a Word document named Fix Corrupt Access Database
    > towards the bottom this page:
    > http://www.rogersaccesslibrary.com/OtherLibraries.asp
    > --
    > Jerry Whittle
    > Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
    >
    >
    > "MartyO" wrote:
    >
    > > We have MS Access 2003, SP1 and SP2 users, user FE's linked to BE on a
    > > server.
    > >
    > > Two users accessing the same record, we're getting "Could not Save;Currenlty
    > > locked by another user", instead of getting the friendly message that lets
    > > you handle record locking gracefully. It's a memo field that they are
    > > editing.
    > >
    > > The strangest thing is that we are only getting this message on one
    > > particular record. I've rebuilt the form, the table, deleted the record and
    > > copied it back in.
    > >
    > > Any ideas?
    > > Thanks in advance for your help.
    > > Marty
     
  5. Pieter Wijnen

    Pieter Wijnen
    Expand Collapse
    Guest

    yes & no
    Part of the problem is that Access & MS SQL use page locking instead of
    record (or field locking!) that Oracle does
    which means you're normally hogging (locking) more data than you think.
    the easist way out AFAIK is to use a timer to save/discard the data if the
    user has hogged it to long

    NMH

    Pieter

    "MartyO" <MartyO@discussions.microsoft.com> wrote in message
    news:B1513B75-38A8-4138-B286-BAF1A5DC9598@microsoft.com...
    > Thanks Jerry. These are good articles. I've tried almost all of the
    > suggestions but nothing is working so far. I'll keep at it.
    >
    > Question: If I converted my backend to SQL Server, would that be a step
    > in
    > the right direction in taking care of record locking errors, and memo
    > field
    > woas?
    >
    > Thanks!
    > marty
    >
    > "Jerry Whittle" wrote:
    >
    >> Open the database and go to Tools, Options, and Advanced Tab. Check that
    >> the
    >> Default Open mode is Shared and the Default Record Locking is Edited
    >> Record.
    >> (While you are in the Options area, go over to the General tab and turn
    >> off
    >> Compact on Close and Name AutoCorrect. Trust me on this.)
    >>
    >> Possibly it's a corruption issue. Memo fields corrupt too easily. Have
    >> you
    >> tried a compact and repair?
    >>
    >> Tony Toews has an excellent web page on database corruption.
    >> http://www.granite.ab.ca/access/corruptmdbs.htm
    >>
    >> Allen Brown also has excellent info on corruption.
    >> http://allenbrowne.com/ser-47.html
    >>
    >> I have a white paper in a Word document named Fix Corrupt Access Database
    >> towards the bottom this page:
    >> http://www.rogersaccesslibrary.com/OtherLibraries.asp
    >> --
    >> Jerry Whittle
    >> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
    >>
    >>
    >> "MartyO" wrote:
    >>
    >> > We have MS Access 2003, SP1 and SP2 users, user FE's linked to BE on a
    >> > server.
    >> >
    >> > Two users accessing the same record, we're getting "Could not
    >> > Save;Currenlty
    >> > locked by another user", instead of getting the friendly message that
    >> > lets
    >> > you handle record locking gracefully. It's a memo field that they are
    >> > editing.
    >> >
    >> > The strangest thing is that we are only getting this message on one
    >> > particular record. I've rebuilt the form, the table, deleted the
    >> > record and
    >> > copied it back in.
    >> >
    >> > Any ideas?
    >> > Thanks in advance for your help.
    >> > Marty
     
  6. Pieter Wijnen

    Pieter Wijnen
    Expand Collapse
    Guest

    yes & no
    Part of the problem is that Access & MS SQL use page locking instead of
    record (or field locking!) that Oracle does
    which means you're normally hogging (locking) more data than you think.
    the easist way out AFAIK is to use a timer to save/discard the data if the
    user has hogged it to long

    NMH

    Pieter

    "MartyO" <MartyO@discussions.microsoft.com> wrote in message
    news:B1513B75-38A8-4138-B286-BAF1A5DC9598@microsoft.com...
    > Thanks Jerry. These are good articles. I've tried almost all of the
    > suggestions but nothing is working so far. I'll keep at it.
    >
    > Question: If I converted my backend to SQL Server, would that be a step
    > in
    > the right direction in taking care of record locking errors, and memo
    > field
    > woas?
    >
    > Thanks!
    > marty
    >
    > "Jerry Whittle" wrote:
    >
    >> Open the database and go to Tools, Options, and Advanced Tab. Check that
    >> the
    >> Default Open mode is Shared and the Default Record Locking is Edited
    >> Record.
    >> (While you are in the Options area, go over to the General tab and turn
    >> off
    >> Compact on Close and Name AutoCorrect. Trust me on this.)
    >>
    >> Possibly it's a corruption issue. Memo fields corrupt too easily. Have
    >> you
    >> tried a compact and repair?
    >>
    >> Tony Toews has an excellent web page on database corruption.
    >> http://www.granite.ab.ca/access/corruptmdbs.htm
    >>
    >> Allen Brown also has excellent info on corruption.
    >> http://allenbrowne.com/ser-47.html
    >>
    >> I have a white paper in a Word document named Fix Corrupt Access Database
    >> towards the bottom this page:
    >> http://www.rogersaccesslibrary.com/OtherLibraries.asp
    >> --
    >> Jerry Whittle
    >> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
    >>
    >>
    >> "MartyO" wrote:
    >>
    >> > We have MS Access 2003, SP1 and SP2 users, user FE's linked to BE on a
    >> > server.
    >> >
    >> > Two users accessing the same record, we're getting "Could not
    >> > Save;Currenlty
    >> > locked by another user", instead of getting the friendly message that
    >> > lets
    >> > you handle record locking gracefully. It's a memo field that they are
    >> > editing.
    >> >
    >> > The strangest thing is that we are only getting this message on one
    >> > particular record. I've rebuilt the form, the table, deleted the
    >> > record and
    >> > copied it back in.
    >> >
    >> > Any ideas?
    >> > Thanks in advance for your help.
    >> > Marty




    --
    ----------------------------------------
    I am using the free version of SPAMfighter for private users.
    It has removed 4182 spam emails to date.
    Paying users do not have this message in their emails.
    Get the free SPAMfighter here: http://www.spamfighter.com/len
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page