Results 1 to 3 of 3
  1. #1
    New Lounger
    Join Date
    Jul 2001
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    #Error in table after corruption (A97Sr-1)

    I look after a shared access97 database on a NT network. From time to time it corrupts - and after repair one (or more) records in the tables have #ERROR in the data table(s). The records affected can't be edited - the only thing that can be done is to delete the record. Sometime the deletion of the affected record causes a further crash.

    Does anybody know what causes it ?

    Is there any way to avoid it ?

    Is there a way to recover the record - rather than delete and re-enter?

    Any help would be appreciated

    Thanks in advance!

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

    Re: #Error in table after corruption (A97Sr-1)

    This can usually, if not always, be traced to the presence of memo fields in the table. Even though memo fields look like they're in the table, they really live elsewhere. When the link between the record and its memo field gets corrupted, you get the problem you described. There is no way to recover the memo field, although you may be able to record the rest of the data by querying it out to a temp table before you delete the record.
    Charlotte

  3. #3
    New Lounger
    Join Date
    Jul 2001
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: #Error in table after corruption (A97Sr-1)

    Thanks Charlotte!

    I hate Memo Fields - this db was not my creation - I just inherrited it !

    Cheers !

    GaryC

Posting Permissions

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