Engine stopping processes due to phantom data accesses!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • DaveSlade72
    New Member
    • Jan 2007
    • 23

    #16
    The notes that accompany the JetComp utility contains this explanation for the error:

    Error # 3197

    Error Description The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.

    Cause/Problem This is typically occurs when a long value column (an OLE or MEMO data-type) has bad data stored in it. Long value columns are typically stored in a separate page from the page that the row is stored in. If a long value column is present in the table schema, the Jet database engine will attempt to read the long value page when reading the row of data. In order to read the long value page, there is a pointer in the row of data. This error is generated when the Jet database engine cannot properly read the long value page from the pointer present in the data row. When viewing a row that exhibits this behavior in Microsoft Access data-windows, the user will typically see the number sign (#) for the entire row.
    Cheers,
    Dave

    Comment

    • puppydogbuddy
      Recognized Expert Top Contributor
      • May 2007
      • 1923

      #17
      Originally posted by DaveSlade72
      Ok. The problem lies with the linked database (which is also Access97).

      I've tried Repairing it, and that runs and says it's worked. Compacting it however throws up an error, initially that I don't have read permissions on the database, and the 'MSysCompactErr or' -

      ErrorCode ErrorDescriptio n ErrorRecid ErrorTable
      -1611 The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time. à8 TAXON_OCCURRENC E

      To be honest the databse looks like it's been compacted ok, but I'm not 100% certain.
      Dave,
      Ok, if it is not the Make Table Query, then the errors you are getting are on the list for symptoms of db corruption. See #4 on the list below:



      As to what is causing the corruption, it could be that you have not updated Jet or MDAC to the most recent service releases.

      Comment

      • DaveSlade72
        New Member
        • Jan 2007
        • 23

        #18
        Thanks, that's the conclusion I'd come to (see my post above).

        Best wishes and thanks,
        Dave

        Comment

        Working...