V 8.00.8xx upgrade to 8.00.812A-Record is being modified by another

Yahoo Archive
1
I reported this to Epicor 4 months ago and their response was this:

Major changes to tables and field formats (new and obsolete); thus
causing 'converted' data to have older version table/field format
structures attempting to map to the new table/field format
structures. The areas most prevelant are around Quote & Job Entry
pulling data in from Get Details (Quote, Part, Job, Method). If you
open the default help from Vantage and search by 'Format Changes'
or 'New Fields' you can view the magnitude of tables and field format
changes (new and old).

Here are a few I reported:
JobOper.CommentText
JobOper.RunQty
JobAsmbl.TLEMaterialCost
JobAsmbl.TLELaborCost
JobAsmbl.TLESetupCost

If you are on Vantage running Progress, you are in luck. They have a
dump and load program that 'cleans up' the data. However it may have
to be run several times to pass through the data.

For those on SQL, there is not an option to dump and load. You must
report each instance by clicking the details button to report the
table and field name it errors out on. I think they have most fixed
by the 404B service pack/patch. But there are a few more that didn't
get on that service pack and are slated for 405 & 406.

Thanks
Patty Buechler




--- In vantage@yahoogroups.com, "Linda Lowney" <llowney@...> wrote:
>
> We have the same problem since upgrading from 8 to 8.03 and I was
told
> that the problem was related to a change in the way Progress stores
a
> number.
>
>
>
> Sometimes it helps if you open the record, then save it immediately
> before trying to change anything. We had someone run a Progress
> program to fix the problem for the ones that are stubborn and will
not
> allow us to make a change. I'm pretty sure we tried the dump and
load
> route without any luck.
>
>
>
> Linda
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
We have the same problem since upgrading from 8 to 8.03 and I was told
that the problem was related to a change in the way Progress stores a
number.



Sometimes it helps if you open the record, then save it immediately
before trying to change anything. We had someone run a Progress
program to fix the problem for the ones that are stubborn and will not
allow us to make a change. I'm pretty sure we tried the dump and load
route without any luck.



Linda







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