[SPAM] Employee File Birthdate Corruption

Yahoo Archive
1
This isn't operator error because the records have been set up for at
least 8 years (since we started using Vantage). At any rate, support
sent me a fix yesterday so this apparently is a bug. Thanks for all
the replies!!

Sue

--- In vantage@yahoogroups.com, <lonwiksell@...> wrote:
>
> It may be an operator error but Vantage should never allow that to
> happen. Birthdate should be edited for correctness. In other words
> birthdate can not be greater than today and probably questioned if
it is
> not today + 16 years. Likewise birthdate should be questioned if
it is
> more than 70 years ago. This is a big problem with Vantage because
many
> dates such as order dates are not properly edited. I have written
> several Access programs that do after the fact edit checking that
should
> be done on data entry.
>
>
>
> Lon
>
> ROM Corporation
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of pvolkert365
> Sent: Friday, April 11, 2008 3:49 PM
> To: vantage@yahoogroups.com
> Subject: Re: [SPAM] [Vantage] Employee File Birthdate Corruption
>
>
>
> A year ago (8.03.305x) I made the exact same discovery. Some of our
> birthdates had jumped ahead 100 years. I even put a support call
> in. I finally realized that the person entering the data had used
> two digits for the year and it was in there as 2050 instead of
1950.
> Since you rarely look at that field, it was not noticed. But it was
> operator error.
>
> -Peter
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Calvin Krusen" <ckrusen@> wrote:
> >
> >
> > I Hope not!
> >
> > Isn't the 19 century the 1800's? Just Kidding.
> >
> > But seriously, does Epicor/Progress use pre-Y2K thinking with
their
> DBs?
> > I thought all dates were stored as days from a defined day 'zero'.
> >
> > Could this really be a user interface issue? Meaning that when
> only two
> > digits are entered for the year, the system guesses the century
to
> use.
> >
> >
> >
> > Calvin Krusen
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> ,
> "Winter, Patrick" <pjw@> wrote:
> > >
> > > This is not file corruption, it sounds like a database century
> > parameter
> > > issue. You set it to 59 and the system defaults larger numbers
to
> 19th
> > > century, lower numbers to 20st century.
> > >
> > >
> > >
> > > Patrick J. Winter
> > >
> > >
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> ] On
> > Behalf
> > > Of smj2cool
> > > Sent: Friday, April 11, 2008 7:39 AM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > Subject: [SPAM] [Vantage] Employee File Birthdate Corruption
> > >
> > >
> > >
> > > Here's one for the group that I'll bet you've not heard before.
I
> > > discovered that any employee with a birtdate in the 1950's and
> 1960's
> > > has been changed to 2050, etc... This absolutely is not any
type
> of
> > > operator error since most of these birthdates have been set up
for
> > > years. I logged a call with Vantage two days ago but have not
> heard a
> > > peep from them. Just wondering if anyone else has experienced
> > > something like this. This is very disturbing - what if Vantage
> decided
> > > to corrupt the employee rate dates - that would be a horrible
> mess. We
> > > are on v 8.03.404
> > >
> > >
> > >
> > >
> > >
> > > This e-mail and any attachments may contain confidential and
> > > privileged information. If you are not the intended recipient,
> > > please notify the sender immediately by return e-mail, delete
this
> > > e-mail and destroy any copies. Any dissemination or use of this
> > > information by a person other than the intended recipient is
> > > unauthorized and may be illegal.
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
Here's one for the group that I'll bet you've not heard before. I
discovered that any employee with a birtdate in the 1950's and 1960's
has been changed to 2050, etc... This absolutely is not any type of
operator error since most of these birthdates have been set up for
years. I logged a call with Vantage two days ago but have not heard a
peep from them. Just wondering if anyone else has experienced
something like this. This is very disturbing - what if Vantage decided
to corrupt the employee rate dates - that would be a horrible mess. We
are on v 8.03.404
3
If this is like 6.1 there is a Progress paramter for handling century assumption on 2 digit years. We have ours set to 1929. Perhaps this parameter got changed or overwritten in a patch upgrade? I'm not familiar enough with 8.x to advise where to look but this sounds like that parameter got hit.
-Todd C.


