| Subject: | D6 to D2009 - application fails under Win 2000 |
| Posted by: | Alan Jeffery |
| Date: | Mon, 20 Jul 2009 |
I've just completed the update of a major commercial application to D2009. In testing it it fails when attempting to start under Win 2000. It's not an AV problem although an error messge does display. It's the usual "Failure at 3456999ff" etc. Which, of course, provides no help.
Does anyone know of any problems with D2009 under Win 2000. That application includes QuickReports Pro 5.04 but it doesn't even load the first form before it blows up.
The Win 2000 box has 196 RAM and the app is 9 Megs. So that shouldn't be a problem. The same app, compiled with D6, runs fine.
You know, I'm beginning to think switching to D2009 was a downgrade. It's just one thing after another. If it was just me having the usual transiition whoopsies I wouldn't grumble. But D2009 seems to be lame in so many ways. And now this.
I liked the Code Insight - until things started to slow down. So I disabled that. I liked Error Insight - until it started to report rubbish. So I disabled that. I hated code/block completion from the getgo - so that was disabled pretty promptly. I discovered modeling was on (by default?) so I've just turned all that off. You know, I'm rapidly turning D2009 back into D6. So why did I spend all that money?
I have clients still using Win 2000 and 2003. If the latest version of the app won't run on them then I need to maintain two versions - one on D6 the other on D2009. That is simply not doable.
Code Gear - are you listening?
Alan