ACC2000: DAO LastUpdated Property Returns Incorrect Date/Time (299554)

MORE INFORMATION

The LastUpdated property provided by DAO returns the correct date/time for Jet database 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).

In earlier versions, 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 introduces 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, 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, in a Jet database (.mdb), Jet 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 Jet database engine; therefore, the DateUpdate column always stays the same.

Additionally, you may have noticed that the Database window 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 Jet database engine. Unfortunately, Microsoft Access 2000 does not currently expose this information in its object model; therefore, there is no programmatic way to get to this information in Microsoft Access 2000.

Steps to Reproduce the Behavior

1. Start Microsoft Access 2000, and then create a new, blank database.
2. Create a new, blank form in Design view.
3. Add a text box to the form.
4. Save the form as frmLastUpdated, and then close it.
5. On the View menu, click Details. This displays the Modified and Created dates for each object.
6. Note that both the Modified and Created columns for the frmLastUpdated form are set to the same date and time.
7. Press CTRL+G to open the Immediate window in the Visual Basic Editor.
8. Type the following line into the Immediate window, and then press ENTER:
   
   

   ?CurrentDb.Containers("Forms").Documents("frmLastUpdated").LastUpdated
   						

   Note that the date and time returned corresponds to the Modified and Created columns in the Database window.
9. Press ALT+F11 to switch back to Microsoft Access.
10. Open the frmLastUpdated form in Design view.
11. Add a second text box to the form, and then save and close it.
    
    Note that the Modified column in the Database window contains an updated date and time for the form.
12. Repeat steps 7 and 8.

Note the LastUpdated property still returns the original date and time instead of the new date and time displayed in the Modified column in the Database window.