{Disarmed} Looking for those who have upgraded fro

I would be very cautious of Vantage version 9. While the final
release plan has not been published, I anticipate this version while
using the same technology to have significant changes related to
Epicor convergence plan. Fixes here are likely to be because of the
significant changes involved.

--- In vantage@yahoogroups.com, Greg Gillette <ggillette@...> wrote:
>
> I agree pretty much with this.. what I don't agree with though is
being told version 9 for some fixes. I would really like to see our
current version fixed and not have to tell my users that we have to go
through another major release upgrade just to fix the current version.
Who knows what will break in the process. We are still trying to get
the dust to settle from our 6.1 -> 8.03 upgrade and that was 8 months
ago. I am fairly certain I would dragged outside and pummeled for
even hinting about an upgrade within the next couple of years.
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of Thomas Rose
> Sent: Monday, May 12, 2008 2:13 PM
> To: vantage@yahoogroups.com
> Subject: RE: {Disarmed} Re: [Vantage] Re: Looking for those who have
upgraded from 305 to 404
>
> I can't speak to the actual Epicor practices, but I have experienced
this sort of thing in a company I used to work for. That company
developed software for large financial institutions. Although they
would test the systems before release, their attitude was "Catch and
fix 80% of the bugs and let the clients find the rest." That actually
worked fairly well. In one sense, it is hard to do it any other way.
Unless you are actually running a number of manufacturing companies
and employing a variety of different internal practices, you will find
it hard to imagine all the scenarios that need to be tested. Epicor
is a software company, not a manufacturing company. Thus, even if
they employ many manufacturing experts, they are inherently incapable
of finding all the bugs before a release. Now, as a user, I might
expect them to catch and fix more bugs than they do, but I do
understand that they cannot catch 100% of the bugs.
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of Robert Brown
> Sent: Monday, May 12, 2008 8:55 AM
> To: vantage@yahoogroups.com
> Subject: {Disarmed} Re: [Vantage] Re: Looking for those who have
upgraded from 305 to 404
>
>
> I share your frustration but I have little doubt they DO test before
releasing.
>
> I just think their internal quality standards for allowing a release
to go out to users is very low. (Better to make your deadline and
release known bugs than to miss it.)
>
> Typical of a large corporation with the 'wrong' incentives in place
for employees and management.
>
> I suspect as long as an aplication doesn't completely bomb out, the
release goes out ('on schedule') no matter what the fallout is.
>
> Rob Brown
>
> --- On Mon, 5/12/08, clive.1972
<clive.1972@...<mailto:clive.1972%40yahoo.com>> wrote:
>
> From: clive.1972 <clive.1972@...<mailto:clive.1972%40yahoo.com>>
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Date: Monday, May 12, 2008, 10:58 AM
>
> This is the one thing that bugs me with Vantage, the constant
> patching/updating.
>
> It smacks of Epicor not thoroughly testing new versions before
> releasing them to the general public...
>
> --- In vantage@yahoogroups .com, Greg Gillette <ggillette@ ..> wrote:
> >
> > .405 should be within a couple weeks last I heard.
> >
> > We have fixes scheduled out to .408.. Was even told a couple of
> them would be version 9.
> >
> > -----Original Message-----
> > From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
> Behalf Of bw2868bond
> > Sent: Monday, May 12, 2008 10:39 AM
> > To: vantage@yahoogroups .com
> > Subject: [Vantage] Re: Looking for those who have upgraded from 305
> to 404
> >
> > Do you perhaps mean .405 ??
> >
> > --- In vantage@yahoogroups .com, "clive.1972" <clive.1972@ > wrote:
> > >
> > > We've got a nasty problem that will be resolved by 406, the person
> > > dealing with the support call was kind enough to give me an eta
> for
> > > it.
> > >
> > > Whether or not the eta will be met is a different matter...
> > >
> > > --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ > wrote:
> > > >
> > > > I'm curious how you know ETA for 406?
> > > > Epicor technicians wouldn't tell us anything, even when they
> > > replied to tell us that an open ticket is solved by .406.
> > > >
> > > >
> > > >
> > > > ----- Original Message ----
> > > > From: clive.1972 <clive.1972@ >
> > > > To: vantage@yahoogroups .com
> > > > Sent: Monday, May 12, 2008 3:59:23 AM
> > > > Subject: [Vantage] Re: Looking for those who have upgraded from
> > 305
> > > to 404
> > > >
> > > >
> > > > Definately watch out for the 'Plant Cost ID' !.
> > > >
> > > > The upgrade cleared ours and we went for two weeks without
> a 'MTL
> > > > Unit Cost' being assigne dto jobs.
> > > >
> > > > Epicor are aware that this can occur and they have a fix for it
> > so
> > > > it's not the end of the world but can make things difficult.
> > > >
> > > > Also setup a test server using something like VMware Server and
> > > give
> > > > your upgraded data test after test after test, we've had many
> > > > problems post upgrade from .305 to .404
> > > >
> > > > FYI .406 is coming out at the end of June so you may want to
> > > postpone
> > > > your upgrade until then as once again it provides many fixes to
> > > > Epicor's buggy software ;)
> > > >
> > > > --- In vantage@yahoogroups .com, "Mark Wonsil"
> <mark_wonsil@ ...>
> > > wrote:
> > > > >
> > > > > > We are in the process of evaluating the 400 release in our
> > test
> > > > > > environment.
> > > > > >
> > > > > > For those of you that have completed the upgrade, any reason
> > we
> > > > should
> > > > > > not move forward? Anything we should watch out for?
> > > > >
> > > > > If you're using Sales Kits, DO NOT use multiple releases!!!
> > This
> > > > has screwed
> > > > > up our BookDtl table big time and it's our highest ranking
> > > support
> > > > call at the
> > > > > moment.
> > > > >
> > > > > Make sure your Plant ID has a default Cost ID AFTER the
> upgrade
> > > and
> > > > BEFORE you
> > > > > do any transactions.
> > > > >
> > > > > Test Serial Number out if you use them. Numeric only will not
> > let
> > > > you manually
> > > > > create old S/N formats if the format is different.
> > > > >
> > > > > Mark W.
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
> ____________ _________ _________ _________ _________ _________ _
> > > ____________ __
> > > > Be a better friend, newshound, and
> > > > know-it-all with Yahoo! Mobile. Try it now.
> > > http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> > > >
> > > > [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/ linksYahoo! Groups Links
> >
>
> __________________________________________________________
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>
>
> [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/linksYahoo! Groups Links
>
Hi all,

We are in the process of evaluating the 400 release in our test
environment.

For those of you that have completed the upgrade, any reason we should
not move forward? Anything we should watch out for?

Thanks,

Todd
> We are in the process of evaluating the 400 release in our test
> environment.
>
> For those of you that have completed the upgrade, any reason we should
> not move forward? Anything we should watch out for?

If you're using Sales Kits, DO NOT use multiple releases!!! This has screwed
up our BookDtl table big time and it's our highest ranking support call at the
moment.

Make sure your Plant ID has a default Cost ID AFTER the upgrade and BEFORE you
do any transactions.

Test Serial Number out if you use them. Numeric only will not let you manually
create old S/N formats if the format is different.

Mark W.
The following is a list of things we found in moving from 8.03.305l to
8.03.40x.



1. If you are using the product Configurator ensure you test it
thoroughly. We are stuck at 8.03.403d because the Configurator in 404 is
broken for us completely. We have always had some issues with it but it
becomes totally worthless in 404.
2. If you have very many customizations go through them very carefully,
especially Purchase Order Entry, Part Maintenance, and Sales Order Entry.
There was a schema change in 400 and some the base screen layouts changed.
Our custom fields became hidden in many instances. You should verify all
customizations and even personalizations (if possible) to get them to
function. Some personalizations may have to be deleted entirely.
3. Verify and test all BPM methods. They will probably work but some
may need to be verified before becoming usable.
4. Any queries using the Change Log will need to be redone as well.
The keys were modified from 305.
5. Test all custom Crystal reports using Crystal and resave them
because of the schema change.
6. We found issues with some of the ODBC reports we had. Not so much
with the reports themselves but the fact they would not consistently work
because of memory utilization on the server. I was forced to convert many
of the ODBC reports to BAQ Reports.
7. If you only go to 8.03.403d there is a huge performance issue within
AP Invoice entry. It has to do with retrieving the receipts when an invoice
is initially entered. You're A/P data entry personnel will let you know
very quickly. Support should be able to provide you with a patch. If not,
let me know as it is only one program they replaced.
8. Watch the utilization of Application Servers as they can get out of
hand. It is quite easy to run out of servers during the day.
9. SQL explorer for Open Edge goes away. I miss it because it was a
good tool for testing SQL statements and for a quick retrieval of data from
a table.
10. You will receive a decryption error in the server logs if the
password for the user id you are using to start the application servers is
over 7 characters long.
11. MRP processing will be 20% to 30% slower in 8.03.403x but will
improve again in 8.03.404x (not sure if everything lost is gained because I
have not gone with 8.03.404x on the live server which is a faster machine
than my test server).
12. There is a chance your application servers will not start if you
have the "# of Blocks in DB buffer" set above 200000 in your database
default configuration. It has to do with shared memory size and allocation.
My test server worked without a hitch and I only discovered this the weekend
I was upgrading my live server. I almost had to cancel the upgrade because
of it. I had to put "-shmegsize 128" in the "Other server arguments" in the
configuration. I had to find this on my own since support is not available
on the weekends when most of us IT people have to do our upgrades. I still
don't know why I had to do this on my live server and not my test server.
This is an OpenEdge 10.1b issue.



I can't think of any other negative issues at this point. I will admit
there were a few enhancements in 8.03.40x that are very useful.



1. Customization is much easier to manage.
2. BAQs seem to be faster and more efficient.
3. I had several users say the system seemed to be faster and more
responsive.
4. If you go to 8.03.404x there is the ability to directly call a
Service Connect Workflow using a BPM method. I wish I could get there
because it would save me a lot of custom programming.
5. I do find I get better support if I at least make an attempt to stay
current, especially with Patches.



Have fun,



Charles





_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
todd8800
Sent: Friday, May 09, 2008 12:58 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Looking for those who have upgraded from 305 to 404



Hi all,

We are in the process of evaluating the 400 release in our test
environment.

For those of you that have completed the upgrade, any reason we should
not move forward? Anything we should watch out for?

Thanks,

Todd





[Non-text portions of this message have been removed]
Definately watch out for the 'Plant Cost ID' !.

The upgrade cleared ours and we went for two weeks without a 'MTL
Unit Cost' being assigne dto jobs.

Epicor are aware that this can occur and they have a fix for it so
it's not the end of the world but can make things difficult.

Also setup a test server using something like VMware Server and give
your upgraded data test after test after test, we've had many
problems post upgrade from .305 to .404

FYI .406 is coming out at the end of June so you may want to postpone
your upgrade until then as once again it provides many fixes to
Epicor's buggy software ;)

--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> > We are in the process of evaluating the 400 release in our test
> > environment.
> >
> > For those of you that have completed the upgrade, any reason we
should
> > not move forward? Anything we should watch out for?
>
> If you're using Sales Kits, DO NOT use multiple releases!!! This
has screwed
> up our BookDtl table big time and it's our highest ranking support
call at the
> moment.
>
> Make sure your Plant ID has a default Cost ID AFTER the upgrade and
BEFORE you
> do any transactions.
>
> Test Serial Number out if you use them. Numeric only will not let
you manually
> create old S/N formats if the format is different.
>
> Mark W.
>
I'm curious how you know ETA for 406?
Epicor technicians wouldn't tell us anything, even when they replied to tell us that an open ticket is solved by .406.



----- Original Message ----
From: clive.1972 <clive.1972@...>
To: vantage@yahoogroups.com
Sent: Monday, May 12, 2008 3:59:23 AM
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to 404


Definately watch out for the 'Plant Cost ID' !.

The upgrade cleared ours and we went for two weeks without a 'MTL
Unit Cost' being assigne dto jobs.

Epicor are aware that this can occur and they have a fix for it so
it's not the end of the world but can make things difficult.

Also setup a test server using something like VMware Server and give
your upgraded data test after test after test, we've had many
problems post upgrade from .305 to .404

FYI .406 is coming out at the end of June so you may want to postpone
your upgrade until then as once again it provides many fixes to
Epicor's buggy software ;)

--- In vantage@yahoogroups .com, "Mark Wonsil" <mark_wonsil@ ...> wrote:
>
> > We are in the process of evaluating the 400 release in our test
> > environment.
> >
> > For those of you that have completed the upgrade, any reason we
should
> > not move forward? Anything we should watch out for?
>
> If you're using Sales Kits, DO NOT use multiple releases!!! This
has screwed
> up our BookDtl table big time and it's our highest ranking support
call at the
> moment.
>
> Make sure your Plant ID has a default Cost ID AFTER the upgrade and
BEFORE you
> do any transactions.
>
> Test Serial Number out if you use them. Numeric only will not let
you manually
> create old S/N formats if the format is different.
>
> Mark W.
>




____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Non-text portions of this message have been removed]
We've got a nasty problem that will be resolved by 406, the person
dealing with the support call was kind enough to give me an eta for
it.

Whether or not the eta will be met is a different matter...

--- In vantage@yahoogroups.com, Tony Hughes <thughes281@...> wrote:
>
> I'm curious how you know ETA for 406?
> Epicor technicians wouldn't tell us anything, even when they
replied to tell us that an open ticket is solved by .406.
>
>
>
> ----- Original Message ----
> From: clive.1972 <clive.1972@...>
> To: vantage@yahoogroups.com
> Sent: Monday, May 12, 2008 3:59:23 AM
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
>
>
> Definately watch out for the 'Plant Cost ID' !.
>
> The upgrade cleared ours and we went for two weeks without a 'MTL
> Unit Cost' being assigne dto jobs.
>
> Epicor are aware that this can occur and they have a fix for it so
> it's not the end of the world but can make things difficult.
>
> Also setup a test server using something like VMware Server and
give
> your upgraded data test after test after test, we've had many
> problems post upgrade from .305 to .404
>
> FYI .406 is coming out at the end of June so you may want to
postpone
> your upgrade until then as once again it provides many fixes to
> Epicor's buggy software ;)
>
> --- In vantage@yahoogroups .com, "Mark Wonsil" <mark_wonsil@ ...>
wrote:
> >
> > > We are in the process of evaluating the 400 release in our test
> > > environment.
> > >
> > > For those of you that have completed the upgrade, any reason we
> should
> > > not move forward? Anything we should watch out for?
> >
> > If you're using Sales Kits, DO NOT use multiple releases!!! This
> has screwed
> > up our BookDtl table big time and it's our highest ranking
support
> call at the
> > moment.
> >
> > Make sure your Plant ID has a default Cost ID AFTER the upgrade
and
> BEFORE you
> > do any transactions.
> >
> > Test Serial Number out if you use them. Numeric only will not let
> you manually
> > create old S/N formats if the format is different.
> >
> > Mark W.
> >
>
>
>
>
>
______________________________________________________________________
______________
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
> [Non-text portions of this message have been removed]
>
Do you perhaps mean .405 ??

--- In vantage@yahoogroups.com, "clive.1972" <clive.1972@...> wrote:
>
> We've got a nasty problem that will be resolved by 406, the person
> dealing with the support call was kind enough to give me an eta for
> it.
>
> Whether or not the eta will be met is a different matter...
>
> --- In vantage@yahoogroups.com, Tony Hughes <thughes281@> wrote:
> >
> > I'm curious how you know ETA for 406?
> > Epicor technicians wouldn't tell us anything, even when they
> replied to tell us that an open ticket is solved by .406.
> >
> >
> >
> > ----- Original Message ----
> > From: clive.1972 <clive.1972@>
> > To: vantage@yahoogroups.com
> > Sent: Monday, May 12, 2008 3:59:23 AM
> > Subject: [Vantage] Re: Looking for those who have upgraded from
305
> to 404
> >
> >
> > Definately watch out for the 'Plant Cost ID' !.
> >
> > The upgrade cleared ours and we went for two weeks without a 'MTL
> > Unit Cost' being assigne dto jobs.
> >
> > Epicor are aware that this can occur and they have a fix for it
so
> > it's not the end of the world but can make things difficult.
> >
> > Also setup a test server using something like VMware Server and
> give
> > your upgraded data test after test after test, we've had many
> > problems post upgrade from .305 to .404
> >
> > FYI .406 is coming out at the end of June so you may want to
> postpone
> > your upgrade until then as once again it provides many fixes to
> > Epicor's buggy software ;)
> >
> > --- In vantage@yahoogroups .com, "Mark Wonsil" <mark_wonsil@ ...>
> wrote:
> > >
> > > > We are in the process of evaluating the 400 release in our
test
> > > > environment.
> > > >
> > > > For those of you that have completed the upgrade, any reason
we
> > should
> > > > not move forward? Anything we should watch out for?
> > >
> > > If you're using Sales Kits, DO NOT use multiple releases!!!
This
> > has screwed
> > > up our BookDtl table big time and it's our highest ranking
> support
> > call at the
> > > moment.
> > >
> > > Make sure your Plant ID has a default Cost ID AFTER the upgrade
> and
> > BEFORE you
> > > do any transactions.
> > >
> > > Test Serial Number out if you use them. Numeric only will not
let
> > you manually
> > > create old S/N formats if the format is different.
> > >
> > > Mark W.
> > >
> >
> >
> >
> >
> >
>
______________________________________________________________________
> ______________
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile. Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> > [Non-text portions of this message have been removed]
> >
>
.405 should be within a couple weeks last I heard.

We have fixes scheduled out to .408.. Was even told a couple of them would be version 9.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of bw2868bond
Sent: Monday, May 12, 2008 10:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to 404

Do you perhaps mean .405 ??

--- In vantage@yahoogroups.com, "clive.1972" <clive.1972@...> wrote:
>
> We've got a nasty problem that will be resolved by 406, the person
> dealing with the support call was kind enough to give me an eta for
> it.
>
> Whether or not the eta will be met is a different matter...
>
> --- In vantage@yahoogroups.com, Tony Hughes <thughes281@> wrote:
> >
> > I'm curious how you know ETA for 406?
> > Epicor technicians wouldn't tell us anything, even when they
> replied to tell us that an open ticket is solved by .406.
> >
> >
> >
> > ----- Original Message ----
> > From: clive.1972 <clive.1972@>
> > To: vantage@yahoogroups.com
> > Sent: Monday, May 12, 2008 3:59:23 AM
> > Subject: [Vantage] Re: Looking for those who have upgraded from
305
> to 404
> >
> >
> > Definately watch out for the 'Plant Cost ID' !.
> >
> > The upgrade cleared ours and we went for two weeks without a 'MTL
> > Unit Cost' being assigne dto jobs.
> >
> > Epicor are aware that this can occur and they have a fix for it
so
> > it's not the end of the world but can make things difficult.
> >
> > Also setup a test server using something like VMware Server and
> give
> > your upgraded data test after test after test, we've had many
> > problems post upgrade from .305 to .404
> >
> > FYI .406 is coming out at the end of June so you may want to
> postpone
> > your upgrade until then as once again it provides many fixes to
> > Epicor's buggy software ;)
> >
> > --- In vantage@yahoogroups .com, "Mark Wonsil" <mark_wonsil@ ...>
> wrote:
> > >
> > > > We are in the process of evaluating the 400 release in our
test
> > > > environment.
> > > >
> > > > For those of you that have completed the upgrade, any reason
we
> > should
> > > > not move forward? Anything we should watch out for?
> > >
> > > If you're using Sales Kits, DO NOT use multiple releases!!!
This
> > has screwed
> > > up our BookDtl table big time and it's our highest ranking
> support
> > call at the
> > > moment.
> > >
> > > Make sure your Plant ID has a default Cost ID AFTER the upgrade
> and
> > BEFORE you
> > > do any transactions.
> > >
> > > Test Serial Number out if you use them. Numeric only will not
let
> > you manually
> > > create old S/N formats if the format is different.
> > >
> > > Mark W.
> > >
> >
> >
> >
> >
> >
>
______________________________________________________________________
> ______________
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile. Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> > [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/linksYahoo! Groups Links
I was told 405 is coming out at the end of this month.




"bw2868bond"
<bwalker@adcocirc
uits.com> To
Sent by: vantage@yahoogroups.com
vantage@yahoogrou cc
ps.com
Subject
[Vantage] Re: Looking for those who
05/12/2008 09:38 have upgraded from 305 to 404
AM


Please respond to
vantage@yahoogrou
ps.com











Do you perhaps mean .405 ??

--- In vantage@yahoogroups.com, "clive.1972" <clive.1972@...> wrote:
>
> We've got a nasty problem that will be resolved by 406, the person
> dealing with the support call was kind enough to give me an eta for
> it.
>
> Whether or not the eta will be met is a different matter...
>
> --- In vantage@yahoogroups.com, Tony Hughes <thughes281@> wrote:
> >
> > I'm curious how you know ETA for 406?
> > Epicor technicians wouldn't tell us anything, even when they
> replied to tell us that an open ticket is solved by .406.
> >
> >
> >
> > ----- Original Message ----
> > From: clive.1972 <clive.1972@>
> > To: vantage@yahoogroups.com
> > Sent: Monday, May 12, 2008 3:59:23 AM
> > Subject: [Vantage] Re: Looking for those who have upgraded from
305
> to 404
> >
> >
> > Definately watch out for the 'Plant Cost ID' !.
> >
> > The upgrade cleared ours and we went for two weeks without a 'MTL
> > Unit Cost' being assigne dto jobs.
> >
> > Epicor are aware that this can occur and they have a fix for it
so
> > it's not the end of the world but can make things difficult.
> >
> > Also setup a test server using something like VMware Server and
> give
> > your upgraded data test after test after test, we've had many
> > problems post upgrade from .305 to .404
> >
> > FYI .406 is coming out at the end of June so you may want to
> postpone
> > your upgrade until then as once again it provides many fixes to
> > Epicor's buggy software ;)
> >
> > --- In vantage@yahoogroups .com, "Mark Wonsil" <mark_wonsil@ ...>
> wrote:
> > >
> > > > We are in the process of evaluating the 400 release in our
test
> > > > environment.
> > > >
> > > > For those of you that have completed the upgrade, any reason
we
> > should
> > > > not move forward? Anything we should watch out for?
> > >
> > > If you're using Sales Kits, DO NOT use multiple releases!!!
This
> > has screwed
> > > up our BookDtl table big time and it's our highest ranking
> support
> > call at the
> > > moment.
> > >
> > > Make sure your Plant ID has a default Cost ID AFTER the upgrade
> and
> > BEFORE you
> > > do any transactions.
> > >
> > > Test Serial Number out if you use them. Numeric only will not
let
> > you manually
> > > create old S/N formats if the format is different.
> > >
> > > Mark W.
> > >
> >
> >
> >
> >
> >
>
__________________________________________________________
> ______________
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile. Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> > [Non-text portions of this message have been removed]
> >
>
Nope, definately .406 :)

--- In vantage@yahoogroups.com, "bw2868bond" <bwalker@...> wrote:
>
> Do you perhaps mean .405 ??
>
> --- In vantage@yahoogroups.com, "clive.1972" <clive.1972@> wrote:
> >
> > We've got a nasty problem that will be resolved by 406, the person
> > dealing with the support call was kind enough to give me an eta for
> > it.
> >
> > Whether or not the eta will be met is a different matter...
This is the one thing that bugs me with Vantage, the constant
patching/updating.

It smacks of Epicor not thoroughly testing new versions before
releasing them to the general public...


--- In vantage@yahoogroups.com, Greg Gillette <ggillette@...> wrote:
>
> .405 should be within a couple weeks last I heard.
>
> We have fixes scheduled out to .408.. Was even told a couple of
them would be version 9.
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of bw2868bond
> Sent: Monday, May 12, 2008 10:39 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
>
> Do you perhaps mean .405 ??
>
> --- In vantage@yahoogroups.com, "clive.1972" <clive.1972@> wrote:
> >
> > We've got a nasty problem that will be resolved by 406, the person
> > dealing with the support call was kind enough to give me an eta
for
> > it.
> >
> > Whether or not the eta will be met is a different matter...
> >
> > --- In vantage@yahoogroups.com, Tony Hughes <thughes281@> wrote:
> > >
> > > I'm curious how you know ETA for 406?
> > > Epicor technicians wouldn't tell us anything, even when they
> > replied to tell us that an open ticket is solved by .406.
> > >
> > >
> > >
> > > ----- Original Message ----
> > > From: clive.1972 <clive.1972@>
> > > To: vantage@yahoogroups.com
> > > Sent: Monday, May 12, 2008 3:59:23 AM
> > > Subject: [Vantage] Re: Looking for those who have upgraded from
> 305
> > to 404
> > >
> > >
> > > Definately watch out for the 'Plant Cost ID' !.
> > >
> > > The upgrade cleared ours and we went for two weeks without
a 'MTL
> > > Unit Cost' being assigne dto jobs.
> > >
> > > Epicor are aware that this can occur and they have a fix for it
> so
> > > it's not the end of the world but can make things difficult.
> > >
> > > Also setup a test server using something like VMware Server and
> > give
> > > your upgraded data test after test after test, we've had many
> > > problems post upgrade from .305 to .404
> > >
> > > FYI .406 is coming out at the end of June so you may want to
> > postpone
> > > your upgrade until then as once again it provides many fixes to
> > > Epicor's buggy software ;)
> > >
> > > --- In vantage@yahoogroups .com, "Mark Wonsil"
<mark_wonsil@ ...>
> > wrote:
> > > >
> > > > > We are in the process of evaluating the 400 release in our
> test
> > > > > environment.
> > > > >
> > > > > For those of you that have completed the upgrade, any reason
> we
> > > should
> > > > > not move forward? Anything we should watch out for?
> > > >
> > > > If you're using Sales Kits, DO NOT use multiple releases!!!
> This
> > > has screwed
> > > > up our BookDtl table big time and it's our highest ranking
> > support
> > > call at the
> > > > moment.
> > > >
> > > > Make sure your Plant ID has a default Cost ID AFTER the
upgrade
> > and
> > > BEFORE you
> > > > do any transactions.
> > > >
> > > > Test Serial Number out if you use them. Numeric only will not
> let
> > > you manually
> > > > create old S/N formats if the format is different.
> > > >
> > > > Mark W.
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>
______________________________________________________________________
> > ______________
> > > Be a better friend, newshound, and
> > > know-it-all with Yahoo! Mobile. Try it now.
> > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> > >
> > > [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/linksYahoo! Groups Links
>
I share your frustration but I have little doubt they DO test before releasing.

I just think their internal quality standards for allowing a release to go out to users is very low. (Better to make your deadline and release known bugs than to miss it.)

Typical of a large corporation with the 'wrong' incentives in place for employees and management.

I suspect as long as an aplication doesn't completely bomb out, the release goes out ('on schedule') no matter what the fallout is.

Rob Brown

--- On Mon, 5/12/08, clive.1972 <clive.1972@...> wrote:

From: clive.1972 <clive.1972@...>
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to 404
To: vantage@yahoogroups.com
Date: Monday, May 12, 2008, 10:58 AM






This is the one thing that bugs me with Vantage, the constant
patching/updating.

It smacks of Epicor not thoroughly testing new versions before
releasing them to the general public...

--- In vantage@yahoogroups .com, Greg Gillette <ggillette@. ..> wrote:
>
> .405 should be within a couple weeks last I heard.
>
> We have fixes scheduled out to .408.. Was even told a couple of
them would be version 9.
>
> -----Original Message-----
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf Of bw2868bond
> Sent: Monday, May 12, 2008 10:39 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
>
> Do you perhaps mean .405 ??
>
> --- In vantage@yahoogroups .com, "clive.1972" <clive.1972@ > wrote:
> >
> > We've got a nasty problem that will be resolved by 406, the person
> > dealing with the support call was kind enough to give me an eta
for
> > it.
> >
> > Whether or not the eta will be met is a different matter...
> >
> > --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ > wrote:
> > >
> > > I'm curious how you know ETA for 406?
> > > Epicor technicians wouldn't tell us anything, even when they
> > replied to tell us that an open ticket is solved by .406.
> > >
> > >
> > >
> > > ----- Original Message ----
> > > From: clive.1972 <clive.1972@ >
> > > To: vantage@yahoogroups .com
> > > Sent: Monday, May 12, 2008 3:59:23 AM
> > > Subject: [Vantage] Re: Looking for those who have upgraded from
> 305
> > to 404
> > >
> > >
> > > Definately watch out for the 'Plant Cost ID' !.
> > >
> > > The upgrade cleared ours and we went for two weeks without
a 'MTL
> > > Unit Cost' being assigne dto jobs.
> > >
> > > Epicor are aware that this can occur and they have a fix for it
> so
> > > it's not the end of the world but can make things difficult.
> > >
> > > Also setup a test server using something like VMware Server and
> > give
> > > your upgraded data test after test after test, we've had many
> > > problems post upgrade from .305 to .404
> > >
> > > FYI .406 is coming out at the end of June so you may want to
> > postpone
> > > your upgrade until then as once again it provides many fixes to
> > > Epicor's buggy software ;)
> > >
> > > --- In vantage@yahoogroups .com, "Mark Wonsil"
<mark_wonsil@ ...>
> > wrote:
> > > >
> > > > > We are in the process of evaluating the 400 release in our
> test
> > > > > environment.
> > > > >
> > > > > For those of you that have completed the upgrade, any reason
> we
> > > should
> > > > > not move forward? Anything we should watch out for?
> > > >
> > > > If you're using Sales Kits, DO NOT use multiple releases!!!
> This
> > > has screwed
> > > > up our BookDtl table big time and it's our highest ranking
> > support
> > > call at the
> > > > moment.
> > > >
> > > > Make sure your Plant ID has a default Cost ID AFTER the
upgrade
> > and
> > > BEFORE you
> > > > do any transactions.
> > > >
> > > > Test Serial Number out if you use them. Numeric only will not
> let
> > > you manually
> > > > create old S/N formats if the format is different.
> > > >
> > > > Mark W.
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>
____________ _________ _________ _________ _________ _________ _
> > ____________ __
> > > Be a better friend, newshound, and
> > > know-it-all with Yahoo! Mobile. Try it now.
> > http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> > >
> > > [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/ linksYahoo! Groups Links
>
















____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
There are reasons for the constant updating...

1. Wanting to be the first ERP on .Net... it went out way too soon. Epicor has learned from this... more beta clients running on new code before it's released to the rest of us.

2. Integration with other packages... a constant uphill battle.

3. Wanting to consolidate all their ERP packages on Vantage. This is good and bad. Good as we're on their flagship product, bad because they're adding all the features of those other packages. This means some of our pet peeves wait.

Perhaps Epicor 9 means they're finally done with 3.

----- Original Message -----
From: "clive.1972" <clive.1972@...>
To: <vantage@yahoogroups.com>
Sent: Monday, May 12, 2008 7:58 AM
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to 404


This is the one thing that bugs me with Vantage, the constant patching/updating.

It smacks of Epicor not thoroughly testing new versions before releasing them to the general public...

[Non-text portions of this message have been removed]
I can't speak to the actual Epicor practices, but I have experienced this sort of thing in a company I used to work for. That company developed software for large financial institutions. Although they would test the systems before release, their attitude was "Catch and fix 80% of the bugs and let the clients find the rest." That actually worked fairly well. In one sense, it is hard to do it any other way. Unless you are actually running a number of manufacturing companies and employing a variety of different internal practices, you will find it hard to imagine all the scenarios that need to be tested. Epicor is a software company, not a manufacturing company. Thus, even if they employ many manufacturing experts, they are inherently incapable of finding all the bugs before a release. Now, as a user, I might expect them to catch and fix more bugs than they do, but I do understand that they cannot catch 100% of the bugs.

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Robert Brown
Sent: Monday, May 12, 2008 8:55 AM
To: vantage@yahoogroups.com
Subject: {Disarmed} Re: [Vantage] Re: Looking for those who have upgraded from 305 to 404


I share your frustration but I have little doubt they DO test before releasing.

I just think their internal quality standards for allowing a release to go out to users is very low. (Better to make your deadline and release known bugs than to miss it.)

Typical of a large corporation with the 'wrong' incentives in place for employees and management.

I suspect as long as an aplication doesn't completely bomb out, the release goes out ('on schedule') no matter what the fallout is.

Rob Brown

--- On Mon, 5/12/08, clive.1972 <clive.1972@...<mailto:clive.1972%40yahoo.com>> wrote:

From: clive.1972 <clive.1972@...<mailto:clive.1972%40yahoo.com>>
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to 404
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Date: Monday, May 12, 2008, 10:58 AM

This is the one thing that bugs me with Vantage, the constant
patching/updating.

It smacks of Epicor not thoroughly testing new versions before
releasing them to the general public...

--- In vantage@yahoogroups .com, Greg Gillette <ggillette@. ..> wrote:
>
> .405 should be within a couple weeks last I heard.
>
> We have fixes scheduled out to .408.. Was even told a couple of
them would be version 9.
>
> -----Original Message-----
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf Of bw2868bond
> Sent: Monday, May 12, 2008 10:39 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
>
> Do you perhaps mean .405 ??
>
> --- In vantage@yahoogroups .com, "clive.1972" <clive.1972@ > wrote:
> >
> > We've got a nasty problem that will be resolved by 406, the person
> > dealing with the support call was kind enough to give me an eta
for
> > it.
> >
> > Whether or not the eta will be met is a different matter...
> >
> > --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ > wrote:
> > >
> > > I'm curious how you know ETA for 406?
> > > Epicor technicians wouldn't tell us anything, even when they
> > replied to tell us that an open ticket is solved by .406.
> > >
> > >
> > >
> > > ----- Original Message ----
> > > From: clive.1972 <clive.1972@ >
> > > To: vantage@yahoogroups .com
> > > Sent: Monday, May 12, 2008 3:59:23 AM
> > > Subject: [Vantage] Re: Looking for those who have upgraded from
> 305
> > to 404
> > >
> > >
> > > Definately watch out for the 'Plant Cost ID' !.
> > >
> > > The upgrade cleared ours and we went for two weeks without
a 'MTL
> > > Unit Cost' being assigne dto jobs.
> > >
> > > Epicor are aware that this can occur and they have a fix for it
> so
> > > it's not the end of the world but can make things difficult.
> > >
> > > Also setup a test server using something like VMware Server and
> > give
> > > your upgraded data test after test after test, we've had many
> > > problems post upgrade from .305 to .404
> > >
> > > FYI .406 is coming out at the end of June so you may want to
> > postpone
> > > your upgrade until then as once again it provides many fixes to
> > > Epicor's buggy software ;)
> > >
> > > --- In vantage@yahoogroups .com, "Mark Wonsil"
<mark_wonsil@ ...>
> > wrote:
> > > >
> > > > > We are in the process of evaluating the 400 release in our
> test
> > > > > environment.
> > > > >
> > > > > For those of you that have completed the upgrade, any reason
> we
> > > should
> > > > > not move forward? Anything we should watch out for?
> > > >
> > > > If you're using Sales Kits, DO NOT use multiple releases!!!
> This
> > > has screwed
> > > > up our BookDtl table big time and it's our highest ranking
> > support
> > > call at the
> > > > moment.
> > > >
> > > > Make sure your Plant ID has a default Cost ID AFTER the
upgrade
> > and
> > > BEFORE you
> > > > do any transactions.
> > > >
> > > > Test Serial Number out if you use them. Numeric only will not
> let
> > > you manually
> > > > create old S/N formats if the format is different.
> > > >
> > > > Mark W.
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>
____________ _________ _________ _________ _________ _________ _
> > ____________ __
> > > Be a better friend, newshound, and
> > > know-it-all with Yahoo! Mobile. Try it now.
> > http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> > >
> > > [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/ linksYahoo! Groups Links
>

__________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ



[Non-text portions of this message have been removed]
I agree pretty much with this.. what I don't agree with though is being told version 9 for some fixes. I would really like to see our current version fixed and not have to tell my users that we have to go through another major release upgrade just to fix the current version. Who knows what will break in the process. We are still trying to get the dust to settle from our 6.1 -> 8.03 upgrade and that was 8 months ago. I am fairly certain I would dragged outside and pummeled for even hinting about an upgrade within the next couple of years.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Thomas Rose
Sent: Monday, May 12, 2008 2:13 PM
To: vantage@yahoogroups.com
Subject: RE: {Disarmed} Re: [Vantage] Re: Looking for those who have upgraded from 305 to 404

I can't speak to the actual Epicor practices, but I have experienced this sort of thing in a company I used to work for. That company developed software for large financial institutions. Although they would test the systems before release, their attitude was "Catch and fix 80% of the bugs and let the clients find the rest." That actually worked fairly well. In one sense, it is hard to do it any other way. Unless you are actually running a number of manufacturing companies and employing a variety of different internal practices, you will find it hard to imagine all the scenarios that need to be tested. Epicor is a software company, not a manufacturing company. Thus, even if they employ many manufacturing experts, they are inherently incapable of finding all the bugs before a release. Now, as a user, I might expect them to catch and fix more bugs than they do, but I do understand that they cannot catch 100% of the bugs.

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Robert Brown
Sent: Monday, May 12, 2008 8:55 AM
To: vantage@yahoogroups.com
Subject: {Disarmed} Re: [Vantage] Re: Looking for those who have upgraded from 305 to 404


I share your frustration but I have little doubt they DO test before releasing.

I just think their internal quality standards for allowing a release to go out to users is very low. (Better to make your deadline and release known bugs than to miss it.)

Typical of a large corporation with the 'wrong' incentives in place for employees and management.

I suspect as long as an aplication doesn't completely bomb out, the release goes out ('on schedule') no matter what the fallout is.

Rob Brown

--- On Mon, 5/12/08, clive.1972 <clive.1972@...<mailto:clive.1972%40yahoo.com>> wrote:

From: clive.1972 <clive.1972@...<mailto:clive.1972%40yahoo.com>>
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to 404
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Date: Monday, May 12, 2008, 10:58 AM

This is the one thing that bugs me with Vantage, the constant
patching/updating.

It smacks of Epicor not thoroughly testing new versions before
releasing them to the general public...

--- In vantage@yahoogroups .com, Greg Gillette <ggillette@. ..> wrote:
>
> .405 should be within a couple weeks last I heard.
>
> We have fixes scheduled out to .408.. Was even told a couple of
them would be version 9.
>
> -----Original Message-----
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf Of bw2868bond
> Sent: Monday, May 12, 2008 10:39 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
>
> Do you perhaps mean .405 ??
>
> --- In vantage@yahoogroups .com, "clive.1972" <clive.1972@ > wrote:
> >
> > We've got a nasty problem that will be resolved by 406, the person
> > dealing with the support call was kind enough to give me an eta
for
> > it.
> >
> > Whether or not the eta will be met is a different matter...
> >
> > --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ > wrote:
> > >
> > > I'm curious how you know ETA for 406?
> > > Epicor technicians wouldn't tell us anything, even when they
> > replied to tell us that an open ticket is solved by .406.
> > >
> > >
> > >
> > > ----- Original Message ----
> > > From: clive.1972 <clive.1972@ >
> > > To: vantage@yahoogroups .com
> > > Sent: Monday, May 12, 2008 3:59:23 AM
> > > Subject: [Vantage] Re: Looking for those who have upgraded from
> 305
> > to 404
> > >
> > >
> > > Definately watch out for the 'Plant Cost ID' !.
> > >
> > > The upgrade cleared ours and we went for two weeks without
a 'MTL
> > > Unit Cost' being assigne dto jobs.
> > >
> > > Epicor are aware that this can occur and they have a fix for it
> so
> > > it's not the end of the world but can make things difficult.
> > >
> > > Also setup a test server using something like VMware Server and
> > give
> > > your upgraded data test after test after test, we've had many
> > > problems post upgrade from .305 to .404
> > >
> > > FYI .406 is coming out at the end of June so you may want to
> > postpone
> > > your upgrade until then as once again it provides many fixes to
> > > Epicor's buggy software ;)
> > >
> > > --- In vantage@yahoogroups .com, "Mark Wonsil"
<mark_wonsil@ ...>
> > wrote:
> > > >
> > > > > We are in the process of evaluating the 400 release in our
> test
> > > > > environment.
> > > > >
> > > > > For those of you that have completed the upgrade, any reason
> we
> > > should
> > > > > not move forward? Anything we should watch out for?
> > > >
> > > > If you're using Sales Kits, DO NOT use multiple releases!!!
> This
> > > has screwed
> > > > up our BookDtl table big time and it's our highest ranking
> > support
> > > call at the
> > > > moment.
> > > >
> > > > Make sure your Plant ID has a default Cost ID AFTER the
upgrade
> > and
> > > BEFORE you
> > > > do any transactions.
> > > >
> > > > Test Serial Number out if you use them. Numeric only will not
> let
> > > you manually
> > > > create old S/N formats if the format is different.
> > > >
> > > > Mark W.
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>
____________ _________ _________ _________ _________ _________ _
> > ____________ __
> > > Be a better friend, newshound, and
> > > know-it-all with Yahoo! Mobile. Try it now.
> > http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> > >
> > > [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/ linksYahoo! Groups Links
>

__________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ



[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/linksYahoo! Groups Links
I think the 9 release will be like the 8.00-8.03 not like a 6.x-8.x
upgrade so I don't think it will be THAT big of deal, but without seeing
it, you don't really know.



One thing I do know is that I thought the personnel on the 8.03.400 beta
test, on the epicor side, should have been required to get more than 4
beta testers live before they were able to GA it. We had a pool of
about 25-30 beta testers and they only needed 4 to take 8.03.400 Beta 2
live.



I haven't heard anything on 9 about beta, which is disappointing...has
anyone else?



Paul



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Greg Gillette
Sent: Monday, May 12, 2008 2:20 PM
To: vantage@yahoogroups.com
Subject: RE: {Disarmed} Re: [Vantage] Re: Looking for those who have
upgraded from 305 to 404



I agree pretty much with this.. what I don't agree with though is being
told version 9 for some fixes. I would really like to see our current
version fixed and not have to tell my users that we have to go through
another major release upgrade just to fix the current version. Who knows
what will break in the process. We are still trying to get the dust to
settle from our 6.1 -> 8.03 upgrade and that was 8 months ago. I am
fairly certain I would dragged outside and pummeled for even hinting
about an upgrade within the next couple of years.

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Thomas Rose
Sent: Monday, May 12, 2008 2:13 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: {Disarmed} Re: [Vantage] Re: Looking for those who have
upgraded from 305 to 404

I can't speak to the actual Epicor practices, but I have experienced
this sort of thing in a company I used to work for. That company
developed software for large financial institutions. Although they would
test the systems before release, their attitude was "Catch and fix 80%
of the bugs and let the clients find the rest." That actually worked
fairly well. In one sense, it is hard to do it any other way. Unless you
are actually running a number of manufacturing companies and employing a
variety of different internal practices, you will find it hard to
imagine all the scenarios that need to be tested. Epicor is a software
company, not a manufacturing company. Thus, even if they employ many
manufacturing experts, they are inherently incapable of finding all the
bugs before a release. Now, as a user, I might expect them to catch and
fix more bugs than they do, but I do understand that they cannot catch
100% of the bugs.

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Robert Brown
Sent: Monday, May 12, 2008 8:55 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: {Disarmed} Re: [Vantage] Re: Looking for those who have
upgraded from 305 to 404

I share your frustration but I have little doubt they DO test before
releasing.

I just think their internal quality standards for allowing a release to
go out to users is very low. (Better to make your deadline and release
known bugs than to miss it.)

Typical of a large corporation with the 'wrong' incentives in place for
employees and management.

I suspect as long as an aplication doesn't completely bomb out, the
release goes out ('on schedule') no matter what the fallout is.

Rob Brown

--- On Mon, 5/12/08, clive.1972 <clive.1972@...
<mailto:clive.1972%40yahoo.com> <mailto:clive.1972%40yahoo.com>> wrote:

From: clive.1972 <clive.1972@... <mailto:clive.1972%40yahoo.com>
<mailto:clive.1972%40yahoo.com>>
Subject: [Vantage] Re: Looking for those who have upgraded from 305 to
404
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Date: Monday, May 12, 2008, 10:58 AM

This is the one thing that bugs me with Vantage, the constant
patching/updating.

It smacks of Epicor not thoroughly testing new versions before
releasing them to the general public...

--- In vantage@yahoogroups .com, Greg Gillette <ggillette@. ..> wrote:
>
> .405 should be within a couple weeks last I heard.
>
> We have fixes scheduled out to .408.. Was even told a couple of
them would be version 9.
>
> -----Original Message-----
> From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf Of bw2868bond
> Sent: Monday, May 12, 2008 10:39 AM
> To: vantage@yahoogroups .com
> Subject: [Vantage] Re: Looking for those who have upgraded from 305
to 404
>
> Do you perhaps mean .405 ??
>
> --- In vantage@yahoogroups .com, "clive.1972" <clive.1972@ > wrote:
> >
> > We've got a nasty problem that will be resolved by 406, the person
> > dealing with the support call was kind enough to give me an eta
for
> > it.
> >
> > Whether or not the eta will be met is a different matter...
> >
> > --- In vantage@yahoogroups .com, Tony Hughes <thughes281@ > wrote:
> > >
> > > I'm curious how you know ETA for 406?
> > > Epicor technicians wouldn't tell us anything, even when they
> > replied to tell us that an open ticket is solved by .406.
> > >
> > >
> > >
> > > ----- Original Message ----
> > > From: clive.1972 <clive.1972@ >
> > > To: vantage@yahoogroups .com
> > > Sent: Monday, May 12, 2008 3:59:23 AM
> > > Subject: [Vantage] Re: Looking for those who have upgraded from
> 305
> > to 404
> > >
> > >
> > > Definately watch out for the 'Plant Cost ID' !.
> > >
> > > The upgrade cleared ours and we went for two weeks without
a 'MTL
> > > Unit Cost' being assigne dto jobs.
> > >
> > > Epicor are aware that this can occur and they have a fix for it
> so
> > > it's not the end of the world but can make things difficult.
> > >
> > > Also setup a test server using something like VMware Server and
> > give
> > > your upgraded data test after test after test, we've had many
> > > problems post upgrade from .305 to .404
> > >
> > > FYI .406 is coming out at the end of June so you may want to
> > postpone
> > > your upgrade until then as once again it provides many fixes to
> > > Epicor's buggy software ;)
> > >
> > > --- In vantage@yahoogroups .com, "Mark Wonsil"
<mark_wonsil@ ...>
> > wrote:
> > > >
> > > > > We are in the process of evaluating the 400 release in our
> test
> > > > > environment.
> > > > >
> > > > > For those of you that have completed the upgrade, any reason
> we
> > > should
> > > > > not move forward? Anything we should watch out for?
> > > >
> > > > If you're using Sales Kits, DO NOT use multiple releases!!!
> This
> > > has screwed
> > > > up our BookDtl table big time and it's our highest ranking
> > support
> > > call at the
> > > > moment.
> > > >
> > > > Make sure your Plant ID has a default Cost ID AFTER the
upgrade
> > and
> > > BEFORE you
> > > > do any transactions.
> > > >
> > > > Test Serial Number out if you use them. Numeric only will not
> let
> > > you manually
> > > > create old S/N formats if the format is different.
> > > >
> > > > Mark W.
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>
____________ _________ _________ _________ _________ _________ _
> > ____________ __
> > > Be a better friend, newshound, and
> > > know-it-all with Yahoo! Mobile. Try it now.
> > http://mobile. yahoo.com/ ;_ylt=Ahu06i62sR 8HDtDypao8Wcj9tA cJ
> > >
> > > [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/ linksYahoo! Groups Links
>

__________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[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/.
<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/linksYahoo! Groups Links





[Non-text portions of this message have been removed]
> I can't speak to the actual Epicor practices, but I have experienced this
> sort of thing in a company I used to work for. That company developed
> software for large financial institutions. Although they would test the
> systems before release, their attitude was "Catch and fix 80% of the bugs
> and let the clients find the rest." That actually worked fairly well. In one
> sense, it is hard to do it any other way. Unless you are actually running a
> number of manufacturing companies and employing a variety of different
> internal practices, you will find it hard to imagine all the scenarios that
> need to be tested. Epicor is a software company, not a manufacturing
company.
> Thus, even if they employ many manufacturing experts, they are inherently
> incapable of finding all the bugs before a release. Now, as a user, I might
> expect them to catch and fix more bugs than they do, but I do understand
> that they cannot catch 100% of the bugs.

While it is true that you can't catch all errors, a bug you fixed once should
NEVER appear again. I, too, worked at a software company in a prior life. The
technique used to prevent recurring errors is called Unit Testing:

http://en.wikipedia.org/wiki/Unit_test

Every time that Epicor writes code, there should be a Unit Test to make sure
that it performs properly. As bugs arise, a new Unit Test is added to the test
suite. The developers should fix the code and then test it against all
previous unit tests to make sure that they haven't broken any original
functionality. Beta testers should catch most of your bugs and tests for those
bugs should be added to the test suite.

The cost of Unit Testing software is FREE. (http://www.nunit.org/index.php)
Epicor actually ships a Business Object Tester but I can't believe that they
keep adding to the test suites as they fix/upgrade code because errors seem to
resurface.

The cost of letting your user base find bugs is not free. It leads to poor
word of mouth and a reduction in sales and support revenue.

Mark W.