Darn it, Barbara, I asked you to contradict me! :)

Rich.

>Rich, I didn't read the post carefully enough, and now that you mention it I remember the earlier posts about the 2/4 digit display. My mind was set in the 'Sets are data-session specific' mold and I answered THAT question.
>
>Thanks for the correction
>Barbara
>
>>If you read her post carefully, I think you'll see she said she starts with CENTURY OFF, then if the user enters a 21st century date, VFP seems to force CENTURY ON. I seem to remember Dave Bower noticing this behavior a few months ago as well. I think the concensus at the time was that it was acknowledged as a bug (or at least inappropriate, or unexpected, but confirmed behavior). I think the workaround people decided on was that you just have to start with CENTURY ON and live with it, if you're going to be entering 21st century dates in VFP.
>>
>>I would love it if someone could contradict me on this. It's a pretty big hole in my favorite product.
>>
>>- Rich.
>>
>>>This display is linked to Set Century ON/OFF. You'll have to change the setting before loading the form.
>>>
>>>
>>>>A little bit of weird behavior, maybe there is and easy answer. When we use some of our legacy code using @... say in vfp, if the customer keys in a 21st century date, the display switches from 2 to 4 digit year even though the field size hasn't changed on the screen, so you now see 01/01/20 with the other two 0's scrolled off the field. We would really like to find a solution for this besides set century on. Any ideas?