Article ID: 299554 - View products that this article applies to.
This article was previously published under Q299554
Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies only to a Microsoft Access database (.mdb).
The Data Access Objects (DAO) LastUpdated property returns incorrect dates/times for Microsoft Access forms, reports, macros, and modules.
Microsoft Access does not notify the Microsoft Jet database engine about the modification of Access-specific objects (forms, reports, macros, and modules); therefore, the DateUpdate column in the MSysObjects table is never updated to the correct date and time. The same behavior is true for Microsoft Access 2007, which uses the Microsoft Access Database Engine.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The LastUpdated property provided by DAO returns the correct date/time for database engine objects (tables, queries, and relationships), but it only returns the creation date, not the last modified date for Microsoft Access specific-objects (forms, reports, macros, and modules).
Prior to Microsoft Access 2000, Microsoft Access used a Jet database (.mdb) file to store both database objects (tables, queries, and relationships) as well as the Microsoft Access-specific objects (forms, reports, macros, and modules). Microsoft Access stored its specific objects in Jet system tables, specifically the MSysObjects and MSysModules (or MSysModules2) tables. The DateUpdate column in the MSysObjects table is responsible for storing an object's last modification date and is the column that the DAO LastUpdated property uses to return an object's last modified date. When a user modified and saved an object in earlier versions, Microsoft Access notified the Jet database engine that the object had been modified, and Jet updated the DateUpdate column to the current date and time.
Microsoft Access 2000 introduced Access project (.adp) files, which have the capability of connecting directly to Microsoft SQL Server databases without using the Jet database engine. Because ADP files do not use the Jet database engine (or the Access Database Engine), Access could not use the same storage format previously used in Jet databases for Access-specific objects. It had to store them in a new OLE doc storage format that is accessible in both Jet databases and Access projects. When the user initially creates a new Microsoft Access specific-object, such as a form), the database engine still enters the current date and time into the DateCreate and DateUpdate columns in the MSysObjects table. However, when the user modifies and saves the object, Microsoft Access does not notify the database engine; therefore, the DateUpdate column always stays the same.
Additionally, you may have noticed that the Database window (in versions prior to Access 2007) and the Navigation Pane in Access 2007 or Access 2010 displays the correct date and time for an object's last modification. This is because Microsoft Access uses its own internal mechanism for storing the date created and date modified, independent of the database engine. Unfortunately, Microsoft Access does not expose this information in its object model; therefore, there is no programmatic way to get to this information in Microsoft Access.
Steps to Reproduce the Behavior