Serious Bug in Patch 305 - Part Maint

Yahoo Archive
1
Based on my testing you CAN delete operations & renumber. The only
constraint is don't use the "Resequence" command. If you delete and
renumber manually you should be ok. At least on the two trials I did it
worked out ok....


Rick Joslin
V-S Industries


________________________________________________________________________
________________________________________________________________________

Message: 2
Date: Wed, 15 Jan 2003 14:29:02 -0500
From: "Kathy Hambleton" <kbh@...>
Subject: RE: Re: Serious Bug in Patch 305 - Part Maint.

Same here!

-----Original Message-----
From: Robert Bruton [mailto:bob@...]
Sent: Wednesday, January 15, 2003 11:40 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Serious Bug in Patch 305 - Part Maint.


I've had the same problem. I've also seen negative sequence numbers. Don't
delete sequences. Don't renumber. Sure would like to know when the fix is
supposed to be out. I've got some really messed up BOMs that I can't seem
to fix.

Bob Bruton
Entek Corp.


We have hit the same problem you are having with the 305 patch. In fact I
have already been in touch with Vantage Support about this. They tell me
that patch 307 is suppose to fix this. When they tried to duplicate the
problem there, they were unable to. Then she said she was running patch 307
not released to the public
yet.


James Piper
Meco Inc
Paris, IL



--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> Since applying patch 305 last weekend we have encountered further
serious problems in Engineering Workbench and the maintenance of Part
BOMs. At patch 211 there was an issue with deleting operations and
resequencing (thus re-using a oper sequence number) which caused in
infinite loop on part check-in and the PC would hang. The workaround
was to not resequence or re-use a sequence number.
>
> Now in 305 we can not delete operations at all. The appear to
delete but when the part is checked-in but if it is checked out again
or examined in part tracker all the deleted sequences are back and
added to the end of operations AND renumbered relative to the last
sequence number that was there even if it was a deleted one. If we
had sequences 10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and
without resequencing) we should see 10, 20, 30, 60, 70 but the part
comes back as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two
deleted operations. We we had deleted 50 thru 70 they would come
back as 80-100.
>
> In short, there is no way to delete an operation and if we try to
the part's BOM gets seriously messed up. Support is aware of this
(SCR 5292 and former SCR 4608) but due to the seriousness of the
issue and not having seen it mentioned much here I figured it is
something other sites might be interested in knowing about.
Especially if contemplating applying patch 305. Perhaps others at
this patch level are seeing different symptoms which could assist
development in getting this fixed as quickly as possible.
>
> At the moment our only workaround is to replace operations to be
deleted with a bogus operation number called "DELETED OPER" as a sort
of place holder and then take it out when the job is created.
>
> -
2
Since applying patch 305 last weekend we have encountered further serious problems in Engineering Workbench and the maintenance of Part BOMs. At patch 211 there was an issue with deleting operations and resequencing (thus re-using a oper sequence number) which caused in infinite loop on part check-in and the PC would hang. The workaround was to not resequence or re-use a sequence number.

Now in 305 we can not delete operations at all. The appear to delete but when the part is checked-in but if it is checked out again or examined in part tracker all the deleted sequences are back and added to the end of operations AND renumbered relative to the last sequence number that was there even if it was a deleted one. If we had sequences 10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and without resequencing) we should see 10, 20, 30, 60, 70 but the part comes back as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two deleted operations. We we had deleted 50 thru 70 they would come back as 80-100.

In short, there is no way to delete an operation and if we try to the part's BOM gets seriously messed up. Support is aware of this (SCR 5292 and former SCR 4608) but due to the seriousness of the issue and not having seen it mentioned much here I figured it is something other sites might be interested in knowing about. Especially if contemplating applying patch 305. Perhaps others at this patch level are seeing different symptoms which could assist development in getting this fixed as quickly as possible.

At the moment our only workaround is to replace operations to be deleted with a bogus operation number called "DELETED OPER" as a sort of place holder and then take it out when the job is created.

-Todd Caughey
Havey Vogel Mfg. Co.





[Non-text portions of this message have been removed]
3
We have hit the same problem you are having with the 305 patch.
In fact I have already been in touch with Vantage Support about this.
They tell me that patch 307 is suppose to fix this.
When they tried to duplicate the problem there, they were unable to.
Then she said she was running patch 307 not released to the public
yet.


James Piper
Meco Inc
Paris, IL



