Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003
    Posts
    1

    Exclamation Unanswered: Error 3260 couldn't update; currently locked

    Hi,
    I am using VC++ and microsoft access for my application,
    and opening the database through CRecordset.
    After addtion of 30000 records I am getting the error:

    3260 couldn't update; currently locked by user <1> on machine <2>.

    Though this is a single user system and adding all these records from single function this error is coming.

    After Clicking OK program is running through it's normal way and adding new records.

    Again after adding few thousands of records the above error comes.

    setting used are Dynaset and pessimistic locking.

    Is there is any mechanism in vc++ so that no error message from system should be displayed.

    What Setting of access should I use to remove the above error.

    Please help me.

    Sandip

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    I don't know a thing about CRecordset or exactly how your application is working, but as a wild guess I would look at the commit interval being used and maybe try to commit more often if possible.

  3. #3
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1

    Re: Error 3260 couldn't update; currently locked

    Originally posted by sandip_bhirud79
    Hi,
    I am using VC++ and microsoft access for my application,
    and opening the database through CRecordset.
    I'm not sure if this is the right forum to ask questions about MS Access but if you search MSDN for "error 3260" you'll get this:
    3260 "Couldn't update; currently locked by user <name> on machine <name>."

    This error occurs when a user attempts to edit a record and the current record (or if you are using page-level locking, the page it is on) is locked.

    If you are using page-level locking, this error also occurs when a user uses the AddNew method or the Update method to save a record on a locked page. This situation can occur when the user is trying to save a new record or when optimistic locking is in place and another user locks the page.

    To handle this error, program your solution to wait for a short period of time, and then try to save the record again. Or, you can inform users of the problem and allow them to indicate whether or not they want to retry the operation.
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •