Epicor 9.04.506c

Thanks Dale. You saved me a long email response as your experience mirrors mine (to a degree that I suspect we may be talking about the same software company in regard to users voting on enhancements).
Epicor is the only software provider in 25 yrs that routinely leaves me feeling angry (and like I've been mugged).
Rob

--- Original Message ---
From:"Walker, Dale" <dwalker@...>
Sent:Wed 9/29/10 9:49 am
To:"vantage@yahoogroups.com" <vantage@yahoogroups.com>
Subj:[Vantage] Re: Epicor 9.04.506c

No Thom; this isn't as good as it gets. There are a number of great posts made in this link and I don't want it to degrade into an all-out EPICOR bashing gig because that is not helpful. I do however; have a couple of decades of experience with other ERP solution providers that took a dramatically different posture towards how their existing customer base was supported. One ERP provider in particular provided stellar support and great value for our support dollars. Here are some stark differences...Customers had a direct channel to request enhancements, in fact most enhancements incorporated into the product came directly from the installed customer base, customers had a collective voice in voting for the enhancements most critical to their enterprise, any enhancement requests not acted upon were given full explanation why not, few bugs were found in production code, when bugs were reported by customers it was the vendor's responsibility to recreate the bug and to document the issue and own it until a fix was delivered, fixes normally took days to be delivered, fixes were provided at the software level where the bug was reported unless the customer was too far back (usually measured in years), releases provided more new features than bug fixes, very few (if any) bugs were found during new release testing, when calling support to report a problem we were never subjected to having to explain the situation multiple times because we were transferred to multiple support people, the first support person was the only point of contact and that individual owned the issue until the issue was resolved and then that person would reach out to the customer with the resolution. And lastly-----I was never told that it was "working as designed" in an attempt to end the conversation. If it was truly working as designed the support representative had an immediate conversation with us on how we felt that the current design could be improved, how it would specifically benefit our business, discussed some possible alternative steps, and what the ramifications would be to our business if they took no further action.
I NEVER took issue with the support fees that we paid to this vendor. I am more than willing to pay world class support fees if we receive world class support in return.
Dale.

[cid:073014913@29092010-0109]
Dale Walker
Director, Information Technology
Le Sueur Incorporated
1409 Vine Street
Le Sueur, MN 56058
ph.507.665.6204 x277
fx .507.665.8466
www.lesueurinc.com<http://www.lesueurinc.com/>



[Non-text portions of this message have been removed]
Just a question to the group...

We went live on 9.04.506c a couple weeks ago after much piloting. Since then we have been hit with many, many bugs. By bugs I mean issues that when presented to Epicor Support they say that the fix is in a future patch and set the ticket status to "pending". I currently have 10 open tickets that are awaiting patches. Is this normal? How do your users cope with this? Is there any other recourse? Or, to phrase this another way, HELP!
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17080" name=GENERATOR></HEAD>
<BODY style="BACKGROUND-COLOR: #fff">
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Hi,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>I am still in conversion mode with regards to Version
9.04.506c. I am trying to convert from Avante. If you do not mind me asking,
what are the problems/issues that you have run into that still are awaiting
fixes?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Thanks</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Bob Jessop</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Misonix Inc</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>rjj@...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> vantage@yahoogroups.com
[mailto:vantage@yahoogroups.com] <B>On Behalf Of </B>m_sprowles<BR><B>Sent:</B>
Monday, September 27, 2010 3:01 PM<BR><B>To:</B>
vantage@yahoogroups.com<BR><B>Subject:</B> [Vantage] Epicor
9.04.506c<BR></FONT><BR></DIV>
<DIV></DIV><SPAN style="DISPLAY: none"> </SPAN> <!--~-|**|PrettyHtmlStartT|**|-~-->
<DIV id=ygrp-mlmsg style="POSITION: relative">
<DIV id=ygrp-msg style="Z-INDEX: 1"><!--~-|**|PrettyHtmlEndT|**|-~-->
<DIV id=ygrp-text>
<P>Just a question to the group...<BR><BR>We went live on 9.04.506c a couple
weeks ago after much piloting. Since then we have been hit with many, many bugs.
By bugs I mean issues that when presented to Epicor Support they say that the
fix is in a future patch and set the ticket status to "pending". I currently
have 10 open tickets that are awaiting patches. Is this normal? How do your
users cope with this? Is there any other recourse? Or, to phrase this another
way, HELP!<BR><BR></P></DIV><!--~-|**|PrettyHtmlStart|**|-~-->
<DIV style="COLOR: #fff; HEIGHT: 0px"></DIV><!--~-|**|PrettyHtmlEnd|**|-~--><!--~-|**|PrettyHtmlStart|**|-~-->
<STYLE type=text/css>#ygrp-mkp {
BORDER-RIGHT: #d8d8d8 1px solid; PADDING-RIGHT: 10px; BORDER-TOP: #d8d8d8 1px solid; PADDING-LEFT: 10px; PADDING-BOTTOM: 0px; MARGIN: 10px 0px; BORDER-LEFT: #d8d8d8 1px solid; PADDING-TOP: 0px; BORDER-BOTTOM: #d8d8d8 1px solid; FONT-FAMILY: Arial
}
#ygrp-mkp HR {
BORDER-RIGHT: #d8d8d8 1px solid; BORDER-TOP: #d8d8d8 1px solid; BORDER-LEFT: #d8d8d8 1px solid; BORDER-BOTTOM: #d8d8d8 1px solid
}
#ygrp-mkp #hd {
FONT-WEIGHT: 700; FONT-SIZE: 85%; MARGIN: 10px 0px; COLOR: #628c2a; LINE-HEIGHT: 122%
}
#ygrp-mkp #ads {
MARGIN-BOTTOM: 10px
}
#ygrp-mkp .ad {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
#ygrp-mkp .ad P {
MARGIN: 0px
}
#ygrp-mkp .ad A {
COLOR: #0000ff; TEXT-DECORATION: none
}
#ygrp-sponsor #ygrp-lc {
FONT-FAMILY: Arial
}
#ygrp-sponsor #ygrp-lc #hd {
FONT-WEIGHT: 700; FONT-SIZE: 78%; MARGIN: 10px 0px; LINE-HEIGHT: 122%
}
#ygrp-sponsor #ygrp-lc .ad {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; MARGIN-BOTTOM: 10px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
A {
COLOR: #1e66ae
}
#actions {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; FONT-SIZE: 11px; PADDING-BOTTOM: 10px; PADDING-TOP: 10px; FONT-FAMILY: Verdana
}
#activity {
PADDING-RIGHT: 10px; PADDING-LEFT: 10px; FONT-SIZE: 10px; FLOAT: left; PADDING-BOTTOM: 10px; PADDING-TOP: 10px; FONT-FAMILY: Verdana; BACKGROUND-COLOR: #e0ecee
}
#activity SPAN {
FONT-WEIGHT: 700
}
#activity SPAN:first-child {
TEXT-TRANSFORM: uppercase
}
#activity SPAN A {
COLOR: #5085b6; TEXT-DECORATION: none
}
#activity SPAN SPAN {
COLOR: #ff7900
}
#activity SPAN .underline {
TEXT-DECORATION: underline
}
.attach {
CLEAR: both; PADDING-RIGHT: 0px; PADDING-LEFT: 0px; FONT-SIZE: 12px; PADDING-BOTTOM: 10px; WIDTH: 400px; PADDING-TOP: 10px; FONT-FAMILY: Arial
}
.attach DIV A {
TEXT-DECORATION: none
}
.attach IMG {
PADDING-RIGHT: 5px; BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
.attach LABEL {
DISPLAY: block; MARGIN-BOTTOM: 5px
}
.attach LABEL A {
TEXT-DECORATION: none
}
BLOCKQUOTE {
MARGIN: 0px 0px 0px 4px
}
.bold {
FONT-WEIGHT: 700; FONT-SIZE: 13px; FONT-FAMILY: Arial
}
.bold A {
TEXT-DECORATION: none
}
DD.last P A {
FONT-WEIGHT: 700; FONT-FAMILY: Verdana
}
DD.last P SPAN {
FONT-WEIGHT: 700; MARGIN-RIGHT: 10px; FONT-FAMILY: Verdana
}
DD.last P SPAN.yshortcuts {
MARGIN-RIGHT: 0px
}
DIV.attach-table DIV DIV A {
TEXT-DECORATION: none
}
DIV.attach-table {
WIDTH: 400px
}
DIV.file-title A {
TEXT-DECORATION: none
}
DIV.file-title A:active {
TEXT-DECORATION: none
}
DIV.file-title A:hover {
TEXT-DECORATION: none
}
DIV.file-title A:visited {
TEXT-DECORATION: none
}
DIV.photo-title A {
TEXT-DECORATION: none
}
DIV.photo-title A:active {
TEXT-DECORATION: none
}
DIV.photo-title A:hover {
TEXT-DECORATION: none
}
DIV.photo-title A:visited {
TEXT-DECORATION: none
}
DIV#ygrp-mlmsg #ygrp-msg P A SPAN.yshortcuts {
FONT-WEIGHT: normal; FONT-SIZE: 10px; FONT-FAMILY: Verdana
}
.green {
COLOR: #628c2a
}
.MsoNormal {
MARGIN: 0px
}
o {
FONT-SIZE: 0px
}
#photos DIV {
FLOAT: left; WIDTH: 72px
}
#photos DIV DIV {
BORDER-RIGHT: #666666 1px solid; BORDER-TOP: #666666 1px solid; OVERFLOW: hidden; BORDER-LEFT: #666666 1px solid; WIDTH: 62px; BORDER-BOTTOM: #666666 1px solid; HEIGHT: 62px
}
#photos DIV LABEL {
FONT-SIZE: 10px; OVERFLOW: hidden; WIDTH: 64px; COLOR: #666666; WHITE-SPACE: nowrap; TEXT-ALIGN: center
}
#reco-category {
FONT-SIZE: 77%
}
#reco-desc {
FONT-SIZE: 77%
}
.replbq {
MARGIN: 4px
}
#ygrp-actbar DIV A:first-child {
PADDING-RIGHT: 5px; MARGIN-RIGHT: 2px
}
#ygrp-mlmsg {
FONT-SIZE: small; FONT-FAMILY: Arial, helvetica,clean, sans-serif
}
#ygrp-mlmsg TABLE {

}
#ygrp-mlmsg SELECT {
FONT: 99% Arial, Helvetica, clean, sans-serif
}
INPUT {
FONT: 99% Arial, Helvetica, clean, sans-serif
}
TEXTAREA {
FONT: 99% Arial, Helvetica, clean, sans-serif
}
#ygrp-mlmsg PRE {
FONT: 100% monospace
}
CODE {
FONT: 100% monospace
}
#ygrp-mlmsg * {
LINE-HEIGHT: 1.22em
}
#ygrp-mlmsg #logo {
PADDING-BOTTOM: 10px
}
#ygrp-mlmsg A {
COLOR: #1e66ae
}
#ygrp-msg P A {
FONT-FAMILY: Verdana
}
#ygrp-msg P#attach-count SPAN {
FONT-WEIGHT: 700; COLOR: #1e66ae
}
#ygrp-reco #reco-head {
FONT-WEIGHT: 700; COLOR: #ff7900
}
#ygrp-reco {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; MARGIN-BOTTOM: 20px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
#ygrp-sponsor #ov LI A {
FONT-SIZE: 130%; TEXT-DECORATION: none
}
#ygrp-sponsor #ov LI {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; FONT-SIZE: 77%; PADDING-BOTTOM: 6px; PADDING-TOP: 6px; LIST-STYLE-TYPE: square
}
#ygrp-sponsor #ov UL {
PADDING-RIGHT: 0px; PADDING-LEFT: 8px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
#ygrp-text {
FONT-FAMILY: Georgia
}
#ygrp-text P {
MARGIN: 0px 0px 1em
}
#ygrp-text TT {
FONT-SIZE: 120%
}
#ygrp-vital UL LI:unknown {
BORDER-RIGHT-STYLE: none! important
}
</STYLE>
<!--~-|**|PrettyHtmlEnd|**|-~--><!-- end group email --></BODY></HTML>


[Non-text portions of this message have been removed]
It's always that way with EPICOR!
They like to use their customers to do their research and development for them.
Every version of software that they have came out with. It's always the same!


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of m_sprowles
Sent: Monday, September 27, 2010 2:01 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor 9.04.506c



Just a question to the group...

We went live on 9.04.506c a couple weeks ago after much piloting. Since then we have been hit with many, many bugs. By bugs I mean issues that when presented to Epicor Support they say that the fix is in a future patch and set the ticket status to "pending". I currently have 10 open tickets that are awaiting patches. Is this normal? How do your users cope with this? Is there any other recourse? Or, to phrase this another way, HELP!



[Non-text portions of this message have been removed]
1) Jobs not linking to Orders, (Jobs do link but link will not display).
2) Bookings will not record correctly or are overwritten.
3) Recurring error of "Data in use by another user" occurs randomly for all users.
4) If you delete a salesman from an order you will delete the entire order.
5) If you quote a non-standard price the quote will revert to the default price.
6) Cannot create a job related misc. charge on an invoice
7) Credit Hold indicator missing from Order Entry and will not display
8) The CALC ABC Codes report will not generate and hangs the system
9) The refresh tool in Epicor for FRx is missing
10) The Bank Recon function will not print edit lists

Those are the ten for which we are awaiting patches. We have several other tickets in that have yet to be considered bugs but no corrective action has been taken by Epicor as yet...

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Robert Jessop
Sent: Monday, September 27, 2010 3:03 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17080" name=GENERATOR></HEAD>
<BODY style="BACKGROUND-COLOR: #fff">
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Hi,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>I am still in conversion mode with regards to Version
9.04.506c. I am trying to convert from Avante. If you do not mind me asking,
what are the problems/issues that you have run into that still are awaiting
fixes?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Thanks</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Bob Jessop</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>Misonix Inc</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2>rjj@... <mailto:rjj%40misonix.com> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=126360119-27092010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] <B>On Behalf Of </B>m_sprowles<BR><B>Sent:</B>
Monday, September 27, 2010 3:01 PM<BR><B>To:</B>
vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> <BR><B>Subject:</B> [Vantage] Epicor
9.04.506c<BR></FONT><BR></DIV>
<DIV></DIV><SPAN style="DISPLAY: none"> </SPAN> <!--~-|**|PrettyHtmlStartT|**|-~-->
<DIV id=ygrp-mlmsg style="POSITION: relative">
<DIV id=ygrp-msg style="Z-INDEX: 1"><!--~-|**|PrettyHtmlEndT|**|-~-->
<DIV id=ygrp-text>
<P>Just a question to the group...<BR><BR>We went live on 9.04.506c a couple
weeks ago after much piloting. Since then we have been hit with many, many bugs.
By bugs I mean issues that when presented to Epicor Support they say that the
fix is in a future patch and set the ticket status to "pending". I currently
have 10 open tickets that are awaiting patches. Is this normal? How do your
users cope with this? Is there any other recourse? Or, to phrase this another
way, HELP!<BR><BR></P></DIV><!--~-|**|PrettyHtmlStart|**|-~-->
<DIV style="COLOR: #fff; HEIGHT: 0px"></DIV><!--~-|**|PrettyHtmlEnd|**|-~--><!--~-|**|PrettyHtmlStart|**|-~-->
<STYLE type=text/css>#ygrp-mkp {
BORDER-RIGHT: #d8d8d8 1px solid; PADDING-RIGHT: 10px; BORDER-TOP: #d8d8d8 1px solid; PADDING-LEFT: 10px; PADDING-BOTTOM: 0px; MARGIN: 10px 0px; BORDER-LEFT: #d8d8d8 1px solid; PADDING-TOP: 0px; BORDER-BOTTOM: #d8d8d8 1px solid; FONT-FAMILY: Arial
}
#ygrp-mkp HR {
BORDER-RIGHT: #d8d8d8 1px solid; BORDER-TOP: #d8d8d8 1px solid; BORDER-LEFT: #d8d8d8 1px solid; BORDER-BOTTOM: #d8d8d8 1px solid
}
#ygrp-mkp #hd {
FONT-WEIGHT: 700; FONT-SIZE: 85%; MARGIN: 10px 0px; COLOR: #628c2a; LINE-HEIGHT: 122%
}
#ygrp-mkp #ads {
MARGIN-BOTTOM: 10px
}
#ygrp-mkp .ad {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
#ygrp-mkp .ad P {
MARGIN: 0px
}
#ygrp-mkp .ad A {
COLOR: #0000ff; TEXT-DECORATION: none
}
#ygrp-sponsor #ygrp-lc {
FONT-FAMILY: Arial
}
#ygrp-sponsor #ygrp-lc #hd {
FONT-WEIGHT: 700; FONT-SIZE: 78%; MARGIN: 10px 0px; LINE-HEIGHT: 122%
}
#ygrp-sponsor #ygrp-lc .ad {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; MARGIN-BOTTOM: 10px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
A {
COLOR: #1e66ae
}
#actions {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; FONT-SIZE: 11px; PADDING-BOTTOM: 10px; PADDING-TOP: 10px; FONT-FAMILY: Verdana
}
#activity {
PADDING-RIGHT: 10px; PADDING-LEFT: 10px; FONT-SIZE: 10px; FLOAT: left; PADDING-BOTTOM: 10px; PADDING-TOP: 10px; FONT-FAMILY: Verdana; BACKGROUND-COLOR: #e0ecee
}
#activity SPAN {
FONT-WEIGHT: 700
}
#activity SPAN:first-child {
TEXT-TRANSFORM: uppercase
}
#activity SPAN A {
COLOR: #5085b6; TEXT-DECORATION: none
}
#activity SPAN SPAN {
COLOR: #ff7900
}
#activity SPAN .underline {
TEXT-DECORATION: underline
}
.attach {
CLEAR: both; PADDING-RIGHT: 0px; PADDING-LEFT: 0px; FONT-SIZE: 12px; PADDING-BOTTOM: 10px; WIDTH: 400px; PADDING-TOP: 10px; FONT-FAMILY: Arial
}
.attach DIV A {
TEXT-DECORATION: none
}
.attach IMG {
PADDING-RIGHT: 5px; BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
.attach LABEL {
DISPLAY: block; MARGIN-BOTTOM: 5px
}
.attach LABEL A {
TEXT-DECORATION: none
}
BLOCKQUOTE {
MARGIN: 0px 0px 0px 4px
}
.bold {
FONT-WEIGHT: 700; FONT-SIZE: 13px; FONT-FAMILY: Arial
}
.bold A {
TEXT-DECORATION: none
}
DD.last P A {
FONT-WEIGHT: 700; FONT-FAMILY: Verdana
}
DD.last P SPAN {
FONT-WEIGHT: 700; MARGIN-RIGHT: 10px; FONT-FAMILY: Verdana
}
DD.last P SPAN.yshortcuts {
MARGIN-RIGHT: 0px
}
DIV.attach-table DIV DIV A {
TEXT-DECORATION: none
}
DIV.attach-table {
WIDTH: 400px
}
DIV.file-title A {
TEXT-DECORATION: none
}
DIV.file-title A:active {
TEXT-DECORATION: none
}
DIV.file-title A:hover {
TEXT-DECORATION: none
}
DIV.file-title A:visited {
TEXT-DECORATION: none
}
DIV.photo-title A {
TEXT-DECORATION: none
}
DIV.photo-title A:active {
TEXT-DECORATION: none
}
DIV.photo-title A:hover {
TEXT-DECORATION: none
}
DIV.photo-title A:visited {
TEXT-DECORATION: none
}
DIV#ygrp-mlmsg #ygrp-msg P A SPAN.yshortcuts {
FONT-WEIGHT: normal; FONT-SIZE: 10px; FONT-FAMILY: Verdana
}
.green {
COLOR: #628c2a
}
.MsoNormal {
MARGIN: 0px
}
o {
FONT-SIZE: 0px
}
#photos DIV {
FLOAT: left; WIDTH: 72px
}
#photos DIV DIV {
BORDER-RIGHT: #666666 1px solid; BORDER-TOP: #666666 1px solid; OVERFLOW: hidden; BORDER-LEFT: #666666 1px solid; WIDTH: 62px; BORDER-BOTTOM: #666666 1px solid; HEIGHT: 62px
}
#photos DIV LABEL {
FONT-SIZE: 10px; OVERFLOW: hidden; WIDTH: 64px; COLOR: #666666; WHITE-SPACE: nowrap; TEXT-ALIGN: center
}
#reco-category {
FONT-SIZE: 77%
}
#reco-desc {
FONT-SIZE: 77%
}
.replbq {
MARGIN: 4px
}
#ygrp-actbar DIV A:first-child {
PADDING-RIGHT: 5px; MARGIN-RIGHT: 2px
}
#ygrp-mlmsg {
FONT-SIZE: small; FONT-FAMILY: Arial, helvetica,clean, sans-serif
}
#ygrp-mlmsg TABLE {

}
#ygrp-mlmsg SELECT {
FONT: 99% Arial, Helvetica, clean, sans-serif
}
INPUT {
FONT: 99% Arial, Helvetica, clean, sans-serif
}
TEXTAREA {
FONT: 99% Arial, Helvetica, clean, sans-serif
}
#ygrp-mlmsg PRE {
FONT: 100% monospace
}
CODE {
FONT: 100% monospace
}
#ygrp-mlmsg * {
LINE-HEIGHT: 1.22em
}
#ygrp-mlmsg #logo {
PADDING-BOTTOM: 10px
}
#ygrp-mlmsg A {
COLOR: #1e66ae
}
#ygrp-msg P A {
FONT-FAMILY: Verdana
}
#ygrp-msg P#attach-count SPAN {
FONT-WEIGHT: 700; COLOR: #1e66ae
}
#ygrp-reco #reco-head {
FONT-WEIGHT: 700; COLOR: #ff7900
}
#ygrp-reco {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; MARGIN-BOTTOM: 20px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
#ygrp-sponsor #ov LI A {
FONT-SIZE: 130%; TEXT-DECORATION: none
}
#ygrp-sponsor #ov LI {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; FONT-SIZE: 77%; PADDING-BOTTOM: 6px; PADDING-TOP: 6px; LIST-STYLE-TYPE: square
}
#ygrp-sponsor #ov UL {
PADDING-RIGHT: 0px; PADDING-LEFT: 8px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
#ygrp-text {
FONT-FAMILY: Georgia
}
#ygrp-text P {
MARGIN: 0px 0px 1em
}
#ygrp-text TT {
FONT-SIZE: 120%
}
#ygrp-vital UL LI:unknown {
BORDER-RIGHT-STYLE: none! important
}
</STYLE>
<!--~-|**|PrettyHtmlEnd|**|-~--><!-- end group email --></BODY></HTML>