________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of smj2cool
Sent: Friday, April 11, 2008 7:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Employee File Birthdate Corruption


Here's one for the group that I'll bet you've not heard before. I
discovered that any employee with a birtdate in the 1950's and 1960's
has been changed to 2050, etc... This absolutely is not any type of
operator error since most of these birthdates have been set up for
years. I logged a call with Vantage two days ago but have not heard a
peep from them. Just wondering if anyone else has experienced
something like this. This is very disturbing - what if Vantage decided
to corrupt the employee rate dates - that would be a horrible mess. We
are on v 8.03.404





[Non-text portions of this message have been removed]
4
This is not file corruption, it sounds like a database century parameter
issue. You set it to 59 and the system defaults larger numbers to 19th
century, lower numbers to 20st century.



Patrick J. Winter



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of smj2cool
Sent: Friday, April 11, 2008 7:39 AM
To: vantage@yahoogroups.com
Subject: [SPAM] [Vantage] Employee File Birthdate Corruption



Here's one for the group that I'll bet you've not heard before. I
discovered that any employee with a birtdate in the 1950's and 1960's
has been changed to 2050, etc... This absolutely is not any type of
operator error since most of these birthdates have been set up for
years. I logged a call with Vantage two days ago but have not heard a
peep from them. Just wondering if anyone else has experienced
something like this. This is very disturbing - what if Vantage decided
to corrupt the employee rate dates - that would be a horrible mess. We
are on v 8.03.404





This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]
5
> If this is like 6.1 there is a Progress paramter for handling century
> assumption on 2 digit years. We have ours set to 1929.

But isn't the century assumption used only for entry of new dates? I can't
imagine any software company in the world today who would actually store the
year using only two digits. If a date field is being copied in a conversion,
it should not have to make any century assumptions since the century should be
included. The only way I can see this happening is if an export program lopped
off the century before being read by the conversion program - and that's a
bug.

More fun with computer dates: http://www.theiet.org/factfiles/it/dates.cfm

Mark W.
6
Thanks for your replies. Since you so readily understood my issue
and a possible fix, I can only wonder why I haven't heard from
support yet. We did recently install a patch so perhaps that's the
cause.

Sue Jones

--- In vantage@yahoogroups.com, Todd Caughey <caugheyt@...> wrote:
>
> If this is like 6.1 there is a Progress paramter for handling
century assumption on 2 digit years. We have ours set to 1929.
Perhaps this parameter got changed or overwritten in a patch
upgrade? I'm not familiar enough with 8.x to advise where to look
but this sounds like that parameter got hit.
> -Todd C.
>
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of smj2cool
> Sent: Friday, April 11, 2008 7:39 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Employee File Birthdate Corruption
>
>
> Here's one for the group that I'll bet you've not heard before. I
> discovered that any employee with a birtdate in the 1950's and
1960's
> has been changed to 2050, etc... This absolutely is not any type of
> operator error since most of these birthdates have been set up for
> years. I logged a call with Vantage two days ago but have not heard
a
> peep from them. Just wondering if anyone else has experienced
> something like this. This is very disturbing - what if Vantage
decided
> to corrupt the employee rate dates - that would be a horrible mess.
We
> are on v 8.03.404
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
7
I Hope not!

Isn't the 19 century the 1800's? Just Kidding.

But seriously, does Epicor/Progress use pre-Y2K thinking with their DBs?
I thought all dates were stored as days from a defined day 'zero'.

Could this really be a user interface issue? Meaning that when only two
digits are entered for the year, the system guesses the century to use.



Calvin Krusen

--- In vantage@yahoogroups.com, "Winter, Patrick" <pjw@...> wrote:
>
> This is not file corruption, it sounds like a database century
parameter
> issue. You set it to 59 and the system defaults larger numbers to 19th
> century, lower numbers to 20st century.
>
>
>
> Patrick J. Winter
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of smj2cool
> Sent: Friday, April 11, 2008 7:39 AM
> To: vantage@yahoogroups.com
> Subject: [SPAM] [Vantage] Employee File Birthdate Corruption
>
>
>
> Here's one for the group that I'll bet you've not heard before. I
> discovered that any employee with a birtdate in the 1950's and 1960's
> has been changed to 2050, etc... This absolutely is not any type of
> operator error since most of these birthdates have been set up for
> years. I logged a call with Vantage two days ago but have not heard a
> peep from them. Just wondering if anyone else has experienced
> something like this. This is very disturbing - what if Vantage decided
> to corrupt the employee rate dates - that would be a horrible mess. We
> are on v 8.03.404
>
>
>
>
>
> This e-mail and any attachments may contain confidential and
> privileged information. If you are not the intended recipient,
> please notify the sender immediately by return e-mail, delete this
> e-mail and destroy any copies. Any dissemination or use of this
> information by a person other than the intended recipient is
> unauthorized and may be illegal.
>
> [Non-text portions of this message have been removed]
>
8
A year ago (8.03.305x) I made the exact same discovery. Some of our
birthdates had jumped ahead 100 years. I even put a support call
in. I finally realized that the person entering the data had used
two digits for the year and it was in there as 2050 instead of 1950.
Since you rarely look at that field, it was not noticed. But it was
operator error.

-Peter

--- In vantage@yahoogroups.com, "Calvin Krusen" <ckrusen@...> wrote:
>
>
> I Hope not!
>
> Isn't the 19 century the 1800's? Just Kidding.
>
> But seriously, does Epicor/Progress use pre-Y2K thinking with their
DBs?
> I thought all dates were stored as days from a defined day 'zero'.
>
> Could this really be a user interface issue? Meaning that when
only two
> digits are entered for the year, the system guesses the century to
use.
>
>
>
> Calvin Krusen
>
> --- In vantage@yahoogroups.com, "Winter, Patrick" <pjw@> wrote:
> >
> > This is not file corruption, it sounds like a database century
> parameter
> > issue. You set it to 59 and the system defaults larger numbers to
19th
> > century, lower numbers to 20st century.
> >
> >
> >
> > Patrick J. Winter
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf
> > Of smj2cool
> > Sent: Friday, April 11, 2008 7:39 AM
> > To: vantage@yahoogroups.com
> > Subject: [SPAM] [Vantage] Employee File Birthdate Corruption
> >
> >
> >
> > Here's one for the group that I'll bet you've not heard before. I
> > discovered that any employee with a birtdate in the 1950's and
1960's
> > has been changed to 2050, etc... This absolutely is not any type
of
> > operator error since most of these birthdates have been set up for
> > years. I logged a call with Vantage two days ago but have not
heard a
> > peep from them. Just wondering if anyone else has experienced
> > something like this. This is very disturbing - what if Vantage
decided
> > to corrupt the employee rate dates - that would be a horrible
mess. We
> > are on v 8.03.404
> >
> >
> >
> >
> >
> > This e-mail and any attachments may contain confidential and
> > privileged information. If you are not the intended recipient,
> > please notify the sender immediately by return e-mail, delete this
> > e-mail and destroy any copies. Any dissemination or use of this
> > information by a person other than the intended recipient is
> > unauthorized and may be illegal.
> >
> > [Non-text portions of this message have been removed]
> >
>
9
It may be an operator error but Vantage should never allow that to
happen. Birthdate should be edited for correctness. In other words
birthdate can not be greater than today and probably questioned if it is
not today + 16 years. Likewise birthdate should be questioned if it is
more than 70 years ago. This is a big problem with Vantage because many
dates such as order dates are not properly edited. I have written
several Access programs that do after the fact edit checking that should
be done on data entry.



Lon

ROM Corporation



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of pvolkert365
Sent: Friday, April 11, 2008 3:49 PM
To: vantage@yahoogroups.com
Subject: Re: [SPAM] [Vantage] Employee File Birthdate Corruption



A year ago (8.03.305x) I made the exact same discovery. Some of our
birthdates had jumped ahead 100 years. I even put a support call
in. I finally realized that the person entering the data had used
two digits for the year and it was in there as 2050 instead of 1950.
Since you rarely look at that field, it was not noticed. But it was
operator error.

-Peter

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Calvin Krusen" <ckrusen@...> wrote:
>
>
> I Hope not!
>
> Isn't the 19 century the 1800's? Just Kidding.
>
> But seriously, does Epicor/Progress use pre-Y2K thinking with their
DBs?
> I thought all dates were stored as days from a defined day 'zero'.
>
> Could this really be a user interface issue? Meaning that when
only two
> digits are entered for the year, the system guesses the century to
use.
>
>
>
> Calvin Krusen
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Winter, Patrick" <pjw@> wrote:
> >
> > This is not file corruption, it sounds like a database century
> parameter
> > issue. You set it to 59 and the system defaults larger numbers to
19th
> > century, lower numbers to 20st century.
> >
> >
> >
> > Patrick J. Winter
> >
> >
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > Of smj2cool
> > Sent: Friday, April 11, 2008 7:39 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [SPAM] [Vantage] Employee File Birthdate Corruption
> >
> >
> >
> > Here's one for the group that I'll bet you've not heard before. I
> > discovered that any employee with a birtdate in the 1950's and
1960's
> > has been changed to 2050, etc... This absolutely is not any type
of
> > operator error since most of these birthdates have been set up for
> > years. I logged a call with Vantage two days ago but have not
heard a
> > peep from them. Just wondering if anyone else has experienced
> > something like this. This is very disturbing - what if Vantage
decided
> > to corrupt the employee rate dates - that would be a horrible
mess. We
> > are on v 8.03.404
> >
> >
> >
> >
> >
> > This e-mail and any attachments may contain confidential and
> > privileged information. If you are not the intended recipient,
> > please notify the sender immediately by return e-mail, delete this
> > e-mail and destroy any copies. Any dissemination or use of this
> > information by a person other than the intended recipient is
> > unauthorized and may be illegal.
> >
> > [Non-text portions of this message have been removed]
> >
>





[Non-text portions of this message have been removed]
10
Todd is on the right track. What happens here is there is a startup
parameter (in the mfgsys.pf) of -yy that defaults to 1970.



Any date put into the system before 1970 will end up in the 20xx
anything after in 19xx.



Ex: 1969 = 2069 1971 = 1971



So change -yy 1970 in the pf to earlier than the earliest birthdate
year.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of smj2cool
Sent: Friday, April 11, 2008 8:11 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Employee File Birthdate Corruption



Thanks for your replies. Since you so readily understood my issue
and a possible fix, I can only wonder why I haven't heard from
support yet. We did recently install a patch so perhaps that's the
cause.

Sue Jones

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , Todd
Caughey <caugheyt@...> wrote:
>
> If this is like 6.1 there is a Progress paramter for handling
century assumption on 2 digit years. We have ours set to 1929.
Perhaps this parameter got changed or overwritten in a patch
upgrade? I'm not familiar enough with 8.x to advise where to look
but this sounds like that parameter got hit.
> -Todd C.
>
>
> ________________________________
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of smj2cool
> Sent: Friday, April 11, 2008 7:39 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Employee File Birthdate Corruption
>
>
> Here's one for the group that I'll bet you've not heard before. I
> discovered that any employee with a birtdate in the 1950's and
1960's
> has been changed to 2050, etc... This absolutely is not any type of
> operator error since most of these birthdates have been set up for
> years. I logged a call with Vantage two days ago but have not heard
a
> peep from them. Just wondering if anyone else has experienced
> something like this. This is very disturbing - what if Vantage
decided
> to corrupt the employee rate dates - that would be a horrible mess.
We
> are on v 8.03.404
>
>
>
>
>
> [Non-text portions of this message have been removed]
>


--------------------------------------------------------

This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software Corporation or any other company within its group.


[Non-text portions of this message have been removed]