--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> Since applying patch 305 last weekend we have encountered further
serious problems in Engineering Workbench and the maintenance of Part
BOMs. At patch 211 there was an issue with deleting operations and
resequencing (thus re-using a oper sequence number) which caused in
infinite loop on part check-in and the PC would hang. The workaround
was to not resequence or re-use a sequence number.
>
> Now in 305 we can not delete operations at all. The appear to
delete but when the part is checked-in but if it is checked out again
or examined in part tracker all the deleted sequences are back and
added to the end of operations AND renumbered relative to the last
sequence number that was there even if it was a deleted one. If we
had sequences 10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and
without resequencing) we should see 10, 20, 30, 60, 70 but the part
comes back as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two
deleted operations. We we had deleted 50 thru 70 they would come
back as 80-100.
>
> In short, there is no way to delete an operation and if we try to
the part's BOM gets seriously messed up. Support is aware of this
(SCR 5292 and former SCR 4608) but due to the seriousness of the
issue and not having seen it mentioned much here I figured it is
something other sites might be interested in knowing about.
Especially if contemplating applying patch 305. Perhaps others at
this patch level are seeing different symptoms which could assist
development in getting this fixed as quickly as possible.
>
> At the moment our only workaround is to replace operations to be
deleted with a bogus operation number called "DELETED OPER" as a sort
of place holder and then take it out when the job is created.
>
> -
4
I've had the same problem. I've also seen negative sequence numbers. Don't
delete sequences. Don't renumber.
Sure would like to know when the fix is supposed to be out. I've got some
really messed up BOMs that I can't seem to fix.

Bob Bruton
Entek Corp.


We have hit the same problem you are having with the 305 patch.
In fact I have already been in touch with Vantage Support about this.
They tell me that patch 307 is suppose to fix this.
When they tried to duplicate the problem there, they were unable to.
Then she said she was running patch 307 not released to the public
yet.


James Piper
Meco Inc
Paris, IL



--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> Since applying patch 305 last weekend we have encountered further
serious problems in Engineering Workbench and the maintenance of Part
BOMs. At patch 211 there was an issue with deleting operations and
resequencing (thus re-using a oper sequence number) which caused in
infinite loop on part check-in and the PC would hang. The workaround
was to not resequence or re-use a sequence number.
>
> Now in 305 we can not delete operations at all. The appear to
delete but when the part is checked-in but if it is checked out again
or examined in part tracker all the deleted sequences are back and
added to the end of operations AND renumbered relative to the last
sequence number that was there even if it was a deleted one. If we
had sequences 10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and
without resequencing) we should see 10, 20, 30, 60, 70 but the part
comes back as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two
deleted operations. We we had deleted 50 thru 70 they would come
back as 80-100.
>
> In short, there is no way to delete an operation and if we try to
the part's BOM gets seriously messed up. Support is aware of this
(SCR 5292 and former SCR 4608) but due to the seriousness of the
issue and not having seen it mentioned much here I figured it is
something other sites might be interested in knowing about.
Especially if contemplating applying patch 305. Perhaps others at
this patch level are seeing different symptoms which could assist
development in getting this fixed as quickly as possible.
>
> At the moment our only workaround is to replace operations to be
deleted with a bogus operation number called "DELETED OPER" as a sort
of place holder and then take it out when the job is created.
>
> -




[Non-text portions of this message have been removed]
5
Good to hear it might be fixed. Now if 307 can pass QA and get released. I'd like to have it NOW but also would like it to not break something else. At the moment not sure which I want more. Looks like 307 will be a patch I won't have to think twice about applying as soon as I can get it because the way things are now it would be hard to be worse.
-Todd C.

-----Original Message-----
From: meco_inc_paris <admin@...> [mailto:admin@...]
Sent: Wednesday, January 15, 2003 10:17 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Serious Bug in Patch 305 - Part Maint.


We have hit the same problem you are having with the 305 patch.
In fact I have already been in touch with Vantage Support about this.
They tell me that patch 307 is suppose to fix this.
When they tried to duplicate the problem there, they were unable to.
Then she said she was running patch 307 not released to the public
yet.


James Piper
Meco Inc
Paris, IL



--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> Since applying patch 305 last weekend we have encountered further
serious problems in Engineering Workbench and the maintenance of Part
BOMs. At patch 211 there was an issue with deleting operations and
resequencing (thus re-using a oper sequence number) which caused in
infinite loop on part check-in and the PC would hang. The workaround
was to not resequence or re-use a sequence number.
>
> Now in 305 we can not delete operations at all. The appear to
delete but when the part is checked-in but if it is checked out again
or examined in part tracker all the deleted sequences are back and
added to the end of operations AND renumbered relative to the last
sequence number that was there even if it was a deleted one. If we
had sequences 10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and
without resequencing) we should see 10, 20, 30, 60, 70 but the part
comes back as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two
deleted operations. We we had deleted 50 thru 70 they would come
back as 80-100.
>
> In short, there is no way to delete an operation and if we try to
the part's BOM gets seriously messed up. Support is aware of this
(SCR 5292 and former SCR 4608) but due to the seriousness of the
issue and not having seen it mentioned much here I figured it is
something other sites might be interested in knowing about.
Especially if contemplating applying patch 305. Perhaps others at
this patch level are seeing different symptoms which could assist
development in getting this fixed as quickly as possible.
>
> At the moment our only workaround is to replace operations to be
deleted with a bogus operation number called "DELETED OPER" as a sort
of place holder and then take it out when the job is created.
>
> -



Yahoo! Groups Sponsor

ADVERTISEMENT
<http://rd.yahoo.com/M=241773.2861422.4212389.1925585/D=egroupweb/S=1705007183:HM/A=1394044/R=0/*http://www.hgtv.com/hgtv/pac_ctnt/text/0,,HGTV_3936_5802,FF.html> HGTV Dream Home Giveaway
<http://us.adserver.yahoo.com/l?M=241773.2861422.4212389.1925585/D=egroupmail/S=:HM/A=1394044/rand=894894509>

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> .




[Non-text portions of this message have been removed]
6
Same here!

-----Original Message-----
From: Robert Bruton [mailto:bob@...]
Sent: Wednesday, January 15, 2003 11:40 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Serious Bug in Patch 305 - Part Maint.


I've had the same problem. I've also seen negative sequence numbers.
Don't
delete sequences. Don't renumber.
Sure would like to know when the fix is supposed to be out. I've got
some
really messed up BOMs that I can't seem to fix.

Bob Bruton
Entek Corp.


We have hit the same problem you are having with the 305 patch.
In fact I have already been in touch with Vantage Support about this.
They tell me that patch 307 is suppose to fix this.
When they tried to duplicate the problem there, they were unable to.
Then she said she was running patch 307 not released to the public
yet.


James Piper
Meco Inc
Paris, IL



--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> Since applying patch 305 last weekend we have encountered further
serious problems in Engineering Workbench and the maintenance of Part
BOMs. At patch 211 there was an issue with deleting operations and
resequencing (thus re-using a oper sequence number) which caused in
infinite loop on part check-in and the PC would hang. The workaround
was to not resequence or re-use a sequence number.
>
> Now in 305 we can not delete operations at all. The appear to
delete but when the part is checked-in but if it is checked out again
or examined in part tracker all the deleted sequences are back and
added to the end of operations AND renumbered relative to the last
sequence number that was there even if it was a deleted one. If we
had sequences 10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and
without resequencing) we should see 10, 20, 30, 60, 70 but the part
comes back as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two
deleted operations. We we had deleted 50 thru 70 they would come
back as 80-100.
>
> In short, there is no way to delete an operation and if we try to
the part's BOM gets seriously messed up. Support is aware of this
(SCR 5292 and former SCR 4608) but due to the seriousness of the
issue and not having seen it mentioned much here I figured it is
something other sites might be interested in knowing about.
Especially if contemplating applying patch 305. Perhaps others at
this patch level are seeing different symptoms which could assist
development in getting this fixed as quickly as possible.
>
> At the moment our only workaround is to replace operations to be
deleted with a bogus operation number called "DELETED OPER" as a sort
of place holder and then take it out when the job is created.
>
> -




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



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
7
I just noticed something similiar yesterday. I had to delete the whole
rev and recreate it. I think the initial problem was created by the
earlier Engineering Workbench resequencing issue


Dan Tisone
IS / IT Consultant
dan.tisone@...
(949) 440-3685 x148
Cel (714) 227-4173




-----Original Message-----
From: Todd Caughey [mailto:caugheyt@...]
Sent: Wednesday, January 15, 2003 7:52 AM
To: Vantage@yahoogroups.com
Subject: [Vantage] Serious Bug in Patch 305 - Part Maint.


Since applying patch 305 last weekend we have encountered further
serious problems in Engineering Workbench and the maintenance of Part
BOMs. At patch 211 there was an issue with deleting operations and
resequencing (thus re-using a oper sequence number) which caused in
infinite loop on part check-in and the PC would hang. The workaround
was to not resequence or re-use a sequence number.

Now in 305 we can not delete operations at all. The appear to delete
but when the part is checked-in but if it is checked out again or
examined in part tracker all the deleted sequences are back and added to
the end of operations AND renumbered relative to the last sequence
number that was there even if it was a deleted one. If we had sequences
10, 20, 30, 40, 50, 60, 70 and we deleted 40 & 50 (and without
resequencing) we should see 10, 20, 30, 60, 70 but the part comes back
as 10, 20, 30, 60, 70, 80, 90 with 80 & 90 being the two deleted
operations. We we had deleted 50 thru 70 they would come back as
80-100.

In short, there is no way to delete an operation and if we try to the
part's BOM gets seriously messed up. Support is aware of this (SCR 5292
and former SCR 4608) but due to the seriousness of the issue and not
having seen it mentioned much here I figured it is something other sites
might be interested in knowing about. Especially if contemplating
applying patch 305. Perhaps others at this patch level are seeing
different symptoms which could assist development in getting this fixed
as quickly as possible.

At the moment our only workaround is to replace operations to be deleted
with a bogus operation number called "DELETED OPER" as a sort of place
holder and then take it out when the job is created.

-Todd Caughey
Havey Vogel Mfg. Co.





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



Yahoo! Groups Sponsor

ADVERTISEMENT

<http://rd.yahoo.com/M=241773.2861420.4212388.1925585/D=egroupweb/S=1705
007183:HM/A=1394045/R=0/*http://www.hgtv.com/hgtv/pac_ctnt/text/0,,HGTV_
3936_5802,FF.html> HGTV Dream Home Giveaway

<http://us.adserver.yahoo.com/l?M=241773.2861420.4212388.1925585/D=egrou
pmail/S=:HM/A=1394045/rand=995576388>

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .




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