[Non-text portions of this message have been removed]
That sounds about right (re 'normal'). Users cope because they get paid &Â resign
themselves to living with it.




________________________________
From: m_sprowles <msprowles@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 3:00:36 PM
Subject: [Vantage] Epicor 9.04.506c

Â
Just a question to the group...

We went live on 9.04.506c a couple weeks ago after much piloting. Since then we
have been hit with many, many bugs. By bugs I mean issues that when presented to
Epicor Support they say that the fix is in a future patch and set the ticket
status to "pending". I currently have 10 open tickets that are awaiting patches.
Is this normal? How do your users cope with this? Is there any other recourse?
Or, to phrase this another way, HELP!







[Non-text portions of this message have been removed]
I agree...But as users do we not pay the bills? I am positive we pay heavy for
support - maybe substandard support as time - but as a unit I am sure we have a
recourse.




________________________________
From: Robert Brown <robertb_versa@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 7:44:15 PM
Subject: Re: [Vantage] Epicor 9.04.506c

Â
That sounds about right (re 'normal'). Users cope because they get paid &Â resign

themselves to living with it.

________________________________
From: m_sprowles <msprowles@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 3:00:36 PM
Subject: [Vantage] Epicor 9.04.506c

Â
Just a question to the group...

We went live on 9.04.506c a couple weeks ago after much piloting. Since then we
have been hit with many, many bugs. By bugs I mean issues that when presented to

