Results 1 to 5 of 5
  1. #1
    Lounger
    Join Date
    Jul 2002
    Location
    Wheaton, Illinois, USA
    Posts
    39
    Thanks
    0
    Thanked 0 Times in 0 Posts

    access (runtime)

    Many of our user are getting an error message when working in access runtime. The microsoft jet database engine stopped the process because you and another user are attempting to change the same data at he same time. Does anyone have an answer. Please help! We have the database split frontend backend. It was created in access 97. We converted it to access2000. This is how the problem started.
    Thanks, Marie

  2. #2
    2 Star Lounger
    Join Date
    Jan 2001
    Location
    Mishawaka, Indiana, USA
    Posts
    145
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: access (runtime)

    Look for missing references in your 2000 mdb file.

    Open any module. Select Tools / References.

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: access (runtime)

    You appear to be getting an edit collision. What kind of locking scheme are you using?
    Charlotte

  4. #4
    Bronze Lounger
    Join Date
    Nov 2001
    Location
    Arlington, Virginia, USA
    Posts
    1,394
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: access (runtime) - Corrupt Record Error Msg

    The error message you described often indicates corrupt record or records. Recommend refer to following MS Knowledge Base articles:

    ACC: Jet Database Engine 3.x Error Messages Due to Corruption (Q182867)

    ACC97: Concurrent Appends to a Memo Field Can Cause Corruption and Produces the #deleted Symbol (Q235391)

    Note that the articles refer to Access 97, but I

  5. #5
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: access (runtime)

    Hi Marie

    I had the same message, in my case I think the problem was caused by using too many memo fields.

    I have a master record and six detail tables attached to a 7 tab form with six sub forms

    The master record has 5 memo fields and each six subforms each had a memo field (this design was a carry over from a working dbase system)

    I simply changed the memo field in the six detail table and sub form to text 255 in len and the problem went away. I did'nt touch the memo fields in the master record.

    In my case 255 was enought space to hold the memo data.

    If you do a forum search on your "error message", you will find solutions from charlotte and others.

    Aparently memo fields are stored differently and can share the same page as other memo field in the record set, this message has happen to me in a single user environment

    HTH

    John

Posting Permissions

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