2 {{ upvoteCount | shortNum }}
2 {{ upvoteCount | shortNum }}

MSAccess MDB corruption

by tatumbooth
1 replies
Migrated VB6 (MS Access 2003) based application from Windows Server 2008 Enterprise to Windows Server 2008 R2. The application is accessed via network share from Citrix XenApp.
Since the move, we have had an almost daily corruption issue in one of the mdb files. Does WIN2K8 R2 behave differently than WIN2K8 Enterprise in terms of handling open sessions? The Citrix servers reboot nightly - some end-users are bad about logging out correctly and leaving sessions idle.
Is there a file monitoring tool, script or some other method to monitor the file for corruption and send an e-mail notification?
#corruption #mdb #msaccess
  • Profile picture of the author henrybarker32
    Some things that may say you about corruption and methods to get rid of it, if they can't assist use more powerful solution for complicated cases of access database corruption https://access.recoverytoolbox.com/ Recovery Toolbox for Access

    Access uses a pointer to another location for the data in large fields (memo, hyperlink, or OLE Object). If the pointer is written incorrectly, the field displays garbage.
    To address this kind of corruption, delete the memo field from your table. Compact to get completely rid of it:
    • In Access 2010, Compact and Repair Database on the Database Tools ribbon.
    • In Access 2007, click Office Button (top left) | Manage | Compact.
    • In Access 95 - 2003, Tools | Database Utilities | Compact.
    Then create the memo field again. If the data is important, you may be able to link to an older backup (File | Get External | Link in Access 95 - 2003; External Data | Import in Access 2007 and 2010), create a query joining the current and older copy on the primary key, and then change it to an Update query to update the now blank memo field with the contents of the old one.
    If the strange characters appear only in the query, not when you view the table, this is not a corruption. This occurs when JET is unable to determine the data type of the query field, and is triggered by lots of situations. Solutions for this non-corruption issue include:
    • Add a primary key to your table.
    • Explicitly typecast the field.
    • Do not concatenate text fields that generate more than 255 characters.
    {{ DiscussionBoard.errors[10185243].message }}

Trending Topics