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. Visual Basic
  4. Locking Database Edit

Locking Database Edit

Scheduled Pinned Locked Moved Visual Basic
csharpasp-netdatabasequestion
4 Posts 4 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.
  • O Offline
    O Offline
    ONeil Tomlinson
    wrote on last edited by
    #1

    Im writing an asp.net application that 5 persons will be using. How do i go about locking data edit when its been editing by another person

    L D 2 Replies Last reply
    0
    • O ONeil Tomlinson

      Im writing an asp.net application that 5 persons will be using. How do i go about locking data edit when its been editing by another person

      L Offline
      L Offline
      leong_wang
      wrote on last edited by
      #2

      recording currently user,then locked it -- when someone login,recording his info in database,then otherone login,access this info table,if someone in it ,then locked database for this one

      1 Reply Last reply
      0
      • O ONeil Tomlinson

        Im writing an asp.net application that 5 persons will be using. How do i go about locking data edit when its been editing by another person

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

        This question really belongs in the ASP.NET forum. But, since, in an ASP.NET app, there is no guarantee that the person will actually edit and submit the changes before the session times out. Does it sounds like locking records is not a good idea? You'll have to write code to handle the timeout of the session and, if you get no response from the user, unlock the records in the database. If you really want to do this, you'll have to implement some kind of "checkout" scheme in your own custom session manager.

        Dave Kreskowiak Microsoft MVP - Visual Basic

        J 1 Reply Last reply
        0
        • D Dave Kreskowiak

          This question really belongs in the ASP.NET forum. But, since, in an ASP.NET app, there is no guarantee that the person will actually edit and submit the changes before the session times out. Does it sounds like locking records is not a good idea? You'll have to write code to handle the timeout of the session and, if you get no response from the user, unlock the records in the database. If you really want to do this, you'll have to implement some kind of "checkout" scheme in your own custom session manager.

          Dave Kreskowiak Microsoft MVP - Visual Basic

          J Offline
          J Offline
          jsampsonPC
          wrote on last edited by
          #4

          Would not Transactional-updates also be a factor here? Locking the entries for the purpose of updating their content without allowing anybody else to simultaneously modify the same information. Correct me if I'm wrong, but I figured this was more of a TSQL question :)

          Jonathan Sampson www.SampsonResume.com

          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