Epicor Support they say that the fix is in a future patch and set the ticket
status to "pending". I currently have 10 open tickets that are awaiting patches.

Is this normal? How do your users cope with this? Is there any other recourse?
Or, to phrase this another way, HELP!

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







[Non-text portions of this message have been removed]
> I agree...But as users do we not pay the bills? I am positive we pay heavy for
> support - maybe substandard support as time - but as a unit I am sure we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.
You're lucky you only have 10! :-(

We are on 505c and I've logged about 12 in the last 4 days.

During Pilot, we never encountered the issues as most of the issues are to do
with BAQs and Dashboards etc.

Since getting Epicor we have logged in the region of 350 issues. Granted maybe
10-20 of these were operator error or 'how do I?' questions rather than 'why
wont it?' questions.




________________________________
From: Robert Brown <robertb_versa@...>
To: vantage@yahoogroups.com
Sent: Tue, 28 September, 2010 0:44:15
Subject: Re: [Vantage] Epicor 9.04.506c

Â
That sounds about right (re 'normal'). Users cope because they get paid &Â resign

themselves to living with it.

________________________________
From: m_sprowles <msprowles@...>
To: vantage@yahoogroups.com
Sent: Mon, September 27, 2010 3:00:36 PM
Subject: [Vantage] Epicor 9.04.506c

