Seeing as how the performance issue(s) ... see the topic "Scrolling Very Slow in QMEM 2" neither appear to be getting fixed, nor appear to be be getting any additional answers / encouragment posted, I am wondering what arrangements Quicken has for issuing refunds for this product.
While admittedly the product does perform adequately, in that it permits accurate tracking of medical expenses and reimbursements; it is so encumbered by the slow performance evidenced in the referenced topic that I find it less and less useful to me and I basically avoid going into it because of the frustrations I experience using it.
Unless someone from the Quicken team can give assurances that the issue is being addressed as one of the highest priorities, and can give some reasonable assurance that it will be fixed by a reasonable date, I believe I will have no choice to pursue a refund for the purchase price.
I don't BY ANY MEANS speak for Intuit (see, no red Q next to my name) ... but nevertheless, I have a guess as to any forthcoming response.
IF, as I believe, the root of the scrolling/performance issue is the use of .NET, I don't believe the matter will be fixed in V2. It's simply too big an issue to be addressed in a maintenance release.
IF, as others believe, it's a database issue, I don't believe ... (same ending as previous paragraph).
Sorry ... just one person's opinion ... (but I have been in systems design & development for 25+ years).
db
THINK IT THRU! Have you explained your issue so that someone who knows nothing about you, or YOUR Quicken setup, can understand what your issue is? Are you using standard Quicken terminology, particularly with respect to FILES, ACCOUNTS and CATEGORIES?
The Microsoft .NET Framework or also known briefly as .Net is a platform for building, deploying, and running Web Services and other types of Windows applications in a distributed environment. It is Microsoft?s next generation technology that promises to ease development and deployment tremendously.
--- end ---
I suspect .NET was chosen to help reduce overall program development time. I suspect that the development tools chosen to work with .NET create performance problems with the MEM data structure. If this is the case, it is a root problem and serious decisions will need to be made concerning a rewrite.
I also know (don't suspect) that I know very little about all of this ... and could be absolutely clueless. ;-)
The Microsoft .NET Framework or also known briefly as
.Net is a platform for building, deploying, and
running Web Services and other types of Windows
applications in a distributed environment. It is
Microsoft?s next generation technology that promises
to ease development and deployment tremendously.
--- end ---
Well known. See part above about 25+ years.
I suspect .NET was chosen to help reduce overall
program development time.
I don't ENTIRELY disagree with your statement. I just happen to suspect (based upon those 25+ years) that the programmers had a new toy to play with when they were creating QMEM for their co-worker ... and we're paying the price incurred from the lack of adherence to rigorous design methodologies.
If .NET is such a tool-of-the-future, why aren't Q, QB or TTAX based upon it? OR, more significantly, why wasn't QMEM based upon those PROVEN database engines?
db
THINK IT THRU! Have you explained your issue so that someone who knows nothing about you, or YOUR Quicken setup, can understand what your issue is? Are you using standard Quicken terminology, particularly with respect to FILES, ACCOUNTS and CATEGORIES?
There's a very old aphorism in systems development:
"Let us stand on each others shoulders, NOT on each others toes."
It should be apparent to any who have used both Q & QMEM, that QMEM doesn't stand on the shoulders of Quicken.
db
THINK IT THRU! Have you explained your issue so that someone who knows nothing about you, or YOUR Quicken setup, can understand what your issue is? Are you using standard Quicken terminology, particularly with respect to FILES, ACCOUNTS and CATEGORIES?
I'm not a systems analyst. I'm not a programmer. I do not work for Intuit. My gut says the following:
- Person at Intuit developed prototype for program on his own time. Felt it may help people.
Intuit said if you can find a way to produce it cheaply & show us it can make $$ then we'll go for it.
- probably had/has a set amount of time to show break even/small profit before any further $ will come in.
- Don't know how their BU's (business units) operate at Intuit. Can they share platforms? What are the cross charges? Are they prohibitive? I've worked at firms where it's cheaper, faster, smarter to go outside of what's available internally to get your product out.
- Assuming that existing Intuit platforms were available for the QMEM product mgt team, next question is compatability for a TRANSACTIONAL database. As others have mentioned, tons of code involved here & it's complicated. I manage many transactional databases & know what's involved (market research).
- Time frame. Would QMEM fall to the bottom of the pile & take 6 months for every request?
I tend to view everything from the business perspective...list the needs, importance to the customer, how to achieve, get the costs, timing, feasibility & prioritize. The rankings will give you your task list.
Sorry this is so long. Sometimes looking at the big picture helps. (BTW - I was entering 4 months of info recently - scrolling wasn't all that bad. Included our normal stuff plus 2 hospitalizations & a ton of lab work).
I certainly won't be looking for a refund. MEM has some very strong features, which I find essential in managing my medical expenses.
In <url=http://www.quickenforums.com/thread.jspa?threadID=600008320&start=0&tstart=0>another post</url> Quicken Bruce discusses the performance issues and strongly infers that the fix is a difficult challenge but it is a high priority.
For me, the program is important enough to hang in with the process. :8}
