Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Locked register in Access 2000

Locked register in Access 2000

Scheduled Pinned Locked Moved C#
databasehelpquestionannouncementlounge
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Chals
    wrote on last edited by
    #1

    Hi, I am having a problem when trying to update a table in Access 2000. At (apparently) random times, it throws the following exception. It is translated from spanish, might not be exactly the same in english; 'Can't update. This record is currently locked' There is no concurrent access to this database. Any ideas? Thanks in advance

    D 1 Reply Last reply
    0
    • C Chals

      Hi, I am having a problem when trying to update a table in Access 2000. At (apparently) random times, it throws the following exception. It is translated from spanish, might not be exactly the same in english; 'Can't update. This record is currently locked' There is no concurrent access to this database. Any ideas? Thanks in advance

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      The first thing I'd ask is, "Did you close all of your object when you where done with them? DataSet's, DataReader's, Connection's, ..." Don't keep a connection constantly open to a database. Keep it open only as long as you need to complete the transaction you need. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      C 1 Reply Last reply
      0
      • D Dave Kreskowiak

        The first thing I'd ask is, "Did you close all of your object when you where done with them? DataSet's, DataReader's, Connection's, ..." Don't keep a connection constantly open to a database. Keep it open only as long as you need to complete the transaction you need. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

        C Offline
        C Offline
        Chals
        wrote on last edited by
        #3

        Well I have a couple datatables pointing to the database through the same connection, but NEVER had problems until now. Thought the locking policy came into play when there was more than one user accessing the database. Still, I'll give a look and try to keep 'data objects' to a minimum. Thanks for the reply

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups