8.03.403x - Job Entry: Record has been modified by another user

Yahoo Archive
1
All;

I have information on this error: Record has been modified by
another user....

Basically (in a nut shell) From Patch to Service Pack to Version,
Epicor changes the data formats of fields within tables. Most of the
issues are around numberic type fields, but the one I was reporting
on was JobOper.CommentText.

If you are Progress, Epicor recommends using a dump-n-load program
that scrubs the data as it loads back in and corrects the field
format variances. If you have any questions on that...call Epicor.

If you are SQL, you must capture the DETAILED error in a screen shot,
send them a copy of your DB...hope they can re-create the error, and
they will send you a new .r program that it to fix the error.




--- In vantage@yahoogroups.com, "pvolkert365" <pvolkert@...> wrote:
>
> We are on 403B, Progress. We have had the problem since going from
> 8.00 to 8.03.305. We have seen it in Payroll, Engineering
Workbench,
> PO Entry, and Quote Entry. The Payroll one was particularly bad
> because it happened every time to the same record, and we could not
> change a deduction we had to change. Epicor sent us a fix program,
> and it has been fine. We have done two dump & loads. Engineering
no
> longer gets it. PO Entry only gets it if the buyer approves a PO
and
> then tries to go right back in and make more changes. The worst
one
> we are seeing now is Quote Entry. We only have one Quote Entry
> person and he gets it all the time.
>
> -Peter
>
> --- In vantage@yahoogroups.com, "Paul V. Blais" <pblais@> wrote:
> >
> > This used to be an awful issue for us...Progress...now it is a
> nuisance.
> > We see it in PO Entry, Part Entry, and Job Entry, it really is an
> odd
> > issue.
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf
> > Of Todd Hofert
> > Sent: Tuesday, December 11, 2007 8:45 AM
> > To: vantage@yahoogroups.com
> > Subject: RE: [Vantage] 8.03.403x - Job Entry: Record has been
> modified
> > by another user....
> >
> >
> >
> > Patty,
> >
> > We are on 8.03.403C and we are almost plagued by this issue,
mainly
> in
> > Job Entry but occasionally in other areas. We are Progress and
have
> > listened to the suggestion by support that it is the result of a
> data
> > conversion from previous versions...we didn't convert from
previous
> > version. We did the recommended dump and load twice anyway with no
> > resolution. We have been asked to run black box software to
capture
> the
> > error because no one else has the issue nor can it be duplicated.
We
> > have done this and submitted the results to support with no
> resolution.
> > Right now we are dealing with it with the save early and save
often
> > mentality.
> >
> > Todd Hofert
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > [mailto:vantage@yahoogroups.com <mailto:vantage%
> 40yahoogroups.com> ] On
> > Behalf
> > Of bpbuechler
> > Sent: Tuesday, December 11, 2007 8:37 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] 8.03.403x - Job Entry: Record has been
modified
> by
> > another user....
> >
> > I would like to know of all customers that are on 8.03.403a, b, c
> or d
> >
> > How many of you are getting this error?
> > Are you on a SQL DB?
> > What was your resolution, if any?
> >
> > Thanks
> > Patty Buechler
> > UV Color, Inc.
> >
> > 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
I would like to know of all customers that are on 8.03.403a, b, c or d

How many of you are getting this error?
Are you on a SQL DB?
What was your resolution, if any?

Thanks
Patty Buechler
UV Color, Inc.
3
Patty,



We are on 8.03.403C and we are almost plagued by this issue, mainly in
Job Entry but occasionally in other areas. We are Progress and have
listened to the suggestion by support that it is the result of a data
conversion from previous versions...we didn't convert from previous
version. We did the recommended dump and load twice anyway with no
resolution. We have been asked to run black box software to capture the
error because no one else has the issue nor can it be duplicated. We
have done this and submitted the results to support with no resolution.
Right now we are dealing with it with the save early and save often
mentality.



Todd Hofert



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bpbuechler
Sent: Tuesday, December 11, 2007 8:37 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 8.03.403x - Job Entry: Record has been modified by
another user....



I would like to know of all customers that are on 8.03.403a, b, c or d

How many of you are getting this error?
Are you on a SQL DB?
What was your resolution, if any?

Thanks
Patty Buechler
UV Color, Inc.





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]
4
This used to be an awful issue for us...Progress...now it is a nuisance.
We see it in PO Entry, Part Entry, and Job Entry, it really is an odd
issue.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Hofert
Sent: Tuesday, December 11, 2007 8:45 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] 8.03.403x - Job Entry: Record has been modified
by another user....



Patty,

We are on 8.03.403C and we are almost plagued by this issue, mainly in
Job Entry but occasionally in other areas. We are Progress and have
listened to the suggestion by support that it is the result of a data
conversion from previous versions...we didn't convert from previous
version. We did the recommended dump and load twice anyway with no
resolution. We have been asked to run black box software to capture the
error because no one else has the issue nor can it be duplicated. We
have done this and submitted the results to support with no resolution.
Right now we are dealing with it with the save early and save often
mentality.

Todd Hofert

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of bpbuechler
Sent: Tuesday, December 11, 2007 8:37 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] 8.03.403x - Job Entry: Record has been modified by
another user....

I would like to know of all customers that are on 8.03.403a, b, c or d

How many of you are getting this error?
Are you on a SQL DB?
What was your resolution, if any?

Thanks
Patty Buechler
UV Color, Inc.

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]
5
> This used to be an awful issue for us...Progress...now it is a nuisance.
> We see it in PO Entry, Part Entry, and Job Entry, it really is an odd
> issue.

We would see it if someone printed a document before saving. The last print
time would change and that was enough to "dirty" the entire document header.
The frustrating part is "another user" is you.

When client-server computing started, this was a big issue. I have seen other
software companies get around it by segmenting the different fields into
different areas and only reject an update if the update was in the same area
as another. For example, if someone changes the Last Print Date in one area,
one should still safely be able to update another field that is not used in
that area. This reduces the collisions and that error. One would think that
since Epicor has already created the business objects and isolated the
database logic that this wouldn't be as difficult to implement.

Mark W.
6
Here is the response I got back in the EpicWeb Forum:

The ERROR: Record has been modified by another user.... can stem
from two places.

1) The software now does "Optimistic Locking". Meaning if you and
I call up the same record and I make a modification to that record
and save that record, when you try to save the record, you will get
that message. You will need to refresh and try again. This is both
SQL and Progress.

2) This message can also appear for some cusotmers that entered data
when they were on a specific patch level. There was a problem where
data entered (typically numeric) where you would enter a 1.0 but the
record was written as a 1.
So when the problem was fixed and the record was called up again,
again you would see a 1.0 on your screen, but when a save was
attempted, the check that is performed to verify the record has not
has changed but actaully sees a difference between the 1.0 and a 1
and you get the message. This is for a Progress database only.

The resolution for the second scenario is to dump and load the
Progress database. This process dumps all of the data out of the
database to an Ascii text file. Then upon reload, that data element
is compaired to the data dictionary and will be corrected.

Another plus of doing a dump and load for a Progress database is it
defragments the data and can significantly increase performance
depending on the age of the database.

If you have this issue and can reproduce the error just by opening a
record and pressing the Save button, then a dump and load is for you.

If it only happens occassionaly and never on the same record, then it
is probably optimistic locking and a normal error message.

Thanks
Patty
--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> > This used to be an awful issue for us...Progress...now it is a
nuisance.
> > We see it in PO Entry, Part Entry, and Job Entry, it really is an
odd
> > issue.
>
> We would see it if someone printed a document before saving. The
last print
> time would change and that was enough to "dirty" the entire
document header.
> The frustrating part is "another user" is you.
>
> When client-server computing started, this was a big issue. I have
seen other
> software companies get around it by segmenting the different fields
into
> different areas and only reject an update if the update was in the
same area
> as another. For example, if someone changes the Last Print Date in
one area,
> one should still safely be able to update another field that is not
used in
> that area. This reduces the collisions and that error. One would
think that
> since Epicor has already created the business objects and isolated
the
> database logic that this wouldn't be as difficult to implement.
>
> Mark W.
>
7
We are on 403B, Progress. We have had the problem since going from
8.00 to 8.03.305. We have seen it in Payroll, Engineering Workbench,
PO Entry, and Quote Entry. The Payroll one was particularly bad
because it happened every time to the same record, and we could not
change a deduction we had to change. Epicor sent us a fix program,
and it has been fine. We have done two dump & loads. Engineering no
longer gets it. PO Entry only gets it if the buyer approves a PO and
then tries to go right back in and make more changes. The worst one
we are seeing now is Quote Entry. We only have one Quote Entry
person and he gets it all the time.

-Peter

--- In vantage@yahoogroups.com, "Paul V. Blais" <pblais@...> wrote:
>
> This used to be an awful issue for us...Progress...now it is a
nuisance.
> We see it in PO Entry, Part Entry, and Job Entry, it really is an
odd
> issue.
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of Todd Hofert
> Sent: Tuesday, December 11, 2007 8:45 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] 8.03.403x - Job Entry: Record has been
modified
> by another user....
>
>
>
> Patty,
>
> We are on 8.03.403C and we are almost plagued by this issue, mainly
in
> Job Entry but occasionally in other areas. We are Progress and have
> listened to the suggestion by support that it is the result of a
data
> conversion from previous versions...we didn't convert from previous
> version. We did the recommended dump and load twice anyway with no
> resolution. We have been asked to run black box software to capture
the
> error because no one else has the issue nor can it be duplicated. We
> have done this and submitted the results to support with no
resolution.
> Right now we are dealing with it with the save early and save often
> mentality.
>
> Todd Hofert
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> ] On
> Behalf
> Of bpbuechler
> Sent: Tuesday, December 11, 2007 8:37 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] 8.03.403x - Job Entry: Record has been modified
by
> another user....
>
> I would like to know of all customers that are on 8.03.403a, b, c
or d
>
> How many of you are getting this error?
> Are you on a SQL DB?
> What was your resolution, if any?
>
> Thanks
> Patty Buechler
> UV Color, Inc.
>
> 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]
>
8
Yes we get the same error.

We are running on SQL server. The response from our consultants is
that this is a SQL server issue. We are not live yet, so hopefully
the problem will not become more persistent later.

We have the same problem with Kronos Timekeeper occasionally. Kronos
also states that this is a SQL server issue.


--- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@...> wrote:
>
> I would like to know of all customers that are on 8.03.403a, b, c
or d
>
> How many of you are getting this error?
> Are you on a SQL DB?
> What was your resolution, if any?
>
> Thanks
> Patty Buechler
> UV Color, Inc.
>
9
403b progress, no resolution yet.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of lapulsifer
Sent: Tuesday, December 11, 2007 2:30 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: 8.03.403x - Job Entry: Record has been modified
by another user....



Yes we get the same error.

We are running on SQL server. The response from our consultants is
that this is a SQL server issue. We are not live yet, so hopefully
the problem will not become more persistent later.

We have the same problem with Kronos Timekeeper occasionally. Kronos
also states that this is a SQL server issue.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"bpbuechler" <pbuechler@...> wrote:
>
> I would like to know of all customers that are on 8.03.403a, b, c
or d
>
> How many of you are getting this error?
> Are you on a SQL DB?
> What was your resolution, if any?
>
> Thanks
> Patty Buechler
> UV Color, Inc.
>





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