Results 1 to 5 of 5
  1. #1
    Lounger
    Join Date
    Jun 2004
    Posts
    40
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Form or Table corruption??? (Access 2003 (SP2))

    Edited by HansV to provide link to post - see <!help=19>Help 19<!/help>

    A client of ours is running Windows XP (SP2) with Office 2003 (SP2) on all their PCs. They are experiencing a problem with one of our databases, whereby when they use a reasonably simple subform to input data into a table, the following error message is encountered when they try to tab out of the record (to move to the next available record): -

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Form or Table corruption??? (Access 2003 (SP2))

    Try creating a blank new database and importing as many database objects from the problem database into the new one.

  3. #3
    Lounger
    Join Date
    Jun 2004
    Posts
    40
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Form or Table corruption??? (Access 2003 (SP2))

    Oh yes, forgot to try that! I have just importing all the objects into a new database, but the problem still exists! Thanks anyway though!.

    Do you or anyone else have any more thoughts/ideas?

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Form or Table corruption??? (Access 2003 (SP2))

    You state that there's an identical database that doesn't have the problem. Are you absolutely sure that the problem database doesn't have something different, for example extra code? (Some VBA code can make the jet engine believe that the data have been manipulated by another user). If not, I fear that the problem database is damaged beyond recovery.

  5. #5
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Salem, Oregon, USA
    Posts
    219
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Form or Table corruption??? (Access 2003 (SP2))

    We had a very similar problem. It turns out that the recordset that the form was based upon was being invoked up to four times by other operations that got triggered within the form. Also, there was some circular coding, where the "on activate" event was being called over and over. This poor coding didn't seem to bite badly when the database was in '97, but, as soon as we converted it up to XP, the problem became chronic.

    The solution was to try to streamline the code, and issue record "saves" prior to bopping out to another form that used the same recordset.

    thx
    Pat

Posting Permissions

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