Folks,

strange enough: on our site, the original HP recommendation VSETNEXTCENTURY 2
(without the 0 in the JCW's name) does the job ...

Thanks for this posting - it helped our site as well!

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 28/02/2000 10:03:10 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/GIS/CSC)
Subject:  Re: leap year



Tony White wrote me personally...

<snip>
We were told to also set the JCW VSETNEXTCENTURY0 = 2. That's a zero at the
end.
</snip>

THAT DID IT!!  Thanks Tony and to all else who answered.

Ernie

> -----Original Message-----
> From: Newton, Ernie
> Sent: Monday, February 28, 2000 12:09 PM
> To:   [log in to unmask]
> Subject:      leap year
>
> Greetings,
>
> We are having a problem with VPLUS recognizing 2/29/00.  I've contacted HP
> and they suggested that the JCW VSETNEXTCENTURY = 2 should be set as a
> system-wide UDC.  I have placed it in the logon UDC to execute when
> anybody logs on and it works, but we are still having trouble.  Any
> suggestions?
>
> The error we get is "The field must be a valid date, in MDY order.(YEAR =
> YYYY)" , with RCA100.
>
> We are currently on 5.5 with powerpatch 6 and I've also installed the
> VPLKXR3 patch.
> We also have FORMSPEC/V B.06.07
>
>
> Thanks,
>
>
> Ernie Newton
> Computer Systems Specialist
> Yolo County Office of Education
> [log in to unmask]