Â
Just a question to the group...

We went live on 9.04.506c a couple weeks ago after much piloting. Since then we
have been hit with many, many bugs. By bugs I mean issues that when presented to

Epicor Support they say that the fix is in a future patch and set the ticket
status to "pending". I currently have 10 open tickets that are awaiting patches.

Is this normal? How do your users cope with this? Is there any other recourse?
Or, to phrase this another way, HELP!

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







[Non-text portions of this message have been removed]
Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...



If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.



Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor 9.04.506c





> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.





[Non-text portions of this message have been removed]
So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...



If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.



Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor 9.04.506c





> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.





[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
Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and awaiting fixes)? Perhaps a new folder with a description and SCR# for a header? If they won't supply such a list we could do so. It would be useful for everyone in the group and also be a tool for communicating our problems to Epicor. I realize we would then have to find an avenue within Epicor with which to communicate... but it would be a start.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Brian W. Spolarich
Sent: Tuesday, September 28, 2010 9:36 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c



So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...

If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.

Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.

[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]
Contact George Klaus?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "Brian W. Spolarich " <bspolarich@...>
Sender: vantage@yahoogroups.com
Date: Tue, 28 Sep 2010 09:35:54
To: <vantage@yahoogroups.com>
Reply-To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...



If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.



Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor 9.04.506c





> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.





[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






[Non-text portions of this message have been removed]
One thing that I find frustrating is when you know there is a bug, it either
takes months before they give you an SCR for it, or they class it as 'working as
designed' but then just happen to change it in a later release.

If we could search their known issues again, we could take a lot of weight of
support and rather than spend hours with emails back and forth with recreation
steps etc, we could be better clued up.

I still dont understand why they plough on producing new version after new
version instead of getting to eg 505Z if they have to as long as every single
thing is working, then move on and make improvements. They try to make
improvements on a system that doesnt work in the first place. It is like putting
leather seats in your 20 year old car. The car doesnt work very well in the
first place, so adding leather seats just means it looks better but all the
faults from before are still there.

And enhancement requests - 'may be included in 9.1'. I wonder if they listen to
users about useful functionality instead of adding stuff that they think is
useful but they dont use it every day and see the things that dont work on
day-to-day screens as it is.



________________________________
From: "Sprowles, Mark" <msprowles@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Tue, 28 September, 2010 14:47:13
Subject: RE: [Vantage] Epicor 9.04.506c

Â
Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and
awaiting fixes)? Perhaps a new folder with a description and SCR# for a header?
If they won't supply such a list we could do so. It would be useful for everyone
in the group and also be a tool for communicating our problems to Epicor. I
realize we would then have to find an avenue within Epicor with which to
communicate... but it would be a start.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Brian W. Spolarich
Sent: Tuesday, September 28, 2010 9:36 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...

If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.

Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.

[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]







[Non-text portions of this message have been removed]
Who is George Klaus?

I think top and bottom is their support are over worked because there arent
enough of them to deal with all of the bugs in the software. But instead of
working on all the bugs they rush on createing more versions with even more
bugs.



________________________________
From: "advantage@..." <advantage@...>
To: vantage@yahoogroups.com
Sent: Tue, 28 September, 2010 14:55:33
Subject: Re: [Vantage] Epicor 9.04.506c

Â
Contact George Klaus?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "Brian W. Spolarich " <bspolarich@...>
Sender: vantage@yahoogroups.com
Date: Tue, 28 Sep 2010 09:35:54
To: <vantage@yahoogroups.com>
Reply-To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...



If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.



Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor 9.04.506c





> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.





[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





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







[Non-text portions of this message have been removed]
I hope that we, as a user community can organize and both share/list version specific issues we find, as well as do something with this absolutely awful technical support that Epicor provides to its customer (that pay a lot for the service).
If I could, I would take my support money way from Epicor and keep the upgrade only – wish I could split tech support from SP upgrades.

Regarding the specific issues list, would recommend having in a separate location version specific.
We are 2 weeks away from go live on 905.600C (from 803.409) with a long issues list and find it useful when browsing through other postings to see what others have as issues, then turn around and verify that we don't have the same on our system.


Motty


--- In vantage@yahoogroups.com, "Sprowles, Mark" <msprowles@...> wrote:
>
> Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and awaiting fixes)? Perhaps a new folder with a description and SCR# for a header? If they won't supply such a list we could do so. It would be useful for everyone in the group and also be a tool for communicating our problems to Epicor. I realize we would then have to find an avenue within Epicor with which to communicate... but it would be a start.
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Brian W. Spolarich
> Sent: Tuesday, September 28, 2010 9:36 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] Epicor 9.04.506c
>
>
>
> So how do we, as a group, collect both the specific impacts of some of
> these release-related problems and the general sense of dissatisfaction
> and deliver it to the right level of management at Epicor to be
> effectively heard and to get a response that's more than lip service?
>
> -bws
>
> -----Original Message-----
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
> Of Butler, Bruce
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> Every year it gets to be a tougher argument for me to justify the cost
> of paying maintenance. It's a lot like having a nonperforming employee
> you can't fire. Extending the analogy...
>
> If you were to fire the employee, the unfortunate truth is any
> replacements are more than likely to have the same problems. Not only
> that but employee (i.e. software) turnover is an expensive burden to put
> on the company.
>
> Typically, I understand the value of paying maintenance. It is what
> keeps the company alive, and we all have vested interest in Epicor
> remaining in business. So as a stakeholder in this company, I wish they
> would invest in better testing of the software. It seems the quest for
> new customers overrides the needs of existing customers. This cannot be
> a good long term strategy.
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
> Of Mark Wonsil
> Sent: Monday, September 27, 2010 8:45 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Epicor 9.04.506c
>
> > I agree...But as users do we not pay the bills? I am positive we pay
> heavy for
> > support - maybe substandard support as time - but as a unit I am sure
> we have a
> > recourse.
>
> I would think that the Epicor Users Group might be one possibility.
> They already have the ear of Epicor and I've met a lot of helpful
> people there - many on this list. I'm sure that Jeff Glaze would like
> to hear your thoughts.
>
> Mark W.
>
> [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]
>
Perhaps... maybe show up as a group at Perspectives?

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of advantage@...
Sent: Tuesday, September 28, 2010 9:56 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor 9.04.506c



