On Mon, Sep 9, 2013 at 11:14 AM, Michael Barry <mbarry@...> wrote:
Â
<div>
<p>Really? Â SQL will always wins? Â Ever tried to run SQL server on enterprise class hardware? Â SQL Server suffers from Windows myopia but, hey, it looks really cool as a Windows Server 2012 metro app. Â Besides, if you have a real problem with Progress, you can always run SQL Server now so what is the point?<br>
On Sep 9, 2013, at 7:33 AM, Scotty K. <scottyk537@...> wrote:
Â
<div><div><br></div><div dir="ltr"><div><span>Epicor</span> has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.</div>
Â
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
<div><div><br></div><div><p class="ygrps-yiv-1645238351MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;">Progress is not the cause of any major programming issues in the system. <u></u><u></u></span></p><p class="ygrps-yiv-1645238351MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;"><u></u>Â <u></u></span></p>
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Â
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Â
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
Â
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
Sent: Friday, September 06, 2013 8:15 PM To: <vantage@yahoogroups.com> Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
Â
What's one of the current major issues caused from? Answer=progress. E10 is  SQL only... That alone fixes the majority of "known issues".Â
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@…> wrote:
Â
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
On Sep 9, 2013, at 8:24 AM, Jose Gomez <jose@...> wrote:
<div id="ygrps-yiv-2070063919ygrp-text"><div><br class="ygrps-yiv-2070063919webkit-block-placeholder"></div><div dir="ltr"><div class="ygrps-yiv-2070063919gmail_default" style="font-family:verdana, sans-serif;font-size:small;">Seriously a SQL vs Progress fight again? can't we just go back and ready the 10K other threads about this? lol</div></div>
On Mon, Sep 9, 2013 at 11:14 AM, Michael Barry <mbarry@...> wrote:
<div><p>Really? SQL will always wins? Ever tried to run SQL server on enterprise class hardware? SQL Server suffers from Windows myopia but, hey, it looks really cool as a Windows Server 2012 metro app. Besides, if you have a real problem with Progress, you can always run SQL Server now so what is the point?<br>
On Sep 9, 2013, at 7:33 AM, Scotty K. <scottyk537@...> wrote:
<div><div><br></div><div dir="ltr"><div><span>Epicor</span> has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.</div>
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
<div><div><br></div><div><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;">Progress is not the cause of any major programming issues in the system. <u></u><u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;"><u></u> <u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;">I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.<u></u><u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;"><u></u> <u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;">Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.<u></u><u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;"><u></u> <u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;">Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.<u></u><u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;"><u></u> <u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;">As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.<u></u><u></u></span></p><p class="ygrps-yiv-2070063919MsoNormal"><span style="color:rgb(31,73,125);font-size:11pt;"><u></u> <u></u></span></p><div><div style="border-top-color:rgb(181,196,223);border-top-width:1pt;border-top-style:solid;"><p class="ygrps-yiv-2070063919MsoNormal"><b><span style="font-size:10pt;">From:</span></b><span style="font-size:10pt;"> <a rel="nofollow" target="_blank" href="mailto:vantage@yahoogroups.com">vantage@yahoogroups.com</a> [mailto:<a rel="nofollow" target="_blank" href="mailto:vantage@yahoogroups.com">vantage@yahoogroups.com</a>] <b>On Behalf Of </b>Anthony Gercar<br>
Sent: Friday, September 06, 2013 8:15 PM To: <vantage@yahoogroups.com> Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@…> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Again, that’s not a problem with Progress, that’s a problem with Epicor.
If you wanted to, you can easily recreate the service in windows and then that wouldn’t be a problem.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar Sent: Monday, September 09, 2013 10:38 AM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
I can only re-create the service by re-installing openedge completely…
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Ned Sent: Monday, September 9, 2013 1:06 PM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Again, that’s not a problem with Progress, that’s a problem with Epicor.
If you wanted to, you can easily recreate the service in windows and then that wouldn’t be a problem.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the
end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste
comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation
of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released
at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses
given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
I’ll disagree with you that SQL will always win, while you might not need to do a dump and load on SQL, there are plenty of very similar processes that need to be done on SQL that are similar, they just get automated.
And in terms of the dump and load, those can be reduced and not needed to be done as often, but again, it goes back to Epicor not actually utilizing the features available to a Progress database which could very easily eliminate much of the need for a dump and load, but in order to maintain a simplified installation standard across all their customers and make it easier to support, they have foregone the use of those features.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Scotty K. Sent: Monday, September 09, 2013 10:33 AM To: vantage@yahoogroups.com Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar Sent: Monday, September 09, 2013 1:09 PM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
I can only re-create the service by re-installing openedge completely…
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Well support said that only way to fix my issue with the service is to completely re-install openedge…
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Ned Sent: Monday, September 9, 2013 1:37 PM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the
end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste
comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation
of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released
at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses
given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Agree to disagree and end this painful thread gooooooodness. Another downfall of the Yahoo Group no thread locking. We should consider moving to another platform to correct this! Thoughts? Yeah…. we can all re-live that for the third time this year please stop this madness!!!!!!!
Maybe I’m in a crappy mood, but Jesus Genesis you guys… hash this out offline if you need to as there will never be a resolve (please see children’s book reference)
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Ned Sent: Monday, September 9, 2013 12:37 PM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
I’ll disagree with you that SQL will always win, while you might not need to do a dump and load on SQL, there are plenty of very similar processes that need to be done on SQL that are similar, they just get automated.
And in terms of the dump and load, those can be reduced and not needed to be done as often, but again, it goes back to Epicor not actually utilizing the features available to a Progress database which could very easily eliminate much of the need for a dump and load, but in order to maintain a simplified installation standard across all their customers and make it easier to support, they have foregone the use of those features.
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I beli eve they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Agree to disagree and end this painful thread gooooooodness. Another downfall of the Yahoo Group no thread locking. We should consider moving to another platform to correct this! Thoughts?
Yeah…. we can all re-live that for the third time this year please stop this madness!!!!!!!
Maybe I’m in a crappy mood, but Jesus Genesis you guys… hash this out offline if you need to as there will never be a resolve (please see children’s book reference)
I’ll disagree with you that SQL will always win, while you might not need to do a dump and load on SQL, there are plenty of very similar processes that need to be done on SQL that are similar,
they just get automated.
And in terms of the dump and load, those can be reduced and not needed to be done as often, but again, it goes back to Epicor not actually utilizing the features available to a Progress database
which could very easily eliminate much of the need for a dump and load, but in order to maintain a simplified installation standard across all their customers and make it easier to support, they have foregone the use of those features.
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I beli eve they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand
the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches
it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require
a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release
of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Make sure there is a space after the = sign
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar Sent: Monday, September 09, 2013 2:05 PM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Well support said that only way to fix my issue with the service is to completely re-install openedge…
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software, but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
Sue
--- In vantage@yahoogroups.com, <TechnoBabbly@...> wrote:
Goes back to the point about the problem being with Epicor more than with Progress or OpenEdge.
Assuming your OpenEdge is installed to the Path D:\Epicor\oe102a
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Make sure there is a space after the = sign
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar Sent: Monday, September 09, 2013 2:05 PM To: vantage@yahoogroups.com Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Well support said that only way to fix my issue with the service is to completely re-install openedge…
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
If anyone from EPICOR is on this forum, this is my frustration also.
William R. King
IT Analyst
Topura America Fastener, Inc.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of snielsen.hipco@... Sent: Tuesday, September 10, 2013 9:47 AM To: vantage@yahoogroups.com Subject: RE: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software,
but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL
a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system,
or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code
rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system
this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece of software is HUGE it runs an entire company actually it has the ability to run entire companies (plural).
If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect them to come out with completely bug free code that will fit all our needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never be able to move forward and improve the product cause they would be stuck bug fixing for ever.
Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our upgrades and we should strive to be "near the bleeding edge" and hope that in turn Epicor will  become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better, the progress people will claim otherwise and the MySQL folk just need to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they are lacking.
And NO I do not work for or with Epicor nor do they pay me to say this.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software,
but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL
a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
Â
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
Â
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system,
or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Â
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Â
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
Â
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code
rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is  SQL only... That alone fixes the majority of "known issues".Â
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
Â
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system
this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Stream str = Properties.Resources.wavGolfClapAudio;
SoundPlayer plr = new SoundPlayer(str);
plr.Play();
--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> There are plenty of eyes from Epicor watching the forum trust me. In E10
> the are going to address a lot of issues (and introduce quite a few), but
> we have to keep in mind that this piece of software is HUGE it runs an
> entire company actually it has the ability to run entire companies (plural).
> If any of us set out to write such a piece of code we could not do 1/2
> better, Epicor support is lacking in some areas and they are working on it
> (i hear), but its not really fair to expect them to come out with
> completely bug free code that will fit all our needs. Should they perhaps
> be more responsive? Yes I would agree on that but we can't also expect them
> to fix bugs back to 6x, 8x, and older 9x versions if that were the case
> they would never be able to move forward and improve the product cause they
> would be stuck bug fixing for ever.
>
> Is us up to us to be good "customers" and try to keep up to date as much as
> we can (BTW this coming from a guy currently at 8.x but not for lack of
> trying) Our maintenance covers all our upgrades and we should strive to be
> "near the bleeding edge" and hope that in turn Epicor will become more
> responsive (only the squeeky wheel gets the grease). But it is really not
> fair to ask them to fix stuff that was wrong 3 or 4 years ago.
>
> in terms of Progress or Not Progress it doesn't really matter what they
> have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks,
> the MSSQL guys will claim theirs is better, the progress people will claim
> otherwise and the MySQL folk just need to move on ;-) but really and trully
> Epicor is a pretty decent company and they are fairly responsive within
> reason to customers and they do try to improve the areas which they know
> they are lacking.
>
> And NO I do not work for or with Epicor nor do they pay me to say this.
>
>
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
> <http://www.usdoingstuff.com>
>
> *Quis custodiet ipsos custodes?*
>
>
> On Tue, Sep 10, 2013 at 11:50 AM, William King <wking@...> wrote:
>
> > **
> >
> >
> > Well said. ****
> >
> > ** **
> >
> > If anyone from EPICOR is on this forum, this is my frustration also. ****
> >
> > ** **
> >
> > *William R. King*
> >
> > IT Analyst****
> >
> > Topura America Fastener, Inc.****
> >
> > ** **
> >
> > ** **
> >
> > ** **
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] *On
> > Behalf Of *snielsen.hipco@...
> > *Sent:* Tuesday, September 10, 2013 9:47 AM
> > *To:* vantage@yahoogroups.com
> > *Subject:* RE: RE: [Vantage] "Scheduled to be fixed in Epicor
> > 10"****
> >
> > ** **
> >
> > ****
> >
> > Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My
> > frustration comes from paying support and having my support dollars go
> > towards future versions than supporting the version I'm on. I have no
> > problem with "new and improved" software, but it doesn't seem fair that we
> > have to battle to get issues with the version we're on fixed. ****
> >
> > ** **
> >
> > Sue****
> >
> >
> >
> > --- In vantage@yahoogroups.com, <TechnoBabbly@> wrote:****
> >
> > Goes back to the point about the problem being with Epicor more than with
> > Progress or OpenEdge.****
> >
> > ****
> >
> > Assuming your OpenEdge is installed to the Path D:\Epicor\oe102a****
> >
> > ****
> >
> > Under a command prompt run with admin privileges.****
> >
> > ****
> >
> > Sc \\EpicorServer create AdminService10.2A binPath=
> > D:\Epicor\oe102a\bin\AdmSrvc.exe DisplayName= "AdminService for OpenEdge
> > 10.2A"****
> >
> > ****
> >
> > http://support.microsoft.com/kb/251192****
> >
> > ****
> >
> > This is a nice tool, because if you really want to, you can add a
> > dependency to it, if a person is running the SQL version, and they are
> > running them both on the same server, I have made an edit to make MSSQL a
> > dependency of OpenEdge, that way you never end up with OpenEdge starting,
> > and the Appservers not starting up because SQL hasn't come online yet and
> > the DB not available for the Appserver to connect to.****
> >
> > ****
> >
> > Make sure there is a space after the = sign****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Anthony Gercar
> > *Sent:* Monday, September 09, 2013 2:05 PM
> > *To:* vantage@yahoogroups.com
> > *Subject:* RE: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> >
> >
> > ****
> >
> > Well support said that only way to fix my issue with the service is to
> > completely re-install openedgeÂ…****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Ned
> > *Sent:* Monday, September 9, 2013 1:37 PM
> > *To:* vantage@yahoogroups.com
> > *Subject:* RE: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> > ****
> >
> > Incorrect.****
> >
> > ****
> >
> > ****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Anthony Gercar
> > *Sent:* Monday, September 09, 2013 1:09 PM
> > *To:* vantage@yahoogroups.com
> > *Subject:* RE: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> >
> >
> > ****
> >
> > I can only re-create the service by re-installing openedge completelyÂ…****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Ned
> > *Sent:* Monday, September 9, 2013 1:06 PM
> > *To:* vantage@yahoogroups.com
> > *Subject:* RE: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> > ****
> >
> > Again, that's not a problem with Progress, that's a problem with Epicor.**
> > **
> >
> > ****
> >
> > If you wanted to, you can easily recreate the service in windows and then
> > that wouldn't be a problem.****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Anthony Gercar
> > *Sent:* Monday, September 09, 2013 10:38 AM
> > *To:* vantage@yahoogroups.com
> > *Subject:* RE: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> >
> >
> > ****
> >
> > Well from my experience...and current issuesÂ…Progress is the problem.****
> >
> >
> > I need to manually start open edge with a CMD promptÂ…. YeaÂ… The services
> > are not even there. Guess who made the services disappear? A tech from
> > EpicorÂ… ****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Scotty K.
> > *Sent:* Monday, September 9, 2013 10:33 AM
> > *To:* vantage@yahoogroups.com
> > *Subject:* Re: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> > ****
> >
> > Epicor has been working on E10 for at least a couple years and even
> > demoing new features at Insights 2012. They have had plenty of time to
> > rewrite all the code to release by the end of this month, however I believe
> > they are still testing.****
> >
> > ****
> >
> > I agree that the Progress layer is not causing any of the major issues
> > with E9, but it's not helping. It's pointless comapring SQL to Progress
> > because SQL will always win. ****
> >
> > I can list 1000+ reasons why, but only have to point out one. Have anyone
> > ever had to perform a "Dump and Load" on a SQL database? ****
> >
> > ****
> >
> > On Sun, Sep 8, 2013 at 12:47 PM, Ned <TechnoBabbly@> wrote:****
> >
> > ****
> >
> > Progress is not the cause of any major programming issues in the system. *
> > ***
> >
> > ****
> >
> > I have never quite understood the severe distaste that so many have for
> > Progress and OpenEdge. My general assumption is that the distaste comes
> > from people not taking the time or effort to understand the system, or the
> > fact that there aren't a whole bunch of fancy GUI interfaces to use with
> > the system.****
> >
> > ****
> >
> > Progress makes a great product with OpenEdge, the problem is that there
> > are so few of its capabilities taken advantage of in the implementation of
> > the Epicor system that it never fully reaches it's potential.****
> >
> > ****
> >
> > Saying that Progress is at fault or the cause of the problems is along the
> > lines of blaming Budweiser or Ford for the drunk driver.****
> >
> > ****
> >
> > As a side note though, I highly highly highly doubt that they have a 100%
> > SQL version of Epicor even close to being able to be released at the end of
> > the month, I am pretty sure it would require a complete code rewrite in
> > order to accomplish that, unless they have some sort of automated tool to
> > so that, and in that case, I would trust it even less.****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Anthony Gercar
> > *Sent:* Friday, September 06, 2013 8:15 PM
> > *To:* <vantage@yahoogroups.com>
> > *Subject:* Re: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> > ****
> >
> > What's one of the current major issues caused from? Answer=progress. E10
> > is SQL only... That alone fixes the majority of "known issues".
> >
> > Sent from my iPhone****
> >
> >
> > On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@> wrote:****
> >
> > ****
> >
> > I would greatly disagree with the previous statement. E10 will be great
> > I'm sure as there are a ton of "It's fixed in 703 (e10)" responses given
> > from support, however as with any new major release of a system this large
> > there are going to be issues. I wouldn't expect going live on 10 would be
> > smart for easily another year or so. That's a long time to sit back and
> > wait.****
> >
> > ****
> >
> > Josh****
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Anthony Gercar
> > *Sent:* Friday, September 6, 2013 5:04 PM
> > *To:* <vantage@yahoogroups.com>
> > *Cc:* vantage@yahoogroups.com
> > *Subject:* Re: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> > ****
> >
> > Just wait for E10 and work on that. Don't waste your time with E9.
> >
> > Sent from my iPhone****
> >
> >
> > On Sep 6, 2013, at 5:55 PM, "Miguel Santillan" <msantillan@> wrote:****
> >
> > ****
> >
> > I dont think it is ready either, but we are spec'ing out a new server and
> > Epicor is spec'ing it out for E10.****
> >
> > ****
> >
> > I think one thing that I learned is, dont get behind on the these
> > releases. Even though E10 will be released, I wouldnt go Live with it.***
> > *
> >
> > ****
> >
> > *From:* vantage@yahoogroups.com [mailto:vantage@yahoogroups.com<vantage@yahoogroups.com>]
> > *On Behalf Of *Jose Gomez
> > *Sent:* Friday, September 06, 2013 2:50 PM
> > *To:* Vantage
> > *Subject:* Re: [Vantage] "Scheduled to be fixed in Epicor 10"***
> > *
> >
> > ****
> >
> > ****
> >
> > Who ever that support person is she/he is crazy. I don't know when E10
> > will launch but I am fairly certain it's not by the end of the month****
> >
> > On Sep 6, 2013 5:07 PM, <snielsen.hipco@> wrote:****
> >
> > ****
> >
> > I just received my first "Scheduled to be fixed in Epicor 10" response to
> > a service call on Epicor 9. We aren't going live on E9 until next month
> > (hopefully) and it's already "obsolete"! How depressing. Shortly after we
> > went live on 8.03.403 we had to start battling to get things fixed in
> > Vantage (development was busy with E9), now I get to start all over again
> > with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable
> > enough and will meet our needs for a number of years. Hopefully this will
> > be my last ride on the merry-go-round!
> >
> > FYI for anyone watching, according to the response from support, Epicor 10
> > is scheduled to be released at the end of the month.****
> >
> > ****
> >
> > ****
> >
> > ****
> >
> >
> >
> > ****
> >
> > ****
> >
> >
> >
> > ****
> >
> > ****
> >
> >
> >
> > ****
> >
> > ****
> >
> >
> >
>
At Insights, the CEO specifically said, with no prompting, that existing versions would continue to be supported. Whether or not you think it’s fair to expect
Epicor to deliver on that statement is irrelevant. It’s part of what we purchased. When we find bugs, they should fix them - gladly.
As far as your comment about any of us not able to do better, you don’t speak for all of us. The lack of adherence to a set of coding standards is one of the
things that has made my job of customizing Epicor unnecessarily time consuming and frustrating. There have been many occasions where a problem solved on one screen / bo can’t be applied to another.
MRP and forecasting is complicated, yes. Costing too. Maybe there are other algorithmic parts that I’m forgetting but, this app isn’t splitting the atom;
why isn’t it solid? Its architecture is sloppy and inconsistent.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Jose Gomez Sent: Tuesday, September 10, 2013 12:00 PM To: Vantage Subject: Re: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece
of software is HUGE it runs an entire company actually it has the ability to run entire companies (plural).
If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect
them to come out with completely bug free code that will fit all our needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never
be able to move forward and improve the product cause they would be stuck bug fixing for ever.
Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our
upgrades and we should strive to be "near the bleeding edge" and hope that in turn Epicor will become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better,
the progress people will claim otherwise and the MySQL folk just need to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they
are lacking.
And NO I do not work for or with Epicor nor do they pay me to say this.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software,
but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL
a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system,
or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code
rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major release of a system
this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
In my opinion they are supporting us they are fixing stuff in the new versions. Do you expect them to do an in place fix for every version?
On Sep 10, 2013 12:30 PM, "Joe Englert" <englertj@...> wrote:
Â
<div>
<p>
At Insights, the CEO specifically said, with no prompting, that existing versions would continue to be supported. Whether or not you think it’s fair to expect
Epicor to deliver on that statement is irrelevant. It’s part of what we purchased. When we find bugs, they should fix them - gladly.
As far as your comment about any of us not able to do better, you don’t speak for all of us. The lack of adherence to a set of coding standards is one of the
things that has made my job of customizing Epicor unnecessarily time consuming and frustrating. There have been many occasions where a problem solved on one screen / bo can’t be applied to another. Â
Â
MRP and forecasting is complicated, yes. Costing too. Maybe there are other algorithmic parts that I’m forgetting but, this app isn’t splitting the atom;
why isn’t it solid? Its architecture is sloppy and inconsistent.
Â
From:vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Jose Gomez Sent: Tuesday, September 10, 2013 12:00 PM To: Vantage Subject: Re: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Â
Â
There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece
of software is HUGE it runs an entire company actually it has the ability to run entire companies (plural).
If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect
them to come out with completely bug free code that will fit all our needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never
be able to move forward and improve the product cause they would be stuck bug fixing for ever.
Â
Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our
upgrades and we should strive to be "near the bleeding edge" and hope that in turn Epicor will  become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
Â
in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better,
the progress people will claim otherwise and the MySQL folk just need to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they
are lacking.
Â
And NO I do not work for or with Epicor nor do they pay me to say this.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software,
but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL
a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
Â
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
Â
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system,
or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Â
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Â
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
Â
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code
rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is  SQL only... That alone fixes the majority of "known issues".Â
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
Â
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system
this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Have you ever used another ERP system lol? You pretty much just described the gammot...
--- In vantage@yahoogroups.com, Joe Englert <englertj@...> wrote:
>
> At Insights, the CEO specifically said, with no prompting, that existing versions would continue to be supported. Whether or not you think it's fair to expect Epicor to deliver on that statement is irrelevant. It's part of what we purchased. When we find bugs, they should fix them - gladly.
> As far as your comment about any of us not able to do better, you don't speak for all of us. The lack of adherence to a set of coding standards is one of the things that has made my job of customizing Epicor unnecessarily time consuming and frustrating. There have been many occasions where a problem solved on one screen / bo can't be applied to another.
>
> MRP and forecasting is complicated, yes. Costing too. Maybe there are other algorithmic parts that I'm forgetting but, this app isn't splitting the atom; why isn't it solid? Its architecture is sloppy and inconsistent.
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jose Gomez
> Sent: Tuesday, September 10, 2013 12:00 PM
> To: Vantage
> Subject: Re: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
> There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece of software is HUGE it runs an entire company actually it has the ability to run entire companies (plural).
> If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect them to come out with completely bug free code that will fit all our needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never be able to move forward and improve the product cause they would be stuck bug fixing for ever.
>
> Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our upgrades and we should strive to be "near the bleeding edge" and hope that in turn Epicor will become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
>
> in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better, the progress people will claim otherwise and the MySQL folk just need to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they are lacking.
>
> And NO I do not work for or with Epicor nor do they pay me to say this.
>
>
>
> Jose C Gomez
> Software Engineer
>
>
> T: 904.469.1524 mobile
> E: jose@...<mailto:jose@...>
> http://www.josecgomez.com
> [http://www.josecgomez.com/images/linkedin.png%5d<http://www.linkedin.com/in/josecgomez> [http://www.josecgomez.com/images/facebook.png%5d <http://www.facebook.com/josegomez> [http://www.josecgomez.com/images/google.png%5d <http://www.google.com/profiles/jose.gomez> [http://www.josecgomez.com/images/twitter.png%5d <http://www.twitter.com/joc85> [http://www.josecgomez.com/images/wp.png%5d <http://www.josecgomez.com/professional-resume/> [http://www.josecgomez.com/images/rss.png%5d <http://www.josecgomez.com/feed/> [http://www.josecgomez.com/images/uds.png%5d <http://www.usdoingstuff.com>
>
> Quis custodiet ipsos custodes?
>
> On Tue, Sep 10, 2013 at 11:50 AM, William King <wking@...<mailto:wking@...>> wrote:
>
> Well said.
>
> If anyone from EPICOR is on this forum, this is my frustration also.
>
> William R. King
> IT Analyst
> Topura America Fastener, Inc.
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>] On Behalf Of snielsen.hipco@...<mailto:snielsen.hipco@...>
> Sent: Tuesday, September 10, 2013 9:47 AM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: RE: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
> Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software, but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
>
>
>
> Sue
>
>
> --- In vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>, <TechnoBabbly@<mailto:TechnoBabbly@>> wrote:
>
> Goes back to the point about the problem being with Epicor more than with Progress or OpenEdge.
>
>
>
> Assuming your OpenEdge is installed to the Path D:\Epicor\oe102a
>
>
>
> Under a command prompt run with admin privileges.
>
>
>
> Sc \\EpicorServer<file:///\\EpicorServer> create AdminService10.2A binPath= D:\Epicor\oe102a\bin\AdmSrvc.exe DisplayName= "AdminService for OpenEdge 10.2A"
>
>
>
> http://support.microsoft.com/kb/251192
>
>
>
> This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn't come online yet and the DB not available for the Appserver to connect to.
>
>
>
> Make sure there is a space after the = sign
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar
> Sent: Monday, September 09, 2013 2:05 PM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Well support said that only way to fix my issue with the service is to completely re-install openedge...
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Ned
> Sent: Monday, September 9, 2013 1:37 PM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Incorrect.
>
>
>
>
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar
> Sent: Monday, September 09, 2013 1:09 PM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> I can only re-create the service by re-installing openedge completely...
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Ned
> Sent: Monday, September 9, 2013 1:06 PM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Again, that's not a problem with Progress, that's a problem with Epicor.
>
>
>
> If you wanted to, you can easily recreate the service in windows and then that wouldn't be a problem.
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar
> Sent: Monday, September 09, 2013 10:38 AM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Well from my experience...and current issues...Progress is the problem.
>
> I need to manually start open edge with a CMD prompt.... Yea... The services are not even there. Guess who made the services disappear? A tech from Epicor...
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Scotty K.
> Sent: Monday, September 9, 2013 10:33 AM
> To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
>
>
>
> I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
>
> I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
>
>
>
> On Sun, Sep 8, 2013 at 12:47 PM, Ned <TechnoBabbly@<mailto:TechnoBabbly@>> wrote:
>
>
>
> Progress is not the cause of any major programming issues in the system.
>
>
>
> I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system, or the fact that there aren't a whole bunch of fancy GUI interfaces to use with the system.
>
>
>
> Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it's potential.
>
>
>
> Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
>
>
>
> As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar
> Sent: Friday, September 06, 2013 8:15 PM
> To: <vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>>
> Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
>
> Sent from my iPhone
>
> On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@<mailto:jgiese@>> wrote:
>
>
>
> I would greatly disagree with the previous statement. E10 will be great I'm sure as there are a ton of "It's fixed in 703 (e10)" responses given from support, however as with any new major release of a system this large there are going to be issues. I wouldn't expect going live on 10 would be smart for easily another year or so. That's a long time to sit back and wait.
>
>
>
> Josh
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Anthony Gercar
> Sent: Friday, September 6, 2013 5:04 PM
> To: <vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>>
> Cc: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
> Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Just wait for E10 and work on that. Don't waste your time with E9.
>
> Sent from my iPhone
>
> On Sep 6, 2013, at 5:55 PM, "Miguel Santillan" <msantillan@<mailto:msantillan@>> wrote:
>
>
>
> I dont think it is ready either, but we are spec'ing out a new server and Epicor is spec'ing it out for E10.
>
>
>
> I think one thing that I learned is, dont get behind on the these releases. Even though E10 will be released, I wouldnt go Live with it.
>
>
>
> From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Jose Gomez
> Sent: Friday, September 06, 2013 2:50 PM
> To: Vantage
> Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
>
>
>
>
>
> Who ever that support person is she/he is crazy. I don't know when E10 will launch but I am fairly certain it's not by the end of the month
>
> On Sep 6, 2013 5:07 PM, <snielsen.hipco@<mailto:snielsen.hipco@>> wrote:
>
>
>
> I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my last ride on the merry-go-round!
>
> FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
>
In what world is a code base essentially evolved from the early 1980’s consistent and solid? This is a product that began as 4GL code from a platform from the 1980’s and has been tweaked and modified to this day. At some point, perhaps Epicor will choose to wipe a clean slate and move forward with an entirely new software product but, in the meantime, please provide an example of an enterprise class software product that does not suffer from legacy issues.
On Sep 10, 2013, at 9:30 AM, Joe Englert <englertj@...> wrote:
<div id="ygrps-yiv-123337167ygrp-text"><div>
At Insights, the CEO specifically said, with no prompting, that existing versions would continue to be supported. Whether or not you think it’s fair to expect
Epicor to deliver on that statement is irrelevant. It’s part of what we purchased. When we find bugs, they should fix them - gladly.
As far as your comment about any of us not able to do better, you don’t speak for all of us. The lack of adherence to a set of coding standards is one of the
things that has made my job of customizing Epicor unnecessarily time consuming and frustrating. There have been many occasions where a problem solved on one screen / bo can’t be applied to another.
MRP and forecasting is complicated, yes. Costing too. Maybe there are other algorithmic parts that I’m forgetting but, this app isn’t splitting the atom;
why isn’t it solid? Its architecture is sloppy and inconsistent.
From:vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Jose Gomez Sent: Tuesday, September 10, 2013 12:00 PM To: Vantage Subject: Re: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece
of software is HUGE it runs an entire company actually it has the ability to run entire companies (plural).
If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect
them to come out with completely bug free code that will fit all our needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never
be able to move forward and improve the product cause they would be stuck bug fixing for ever.
Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our
upgrades and we should strive to be "near the bleeding edge" and hope that in turn Epicor will become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better,
the progress people will claim otherwise and the MySQL folk just need to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they
are lacking.
And NO I do not work for or with Epicor nor do they pay me to say this.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new and improved" software,
but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made an edit to make MSSQL
a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort to understand the system,
or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would require a complete code
rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major release of a system
this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live on 8.03.403 we had to start
battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years. Hopefully this will be my
last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
I’m not talking about the technologies involved in the architecture, I’m talking about the code they’ve written. I’ve been a programmer, writing small database
applications with small teams for 15 years. This is my first experience working with an ERP system.
It sounds like I’m expecting too much.
Jose, yes, if there’s a bug, they should fix it.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Michael Barry Sent: Tuesday, September 10, 2013 12:43 PM To: vantage@yahoogroups.com Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
In what world is a code base essentially evolved from the early 1980’s consistent and solid? This is a product that began as 4GL code from a platform from the 1980’s and has been tweaked and modified to this day. At some point, perhaps Epicor will choose
to wipe a clean slate and move forward with an entirely new software product but, in the meantime, please provide an example of an enterprise class software product that does not suffer from legacy issues.
On Sep 10, 2013, at 9:30 AM, Joe Englert <englertj@...> wrote:
At Insights, the CEO specifically said, with no prompting, that existing versions would continue to be supported. Whether or not you think it’s fair to expect Epicor to deliver on that statement is irrelevant.
It’s part of what we purchased. When we find bugs, they should fix them - gladly.
As far as your comment about any of us not able to do better, you don’t speak for all of us. The lack of adherence to a set of coding standards is one of the things that has made my job of customizing Epicor unnecessarily
time consuming and frustrating. There have been many occasions where a problem solved on one screen / bo can’t be applied to another.
MRP and forecasting is complicated, yes. Costing too. Maybe there are other algorithmic parts that I’m forgetting but, this app isn’t splitting the atom; why isn’t it solid? Its architecture is sloppy and inconsistent.
From:vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Jose Gomez Sent: Tuesday, September 10, 2013 12:00 PM To: Vantage Subject: Re: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece of software is HUGE it runs an entire company actually it has the ability
to run entire companies (plural).
If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect them to come out with completely bug free code that will fit all our
needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never be able to move forward and improve the product cause they would
be stuck bug fixing for ever.
Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our upgrades and we should strive to be "near the bleeding edge" and hope
that in turn Epicor will become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better, the progress people will claim otherwise and the MySQL folk just need
to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they are lacking.
And NO I do not work for or with Epicor nor do they pay me to say this.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new
and improved" software, but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made
an edit to make MSSQL a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still
testing.
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort
to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully
reaches it’s potential.
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would
require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is SQL only... That alone fixes the majority of "known issues".
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)” responses given from support, however as with any new major
release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live
on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years.
Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
Joe they are fixing the bug on the next version... I am not sure what I am missing here. If you report a bug on Version 9.05.702 they are not going to fix it recompile and then send you your own customized DLL or .P file for every bug that would be insane. What they do is what every singel company does does they fix the bug and then release 9.05.702A it is YOUR JOB to upgrade to take advantage of that fix. I am so lost as to what the problem is?
On Tue, Sep 10, 2013 at 1:01 PM, Joe Englert <englertj@...> wrote:
Â
<div>
<p>
I’m not talking about the technologies involved in the architecture, I’m talking about the code they’ve written. I’ve been a programmer, writing small database
applications with small teams for 15 years. This is my first experience working with an ERP system.Â
Â
It sounds like I’m expecting too much.
Â
Jose, yes, if there’s a bug, they should fix it.
To:vantage@yahoogroups.com Subject: Re: [Vantage] "Scheduled to be fixed in Epicor 10"
Â
Â
In what world is a code base essentially evolved from the early 1980’s consistent and solid?  This is a product that began as 4GL code from a platform from the 1980’s and has been tweaked and modified to this day.  At some point, perhaps Epicor will choose
to wipe a clean slate and move forward with an entirely new software product but, in the meantime, Â please provide an example of an enterprise class software product that does not suffer from legacy issues.
On Sep 10, 2013, at 9:30 AM, Joe Englert <englertj@...> wrote:
Â
Â
At Insights, the CEO specifically said, with no prompting, that existing versions would continue to be supported. Whether or not you think it’s fair to expect Epicor to deliver on that statement is irrelevant.Â
It’s part of what we purchased. When we find bugs, they should fix them - gladly.
As far as your comment about any of us not able to do better, you don’t speak for all of us. The lack of adherence to a set of coding standards is one of the things that has made my job of customizing Epicor unnecessarily
time consuming and frustrating. There have been many occasions where a problem solved on one screen / bo can’t be applied to another. Â
Â
MRP and forecasting is complicated, yes. Costing too. Maybe there are other algorithmic parts that I’m forgetting but, this app isn’t splitting the atom; why isn’t it solid? Its architecture is sloppy and inconsistent.
Â
From:vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Jose Gomez Sent: Tuesday, September 10, 2013 12:00 PM To: Vantage Subject: Re: RE: [Vantage] "Scheduled to be fixed in Epicor 10"
Â
Â
There are plenty of eyes from Epicor watching the forum trust me. In E10 the are going to address a lot of issues (and introduce quite a few), but we have to keep in mind that this piece of software is HUGE it runs an entire company actually it has the ability
to run entire companies (plural).
If any of us set out to write such a piece of code we could not do 1/2 better, Epicor support is lacking in some areas and they are working on it (i hear), but its not really fair to expect them to come out with completely bug free code that will fit all our
needs. Should they perhaps be more responsive? Yes I would agree on that but we can't also expect them to fix bugs back to 6x, 8x, and older 9x versions if that were the case they would never be able to move forward and improve the product cause they would
be stuck bug fixing for ever.
Â
Is us up to us to be good "customers" and try to keep up to date as much as we can (BTW this coming from a guy currently at 8.x but not for lack of trying) Our maintenance covers all our upgrades and we should strive to be "near the bleeding edge" and hope
that in turn Epicor will  become more responsive (only the squeeky wheel gets the grease). But it is really not fair to ask them to fix stuff that was wrong 3 or 4 years ago.
Â
in terms of Progress or Not Progress it doesn't really matter what they have behind, Progress, MSSQL, MongoDB , MySQl every DBMS has its quirks, the MSSQL guys will claim theirs is better, the progress people will claim otherwise and the MySQL folk just need
to move on ;-) but really and trully Epicor is a pretty decent company and they are fairly responsive within reason to customers and they do try to improve the areas which they know they are lacking.
Â
And NO I do not work for or with Epicor nor do they pay me to say this.
Thank you Ned. I never meant my comment to turn into Progress vs. SQL. My frustration comes from paying support and having my support dollars go towards future versions than supporting the version I'm on. I have no problem with "new
and improved" software, but it doesn't seem fair that we have to battle to get issues with the version we're on fixed.
This is a nice tool, because if you really want to, you can add a dependency to it, if a person is running the SQL version, and they are running them both on the same server, I have made
an edit to make MSSQL a dependency of OpenEdge, that way you never end up with OpenEdge starting, and the Appservers not starting up because SQL hasn’t come online yet and the DB not available for the Appserver to connect to.
Well from my experience...and current issues…Progress is the problem.
I need to manually start open edge with a CMD prompt…. Yea… The services are not even there. Guess who made the services disappear? A tech from Epicor…
Epicor has been working on E10 for at least a couple years and even demoing new features at Insights 2012. They have had plenty of time to rewrite all the code to release by the end of this month, however I believe they are still
testing.
Â
I agree that the Progress layer is not causing any of the major issues with E9, but it's not helping. It's pointless comapring SQL to Progress because SQL will always win.
I can list 1000+ reasons why, but only have to point out one. Have anyone ever had to perform a "Dump and Load" on a SQL database?
Progress is not the cause of any major programming issues in the system.
Â
I have never quite understood the severe distaste that so many have for Progress and OpenEdge. My general assumption is that the distaste comes from people not taking the time or effort
to understand the system, or the fact that there aren’t a whole bunch of fancy GUI interfaces to use with the system.
Â
Progress makes a great product with OpenEdge, the problem is that there are so few of its capabilities taken advantage of in the implementation of the Epicor system that it never fully
reaches it’s potential.
Â
Saying that Progress is at fault or the cause of the problems is along the lines of blaming Budweiser or Ford for the drunk driver.
Â
As a side note though, I highly highly highly doubt that they have a 100% SQL version of Epicor even close to being able to be released at the end of the month, I am pretty sure it would
require a complete code rewrite in order to accomplish that, unless they have some sort of automated tool to so that, and in that case, I would trust it even less.
What's one of the current major issues caused from? Answer=progress. E10 is  SQL only... That alone fixes the majority of "known issues".Â
Sent from my iPhone
On Sep 6, 2013, at 7:10 PM, "Joshua Giese" <jgiese@...> wrote:
Â
I would greatly disagree with the previous statement. E10 will be great I’m sure as there are a ton of “It’s fixed in 703 (e10)†responses given from support, however as with any new major
release of a system this large there are going to be issues. I wouldn’t expect going live on 10 would be smart for easily another year or so. That’s a long time to sit back and wait.
I just received my first "Scheduled to be fixed in Epicor 10" response to a service call on Epicor 9. We aren't going live on E9 until next month (hopefully) and it's already "obsolete"! How depressing. Shortly after we went live
on 8.03.403 we had to start battling to get things fixed in Vantage (development was busy with E9), now I get to start all over again with Epicor 9. Oh well, so far it seems that Epicor 9.05.701 is stable enough and will meet our needs for a number of years.
Hopefully this will be my last ride on the merry-go-round!
FYI for anyone watching, according to the response from support, Epicor 10 is scheduled to be released at the end of the month.
