DUNDAS, you pay for lifetimesupport but after one year, you can´t even get the patches
-
Well, I have a very poor opinion of RogueWave/Stingray. These guys didn't even bother updating the toolkit to include know bug fixes from their own site. Tim Smith Descartes Systems Sciences, Inc.
-
Can anyone recommend a company in this market with really good support where bugs get fixed??? Old Simon HB9DRV
I Know A little Company in Seattle, I believe that the name is microsoft or something like this. :-D Carlos Antollini.
-
Doh, double post... I am going to get banned for SPAM now... :) Tim Smith Descartes Systems Sciences, Inc.
-
Well, I have a very poor opinion of RogueWave/Stingray. These guys didn't even bother updating the toolkit to include know bug fixes from their own site. Tim Smith Descartes Systems Sciences, Inc.
-
Well, I have a very poor opinion of RogueWave/Stingray. These guys didn't even bother updating the toolkit to include know bug fixes from their own site. Tim Smith Descartes Systems Sciences, Inc.
I've used Stingray in the Past (early years when Scott Wingo was around) and the support and products were superb, but after the big sell out then product support has declined. I also used Dundas in the early years when their grid was premature, the code wasn't commented and the code was of a poor standard - I have seen later stuff Dundas has produced and it looks a whole better. If your going to sell class(y) software give: #1 Good Documentation - Less support questions! #2 Good Examples - Less support questions! #3 Good support turn around - When you do need help Again I'm quite happy to pay for class based software and updates only stuff gets fixed ,new features are introduced and the support questions are answered. My two (UK) pennies worth.
-
Hyperview Studio is expensive especially when you also buy the lifetime support. Now I cant even get the patches and FAQ to it. When I try to get in contact with them no answer. This is a last try to get in touch with them :confused:
Dave I don't think this guys are out to rubbish your company. It would be appreciative if you could reassure some of the guys you have bought your software. Codeproject is a well used site for developers and basically is not looking good to have your company name being 'bad mouthed' (if that is the appropiate term to use. Your call? Norm
-
I've used Stingray in the Past (early years when Scott Wingo was around) and the support and products were superb, but after the big sell out then product support has declined. I also used Dundas in the early years when their grid was premature, the code wasn't commented and the code was of a poor standard - I have seen later stuff Dundas has produced and it looks a whole better. If your going to sell class(y) software give: #1 Good Documentation - Less support questions! #2 Good Examples - Less support questions! #3 Good support turn around - When you do need help Again I'm quite happy to pay for class based software and updates only stuff gets fixed ,new features are introduced and the support questions are answered. My two (UK) pennies worth.
Few points: * The best support I have ever received by a very long way is from IBM. Very professional, very expensive but 100% on the case. IBM is the best. :rose: :rose: :rose: * The Dundas code I use (and I use quite a lot) is excellently documented - often way above the standards I have set for my own company. * I agree about Stingray - since Scott went I haven't renewed support. I use the Objective Grid extensively, but have modified it beyond belief. * There's a component company out there with newsgroups for support (not Dundas, Not Stingray) where customers have become so frustrated with the lack of support they have been shouting in the newsgroups about the piss-poor support, and the company still hasn't picked the messages up. Old Simon HB9DRV
-
I've used Stingray in the Past (early years when Scott Wingo was around) and the support and products were superb, but after the big sell out then product support has declined. I also used Dundas in the early years when their grid was premature, the code wasn't commented and the code was of a poor standard - I have seen later stuff Dundas has produced and it looks a whole better. If your going to sell class(y) software give: #1 Good Documentation - Less support questions! #2 Good Examples - Less support questions! #3 Good support turn around - When you do need help Again I'm quite happy to pay for class based software and updates only stuff gets fixed ,new features are introduced and the support questions are answered. My two (UK) pennies worth.
I have also use Stringray in the past (during the years of Scott Wingo), and the source code was so buggy or incomplete, we politely repackaged it and said "No Thanks". This was our first attempt into using 3rd party source and now completely stay away from it.
-
Promise? I've seen this message on CodeProject no fewer than three times. Could someone from Dundas PLEASE talk to this guy?
Sure, I will talk to him and see what I can do. email: troym@dundas.com phone: 1.800.463.1492 x 102 Troy
-
Hyperview Studio is expensive especially when you also buy the lifetime support. Now I cant even get the patches and FAQ to it. When I try to get in contact with them no answer. This is a last try to get in touch with them :confused:
Hi, I would like to see how I could help. Please call or email me, so that we can try and resolve your issues. I am officially taking over the component development division of Dundas Software as of September 1st. So, I would like to hear about the good and the bad experiences people have had with Dundas class libraries and components. Also, just to let everyone know. We are in the process of clearing up all messaging about our products to ensure that each and every customer (and potential customer) know what we are offering and what you will receive for your hard earned money. We have also dropped all products that that I feel are of poor quality. Plus all of the other products are being retested and updated. My first concern here at Dundas is quality, not quantity. I would rather have a smaller product line, but have superior products. We are also trying to set up a group of regular beta testers. But the response from the community is quite poor. Even with the incentive that all beta testers get licenses for the products they are testing for Free, the numbers of people who want to help us produce top notch software is extremely low. Too often the feedback we need is not given until the product is released. So, to all those who do not feel that they received their moneys worth from Dundas please contact me directly, and I will see what I can do for you. Troy Marchand troym@dundas.com VP Component Development Dundas Software Ltd.
-
Hi, I would like to see how I could help. Please call or email me, so that we can try and resolve your issues. I am officially taking over the component development division of Dundas Software as of September 1st. So, I would like to hear about the good and the bad experiences people have had with Dundas class libraries and components. Also, just to let everyone know. We are in the process of clearing up all messaging about our products to ensure that each and every customer (and potential customer) know what we are offering and what you will receive for your hard earned money. We have also dropped all products that that I feel are of poor quality. Plus all of the other products are being retested and updated. My first concern here at Dundas is quality, not quantity. I would rather have a smaller product line, but have superior products. We are also trying to set up a group of regular beta testers. But the response from the community is quite poor. Even with the incentive that all beta testers get licenses for the products they are testing for Free, the numbers of people who want to help us produce top notch software is extremely low. Too often the feedback we need is not given until the product is released. So, to all those who do not feel that they received their moneys worth from Dundas please contact me directly, and I will see what I can do for you. Troy Marchand troym@dundas.com VP Component Development Dundas Software Ltd.
Troy, Thanks for the honest answer, you have a job I wouldn't want, but I work closely with the partner involved in my company. My suggestions: [1] Stop the fire sales - all the software you can eat for $99 - that gives a bad impression. Others may wish to comment. [2] Beta testing is all very well, but it costs time to work with buggy code. I will pay good money for quality, but will not invest my time in testing unless the product comes from a company with a proven track record of producing quality products. [3] Get an in-house standard implemented. We're applying for ISO 9000, and will soon get an audit from the Food and Drugs people - I will soon be a gibbering wreck. I have to show the auditors all the software we buy in - from now on all suppliers must have ISO 9000 as a bare minimum. I wish you the best in a difficult market. Old Simon HB9DRV
-
Troy, Thanks for the honest answer, you have a job I wouldn't want, but I work closely with the partner involved in my company. My suggestions: [1] Stop the fire sales - all the software you can eat for $99 - that gives a bad impression. Others may wish to comment. [2] Beta testing is all very well, but it costs time to work with buggy code. I will pay good money for quality, but will not invest my time in testing unless the product comes from a company with a proven track record of producing quality products. [3] Get an in-house standard implemented. We're applying for ISO 9000, and will soon get an audit from the Food and Drugs people - I will soon be a gibbering wreck. I have to show the auditors all the software we buy in - from now on all suppliers must have ISO 9000 as a bare minimum. I wish you the best in a difficult market. Old Simon HB9DRV
Thanks for your feedback.
-
Troy, Thanks for the honest answer, you have a job I wouldn't want, but I work closely with the partner involved in my company. My suggestions: [1] Stop the fire sales - all the software you can eat for $99 - that gives a bad impression. Others may wish to comment. [2] Beta testing is all very well, but it costs time to work with buggy code. I will pay good money for quality, but will not invest my time in testing unless the product comes from a company with a proven track record of producing quality products. [3] Get an in-house standard implemented. We're applying for ISO 9000, and will soon get an audit from the Food and Drugs people - I will soon be a gibbering wreck. I have to show the auditors all the software we buy in - from now on all suppliers must have ISO 9000 as a bare minimum. I wish you the best in a difficult market. Old Simon HB9DRV
Ewwwww, ISO 9000... The standard that says as long as your process is well documented, followed, and consistent, then quality isn't important. I just don't see that as a marketing slogan, "Ford, where process is job #1!" :) Tim Smith Descartes Systems Sciences, Inc.
-
Ewwwww, ISO 9000... The standard that says as long as your process is well documented, followed, and consistent, then quality isn't important. I just don't see that as a marketing slogan, "Ford, where process is job #1!" :) Tim Smith Descartes Systems Sciences, Inc.
I agree to some extent about ISO 9000, but we have an audit upcoming from the FDA where quality is 100% important. I am responsible for *all* bugs in my company's products. The only thing I can offer is to have my team fix them as soon as they are reported once we can reproduce them. The only way to engineer software to be 99.999% fault free is to follow military guidelines, but would you pay the prices these guys pay? Old Simon HB9DRV
