Welcome to SPN

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

Sign Up Now!

How to resolve a record locked problem?

Discussion in 'Information Technology' started by Cesar Ronchese, Nov 10, 2005.

  1. Cesar Ronchese

    Cesar Ronchese
    Expand Collapse
    Guest

    Hi All.

    I'm doing a maintenance in a program full developed with MS Access 97
    (database + forms). Recently, the customers have upgraded his Office
    version to XP.

    After it, they are getting problems on update their data (MSAccess forms).
    The problems are about record locking, saying something like "The record is
    locked by another user in this session". Reiterating, this issue didn't
    happens when computer had office 97.

    I disconnected all the accesses to the database to see if there are others
    users locking the record, but It occurs when are only one user on the db.

    So, what I'm needing is:

    - there are some manner to disable the default MSAccess behaviour, changing
    from pessimistic locking to optimistic locking, so the problem will not show
    anymore?

    - or someone know any other way so I can resolve it?


    PS.: the customer will change this MSAccess software to a .NET+SQL software
    in a few months, so the solution can be palliative.
     
  2. Loading...


  3. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    Cesar Ronchese wrote:
    > Hi All.
    >
    > I'm doing a maintenance in a program full developed with MS Access 97
    > (database + forms). Recently, the customers have upgraded his Office
    > version to XP.
    >
    > After it, they are getting problems on update their data (MSAccess
    > forms). The problems are about record locking, saying something like
    > "The record is locked by another user in this session". Reiterating,
    > this issue didn't happens when computer had office 97.
    >
    > I disconnected all the accesses to the database to see if there are
    > others users locking the record, but It occurs when are only one user
    > on the db.
    >
    > So, what I'm needing is:
    >
    > - there are some manner to disable the default MSAccess behaviour,
    > changing from pessimistic locking to optimistic locking, so the
    > problem will not show anymore?
    >
    > - or someone know any other way so I can resolve it?
    >
    >
    > PS.: the customer will change this MSAccess software to a .NET+SQL
    > software in a few months, so the solution can be palliative.


    First I suggest you check to make sure all the users have full access to
    the directory where the database is located. They need the ability to
    delete files.

    --
    Joseph Meehan

    Dia duit
     
  4. Cesar Ronchese

    Cesar Ronchese
    Expand Collapse
    Guest

    I've checked that. They have full permission on the sharing and on the
    Windows folder security.

    I brought all the related MDBs to my PC and recreated the ambient. Then,
    other thing I noticed is, the first time I try save the record, its Ok. The
    second time the error raises, even when closing and opening the Access
    again.






    "Joseph Meehan" <sligojoe_Spamno@hotmail.com> wrote in message
    news:ZLrcf.124425$tD4.86764@tornado.ohiordc.rr.com...
    > Cesar Ronchese wrote:
    >> Hi All.
    >>
    >> I'm doing a maintenance in a program full developed with MS Access 97
    >> (database + forms). Recently, the customers have upgraded his Office
    >> version to XP.
    >>
    >> After it, they are getting problems on update their data (MSAccess
    >> forms). The problems are about record locking, saying something like
    >> "The record is locked by another user in this session". Reiterating,
    >> this issue didn't happens when computer had office 97.
    >>
    >> I disconnected all the accesses to the database to see if there are
    >> others users locking the record, but It occurs when are only one user
    >> on the db.
    >>
    >> So, what I'm needing is:
    >>
    >> - there are some manner to disable the default MSAccess behaviour,
    >> changing from pessimistic locking to optimistic locking, so the
    >> problem will not show anymore?
    >>
    >> - or someone know any other way so I can resolve it?
    >>
    >>
    >> PS.: the customer will change this MSAccess software to a .NET+SQL
    >> software in a few months, so the solution can be palliative.

    >
    > First I suggest you check to make sure all the users have full access
    > to the directory where the database is located. They need the ability to
    > delete files.
    >
    > --
    > Joseph Meehan
    >
    > Dia duit
    >
     
  5. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    Cesar Ronchese wrote:
    > I've checked that. They have full permission on the sharing and on the
    > Windows folder security.
    >
    > I brought all the related MDBs to my PC and recreated the ambient.
    > Then, other thing I noticed is, the first time I try save the record,
    > its Ok. The second time the error raises, even when closing and
    > opening the Access again.
    >


    I'm sorry, I am out of ideas. You have eliminated all the usual things
    I can think of.

    >
    >
    >
    >
    >
    > "Joseph Meehan" <sligojoe_Spamno@hotmail.com> wrote in message
    > news:ZLrcf.124425$tD4.86764@tornado.ohiordc.rr.com...
    >> Cesar Ronchese wrote:
    >>> Hi All.
    >>>
    >>> I'm doing a maintenance in a program full developed with MS Access
    >>> 97 (database + forms). Recently, the customers have upgraded his
    >>> Office version to XP.
    >>>
    >>> After it, they are getting problems on update their data (MSAccess
    >>> forms). The problems are about record locking, saying something like
    >>> "The record is locked by another user in this session". Reiterating,
    >>> this issue didn't happens when computer had office 97.
    >>>
    >>> I disconnected all the accesses to the database to see if there are
    >>> others users locking the record, but It occurs when are only one
    >>> user on the db.
    >>>
    >>> So, what I'm needing is:
    >>>
    >>> - there are some manner to disable the default MSAccess behaviour,
    >>> changing from pessimistic locking to optimistic locking, so the
    >>> problem will not show anymore?
    >>>
    >>> - or someone know any other way so I can resolve it?
    >>>
    >>>
    >>> PS.: the customer will change this MSAccess software to a .NET+SQL
    >>> software in a few months, so the solution can be palliative.

    >>
    >> First I suggest you check to make sure all the users have full
    >> access to the directory where the database is located. They need
    >> the ability to delete files.
    >>
    >> --
    >> Joseph Meehan
    >>
    >> Dia duit


    --
    Joseph Meehan

    Dia duit
     

Share This Page