FIX: LUPDATE() Does Not Report Correct Century for Year 2000 (176481)


The information in this article applies to:

  • Microsoft Visual FoxPro for Windows 3.0
  • Microsoft Visual FoxPro for Windows 3.0b
  • Microsoft Visual FoxPro for Windows 5.0
  • Microsoft Visual FoxPro for Windows 5.0a
  • Microsoft FoxPro for Windows 2.6
  • Microsoft FoxPro for Windows 2.6a
  • Microsoft FoxPro for MS-DOS 2.6
  • Microsoft FoxPro for MS-DOS 2.6a
  • Microsoft Visual FoxPro for Macintosh 3.0b
  • Microsoft FoxPro for UNIX 2.6
  • Microsoft FoxBASE+ for MS-DOS 2.1
  • Microsoft FoxBASE+ for Macintosh 2.01
  • Microsoft FoxPro for Macintosh 2.6a
This article was previously published under Q176481

SYMPTOMS

When you use SET CENTURY ON with a computer that has the system date set to the year 2000 and a modification is made to the structure of a table (.dbf) file, or a copy of the table file is made, the LUPDATE() function incorrectly displays the century as 1900.

CAUSE

The date of the last update is stored in the header of the .dbf file. The LUPDATE() function reads the date of last update from the header of the .dbf file. This problem is caused by the manner in which FoxPro writes the date into the table's file header.

RESOLUTION

Use one of the following workarounds:
  • Use the FDATE() function to obtain the correct date. With SET CENTURY ON, this function returns the correct year.
  • Create a program subroutine with the ADIR() function to obtain the file date parameter as illustrated by the following program code:
    SET CENTURY ON
      =ADIR(afileinfo, "CUSTOMER.DBF")
      x = afileinfo(1, 3)
      ? x
NOTE: Because FoxBase does not support either the FDATE() or ADIR() function, these workarounds do not apply to FoxBase.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Visual FoxPro6.0.

MORE INFORMATION

The LUPDATE() function returns the date of the last update to the table in the currently selected work area or in a specified work area. The "last updated" date and time are not updated by the operating system until the file is closed. When you close a modified table, FoxPro writes the current system date of the computer into the header of the table file.

With a network, there is no guarantee that all the computers have a synchronized date and time. If the LUPDATE() function makes it appear that the table has not been updated today and then new information is entered into the table, you could be overwriting new data entered from a computer that has the wrong system date.

Steps to Reproduce Behavior

  1. Change the computer's system date to 02/01/2000 (the specific date is not critical as long as the year is 2000 or higher).
  2. In the FoxPro Command window, type the following without the comments:
          SET CENTURY ON
      USE <tablename>         && Name of the table.
      ?LUPDATE()              && Checks the current value of the last 
                              && updated date.
      APPEND BLANK            && Appends a blank record to the table.
      USE                     && This closes the table.
      USE <tablename>         && Open the table again.
      ?LUPDATE()              && Check the last updated date again.

    An incorrect answer is returned: 02/01/1900.
NOTE: Remember to reset your computer system date back to today's date.

REFERENCES

For more information about the LUPDATE(), FDATE(), and ADIR() functions, please see the following articles in the Microsoft Knowledge Base:

130165 PRB: LUPDATE() Does Not Return Date of Last Update

113943 New and Enhanced Commands and Functions in FoxPro Ver 2.6

100554 Using ADIR() Function to Obtain MS-DOS File Information

Microsoft FoxPro Help, "LUPDATE() Function"

Microsoft FoxPro Help, "FDATE() Function"

Microsoft FoxPro Help, "ADIR() Function"

Modification Type:MinorLast Reviewed:3/10/2005
Keywords:kbbug kbfix KB176481
©2004 Microsoft Corporation. All rights reserved.