Contact George Klaus?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "Brian W. Spolarich " <bspolarich@... <mailto:bspolarich%40advancedphotonix.com> >
Sender: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Date: Tue, 28 Sep 2010 09:35:54
To: <vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> >
Reply-To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...



If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.



Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.



From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c





> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.





[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





[Non-text portions of this message have been removed]
I agree, can we configure a separate area for posting findings. I have started
my testing of 601 and am ready to share my findings with the group




________________________________
From: mseal <mseal@...>
To: vantage@yahoogroups.com
Sent: Tue, September 28, 2010 10:06:17 AM
Subject: [Vantage] Re: Epicor 9.04.506c

Â
I hope that we, as a user community can organize and both share/list version
specific issues we find, as well as do something with this absolutely awful
technical support that Epicor provides to its customer (that pay a lot for the
service).
If I could, I would take my support money way from Epicor and keep the upgrade
only – wish I could split tech support from SP upgrades.

Regarding the specific issues list, would recommend having in a separate
location version specific.
We are 2 weeks away from go live on 905.600C (from 803.409) with a long issues
list and find it useful when browsing through other postings to see what others
have as issues, then turn around and verify that we don't have the same on our
system.

Motty

--- In vantage@yahoogroups.com, "Sprowles, Mark" <msprowles@...> wrote:
>
> Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and
>awaiting fixes)? Perhaps a new folder with a description and SCR# for a header?
>If they won't supply such a list we could do so. It would be useful for everyone
>in the group and also be a tool for communicating our problems to Epicor. I
>realize we would then have to find an avenue within Epicor with which to
>communicate... but it would be a start.
>
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
>Brian W. Spolarich
> Sent: Tuesday, September 28, 2010 9:36 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] Epicor 9.04.506c
>
>
>
> So how do we, as a group, collect both the specific impacts of some of
> these release-related problems and the general sense of dissatisfaction
> and deliver it to the right level of management at Epicor to be
> effectively heard and to get a response that's more than lip service?
>
> -bws
>
> -----Original Message-----
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
>[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
> Of Butler, Bruce
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Epicor 9.04.506c
>
> Every year it gets to be a tougher argument for me to justify the cost
> of paying maintenance. It's a lot like having a nonperforming employee
> you can't fire. Extending the analogy...
>
> If you were to fire the employee, the unfortunate truth is any
> replacements are more than likely to have the same problems. Not only
> that but employee (i.e. software) turnover is an expensive burden to put
> on the company.
>
> Typically, I understand the value of paying maintenance. It is what
> keeps the company alive, and we all have vested interest in Epicor
> remaining in business. So as a stakeholder in this company, I wish they
> would invest in better testing of the software. It seems the quest for
> new customers overrides the needs of existing customers. This cannot be
> a good long term strategy.
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
>[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
> Of Mark Wonsil
> Sent: Monday, September 27, 2010 8:45 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: Re: [Vantage] Epicor 9.04.506c
>
> > I agree...But as users do we not pay the bills? I am positive we pay
> heavy for
> > support - maybe substandard support as time - but as a unit I am sure
> we have a
> > recourse.
>
> I would think that the Epicor Users Group might be one possibility.
> They already have the ear of Epicor and I've met a lot of helpful
> people there - many on this list. I'm sure that Jeff Glaze would like
> to hear your thoughts.
>
> Mark W.
>
> [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]
>







[Non-text portions of this message have been removed]
ha,
i'm still having 601 upgrade issues, however, can users that find 601 issues start posting them.
for now we nan just title the post with the product version and 'Issues List'

thanks


--- In vantage@yahoogroups.com, Paul L Bennett <paullbennett@...> wrote:
>
> I agree, can we configure a separate area for posting findings. I have started
> my testing of 601 and am ready to share my findings with the group
>
>
>
>
> ________________________________
> From: mseal <mseal@...>
> To: vantage@yahoogroups.com
> Sent: Tue, September 28, 2010 10:06:17 AM
> Subject: [Vantage] Re: Epicor 9.04.506c
>
> ÂÂ
> I hope that we, as a user community can organize and both share/list version
> specific issues we find, as well as do something with this absolutely awful
> technical support that Epicor provides to its customer (that pay a lot for the
> service).
> If I could, I would take my support money way from Epicor and keep the upgrade
> only â€" wish I could split tech support from SP upgrades.
>
> Regarding the specific issues list, would recommend having in a separate
> location version specific.
> We are 2 weeks away from go live on 905.600C (from 803.409) with a long issues
> list and find it useful when browsing through other postings to see what others
> have as issues, then turn around and verify that we don't have the same on our
> system.
>
> Motty
>
> --- In vantage@yahoogroups.com, "Sprowles, Mark" <msprowles@> wrote:
> >
> > Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and
> >awaiting fixes)? Perhaps a new folder with a description and SCR# for a header?
> >If they won't supply such a list we could do so. It would be useful for everyone
> >in the group and also be a tool for communicating our problems to Epicor. I
> >realize we would then have to find an avenue within Epicor with which to
> >communicate... but it would be a start.
> >
> > ________________________________
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> >Brian W. Spolarich
> > Sent: Tuesday, September 28, 2010 9:36 AM
> > To: vantage@yahoogroups.com
> > Subject: RE: [Vantage] Epicor 9.04.506c
> >
> >
> >
> > So how do we, as a group, collect both the specific impacts of some of
> > these release-related problems and the general sense of dissatisfaction
> > and deliver it to the right level of management at Epicor to be
> > effectively heard and to get a response that's more than lip service?
> >
> > -bws
> >
> > -----Original Message-----
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> >[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
> > Of Butler, Bruce
> > Sent: Tuesday, September 28, 2010 9:19 AM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: RE: [Vantage] Epicor 9.04.506c
> >
> > Every year it gets to be a tougher argument for me to justify the cost
> > of paying maintenance. It's a lot like having a nonperforming employee
> > you can't fire. Extending the analogy...
> >
> > If you were to fire the employee, the unfortunate truth is any
> > replacements are more than likely to have the same problems. Not only
> > that but employee (i.e. software) turnover is an expensive burden to put
> > on the company.
> >
> > Typically, I understand the value of paying maintenance. It is what
> > keeps the company alive, and we all have vested interest in Epicor
> > remaining in business. So as a stakeholder in this company, I wish they
> > would invest in better testing of the software. It seems the quest for
> > new customers overrides the needs of existing customers. This cannot be
> > a good long term strategy.
> >
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> >[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
> > Of Mark Wonsil
> > Sent: Monday, September 27, 2010 8:45 PM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > Subject: Re: [Vantage] Epicor 9.04.506c
> >
> > > I agree...But as users do we not pay the bills? I am positive we pay
> > heavy for
> > > support - maybe substandard support as time - but as a unit I am sure
> > we have a
> > > recourse.
> >
> > I would think that the Epicor Users Group might be one possibility.
> > They already have the ear of Epicor and I've met a lot of helpful
> > people there - many on this list. I'm sure that Jeff Glaze would like
> > to hear your thoughts.
> >
> > Mark W.
> >
> > [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]
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Why should we start the list? Epicor seems to know just about every bug in the software already.
So they should be the ones that create this list on their web site.
After all isn't that a part of having support web site.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Sprowles, Mark
Sent: Tuesday, September 28, 2010 8:47 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Epicor 9.04.506c



Could we start collecting a "bug" list, (actual bugs, admitted by Epicor and awaiting fixes)? Perhaps a new folder with a description and SCR# for a header? If they won't supply such a list we could do so. It would be useful for everyone in the group and also be a tool for communicating our problems to Epicor. I realize we would then have to find an avenue within Epicor with which to communicate... but it would be a start.

________________________________
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Brian W. Spolarich
Sent: Tuesday, September 28, 2010 9:36 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

So how do we, as a group, collect both the specific impacts of some of
these release-related problems and the general sense of dissatisfaction
and deliver it to the right level of management at Epicor to be
effectively heard and to get a response that's more than lip service?

-bws

-----Original Message-----
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On Behalf
Of Butler, Bruce
Sent: Tuesday, September 28, 2010 9:19 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Epicor 9.04.506c

Every year it gets to be a tougher argument for me to justify the cost
of paying maintenance. It's a lot like having a nonperforming employee
you can't fire. Extending the analogy...

If you were to fire the employee, the unfortunate truth is any
replacements are more than likely to have the same problems. Not only
that but employee (i.e. software) turnover is an expensive burden to put
on the company.

Typically, I understand the value of paying maintenance. It is what
keeps the company alive, and we all have vested interest in Epicor
remaining in business. So as a stakeholder in this company, I wish they
would invest in better testing of the software. It seems the quest for
new customers overrides the needs of existing customers. This cannot be
a good long term strategy.

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On Behalf
Of Mark Wonsil
Sent: Monday, September 27, 2010 8:45 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
Subject: Re: [Vantage] Epicor 9.04.506c

> I agree...But as users do we not pay the bills? I am positive we pay
heavy for
> support - maybe substandard support as time - but as a unit I am sure
we have a
> recourse.

I would think that the Epicor Users Group might be one possibility.
They already have the ear of Epicor and I've met a lot of helpful
people there - many on this list. I'm sure that Jeff Glaze would like
to hear your thoughts.

Mark W.

[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/><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]



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