Article ID: 229020
Article Last Modified on 10/15/2002
APPLIES TO
- Microsoft Visual FoxPro 6.0 Professional Edition
This article was previously published under Q229020
SYMPTOMS
You have a Visual FoxPro application written using @ GET commands. You have issued a SET CENTURY OFF command in your application code. If you use an @ GET referring to a date variable or field, the year portion of the date might display incorrectly when the @ GET does not have focus. Note that the underlying data is unaffected, only the display may be incorrect.
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 Studio 6.0 Service Pack 3.
For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:
194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
MORE INFORMATION
Steps to Reproduce Behavior
Run the following code from a program (.PRG) file:
CLEAR SET CENTURY OFF dDate = {^1999/04/05} cString = "Another GET" @ 1,1 GET dDate SIZE 1,10 FONT "Courier New",10 @ 3,1 GET cString FONT "Courier New",10 READ CYCLE- Tab between the two @ GETs. The year value in the first @GET will be 1999 when it has focus and 2019 when the focus moves to the second @ GET.
- Type 01/01/01 in the date field, and then press Tab a few times. The year value of first @ GET will be 2001 when it has focus and the year value will be 2020 when the second @ GET has focus.
- If you monitor the value of dDate in the Debugger Locals window while tabbing between the two @GETS, you will see its value remains unchanged although the display does change.
Keywords: kbbug kbfix kbxbase kbvs600sp3fix KB229020
