Quote:
Originally posted by cnewtonne
<snip>I arrived here at the form today to vent out my frustration and this love-hate relationship with UR. I love it 99% of the time and I hate it when it just disappears or start throwing this AV errors.
I do not want to complain, but I do want to scream load enough for the kinook team to hear us and do something about it.<snip>
<snip>So, kinook, please tell me something new this time. Do not tell me to send you anything because I can't...
- It is all private and corporate confidential stuff
- I can not tell you how to reproduce it.
Also, do not tell me that you have not experienced these crashes. And please DO NOT TELL me to keep number of tabs minimal. I can not believe for a moment that you are not aware or seen these issues.
I do not know what else to say... but let me make some suggestions...
- IMPROVE the Instrumentation of your code to better handle these unexpected exceptions. Truly, the VERY BARE minimum you can do is trap these exceptions as they occur and have UR generate an exception report that can be e-mailed to you. So many apps do this already. I know your time and resources are limited. But BELIEVE me, most if not all users will be fine if you freeze all new features. Take your time to write this and build it into UR.
- please open up you beta testing program to allow us to participate in it. At this point, I personally do not trust your existing beta program. It has proven to be insufficient.
- Freeze all new features. I do not want a single feature added to it. Focus on fixing these major stability issues.
- Hire a software QA person for a short-term contract, may be 6 months. Having work for you full time till it is fixed.<snip>
|
I completely agree and to all of the above I would add one additional observation. The registry tweaks have improved the speed somewhat, but not to the point where UR is competitive with some of its competition. The tweaks can only do so much and they do not fix the underlying problem that the database engine is so darned slow when it comes to importing and exporting items. Recently I imported an mbx file to a new database. 18,319 messages (with attachments) took 4 hours 47 minutes to import. This is outrageous. Please don't tell be about all the background activity going on in UR because the other programs I have in mind all index as well. Import times for these programs is less than 14 minutes and in one case, less than 5 minutes! It is not always practical for me to perform these time intensive operations when the computer is normally idle, which I should not have to do in any case. Work arounds for basic problems are not an answer.
I disagree with Quant about his take on access violations, and I have yet to experience one with any other program on my computer except those I am beta testing and FINAL RELEASES OF UR. With that in mind, why should anyone have to put up with access violations in 3.x final release of a product?
I also grow weary of these gripes. What has been discussed in this thread are fundamental issues which should be resolved before mucking about with new features.
Jon