RE: [DUG] Developers not upgrading

2008-05-21 Thread John Bird
Of Ian Drower Sent: Tuesday, 20 May 2008 9:04 p.m. To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Developers not upgrading Hmm.. I've been running Delphi 5 for a long while now, still with some projects using Paradox 5.0 database and the BDE. Its come time to migrate them to SQL

Re: [DUG] Developers not upgrading

2008-05-20 Thread Ian Drower
Hmm.. I've been running Delphi 5 for a long while now, still with some projects using Paradox 5.0 database and the BDE. Its come time to migrate them to SQL, Microsofts SQL server, MySQL, and was looking at Firebird as well, since the coming and going of Interbase and Codegear hadn't really

Re: [DUG] Developers not upgrading

2008-05-20 Thread Robert martin
Hi You can get QuickReports for Delphi2007 (they opened it up as a separate download). Stability wise its actually pretty nice, you will find most things (asside from 'maybe' the help) to be a big improvement. There are some bugs that haven't been resolved (such as a memory leak when

RE: [DUG] Developers not upgrading

2008-05-12 Thread Sean Cross
So in my case dont think i have scope to upgrade to Delphi 2007:( By the way anyone tried the intraweb feature in delphi latest version. Since i am new to this particual functionalty? regards   Vik I have used Intraweb in a couple of projects with success. I probably wouldn't start a clean

Re: [DUG] Developers not upgrading

2008-05-11 Thread Robert martin
Hi This is a side track but We did upgrade to D2007 and feel somewhat ripped off. D2007 has a number of major bugs that we have reported, seen promoted to the internal database and never seen a fix for. When D2007 was released the auto updating aspect was heavily pushed (at the

RE: Re: [DUG] Developers not upgrading

2008-05-11 Thread Gary T. Benner
[Reply] Hi all, I'd like to add another dimension to this conversation ... after talking to today to a client who told me that he had developers leaving as they saw their career path with C#, and not Delphi. I talked about the migration path with Delphi so they could be doing both Pascal and

RE: Re: [DUG] Developers not upgrading

2008-05-11 Thread Conor Boyd
Yeah, good point. That's probably one of the main reasons for us maintaining our upgrade path to D2007. Another part of our company has been building .NET applications that we intend to provide functionality for, and the attractiveness of being able (relatively easily) to package up some of our

RE: Re: [DUG] Developers not upgrading

2008-05-11 Thread Leigh Wanstead
PROTECTED] Cc: delphi@delphi.org.nz Subject: RE: Re: [DUG] Developers not upgrading [Reply] Hi all, I'd like to add another dimension to this conversation ... after talking to today to a client who told me that he had developers leaving as they saw their career path with C#, and not Delphi. I talked

Re: [DUG] Developers not upgrading

2008-05-11 Thread Phil Scadden
And one last comment, a request actually, how many people have used both Delphi .NET and Visual Studio - and how do they compare? Have both VS and Delphi. Its hard not to have VS really - it runs rings around the opposition for c and c++. For me, it also allows me to debug MPI code

RE: Re: [DUG] Developers not upgrading

2008-05-11 Thread Cheng Wei (FMI)
PROTECTED] W: http://www.fmi.co.nz |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED] On Behalf Of Gary T. Benner |Sent: Monday, 12 May 2008 11:12 p.m. |To: [EMAIL PROTECTED] |Cc: delphi@delphi.org.nz |Subject: RE: Re: [DUG] Developers not upgrading | |[Reply

RE: Re: [DUG] Developers not upgrading

2008-05-11 Thread John Bird
Re pain of upgrading: I upgraded from D5 to D2006 and then D2007 with no issues at all - most pleasantly surprised. I think I was shrewd to use only a small handful of simple third party components. John ___ NZ Borland Developers Group - Delphi

Re: [DUG] Developers not upgrading

2008-05-11 Thread Alister Christie
Delphi 2006 - 2007 was incredibly painless, I just told D2007 to install all the BPLs. D7 - D2006 was very hard and took me a long time to get all the 3rd party components to play nice. Alister Christie Computers for People Ph: 04 471 1849 Fax: 04 471 1266 http://www.salespartner.co.nz PO Box

RE: [DUG] Developers not upgrading

2008-05-10 Thread Eric A
: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; delphi@delphi.org.nz Subject: Re: [DUG] Developers not upgrading CC: I've noticed this one also and it's generally quite annoying because it requires a couple of extra mouse clicks once you know it's happening. The other one that bothers me

Re: [DUG] Developers not upgrading

2008-05-10 Thread Jeremy North
While crashes might be due to 3rd party components, its diabolical to figure out which ones and then how do you know is the bug causing the issue anyway? Process of elimination and/or debugging the IDE ___ NZ Borland Developers Group - Delphi mailing

Re: [DUG] Developers not upgrading

2008-05-10 Thread Vikas...
11:12 p.m. To: 'NZ Borland Developers Group - Delphi List' Subject: [DUG] Developers not upgrading Developers not upgrading... I suppose that is one of the core Codegear problems.I have been working at a firm with production software in Delphi 5 Enterprise - there has been no real need

Re: [DUG] Developers not upgrading

2008-05-10 Thread Jeremy North
- Dont have to work through 4-5 catastrophic error, Application error boxes when I exit What third party experts/components do you have installed? Shutdown errors are almost exclusively linked to issues with third party experts or packages. When you debug an instance of the IDE where are the

[DUG] Developers not upgrading

2008-05-08 Thread John Bird
Developers not upgrading... I suppose that is one of the core Codegear problems.I have been working at a firm with production software in Delphi 5 Enterprise - there has been no real need to upgrade, as it does most of what they need. The main reluctance about upgrading are simply the

RE: [DUG] Developers not upgrading

2008-05-08 Thread David Brennan
. To: 'NZ Borland Developers Group - Delphi List' Subject: [DUG] Developers not upgrading Developers not upgrading... I suppose that is one of the core Codegear problems.I have been working at a firm with production software in Delphi 5 Enterprise - there has been no real need to upgrade, as it does

Re: [DUG] Developers not upgrading

2008-05-08 Thread Berend de Boer
John == John Bird [EMAIL PROTECTED] writes: John If there was an easy way to even just test compiling and John running the existing code on a later version, I bet it would John be much easier for clients like this to upgrade... Just buying an upgrade version isn't too expensive is

Re: [DUG] Developers not upgrading

2008-05-08 Thread Alister Christie
I've noticed this one also and it's generally quite annoying because it requires a couple of extra mouse clicks once you know it's happening. The other one that bothers me a little is the TTable and TQuery glyphs are missing on the components quite frequently - I guess it makes it obvious

Re: [DUG] Developers not upgrading

2008-05-08 Thread Phil Scadden
Developers not upgrading... Well I bought D2 Enterprise. When upgrade time around I found not only was upgrade around 80% of purchase price, but so many of the enterprise bits were completely different. Ie Borland just provided a different set of 3rd party components so application

RE: [DUG] Developers not upgrading

2008-05-08 Thread Myles Penlington
Thankfully D2007 does not have these issues - and it is much faster. Have you installed Andreas Hauslanden DelphiSpeedup Package? Well worth it. http://andy.jgknet.de/dspeedup The only issues experienced on D2006 IDE exit were ones from 3rd party components and our own - which are now fixed.

RE: [DUG] Developers not upgrading

2008-05-08 Thread Paul Heinz
Get a release out with full Unicode support and generics and we'll upgrade from Delphi 5... Of course it better be darn stable and have useful help ;-) Yeah. What he said. Admittedly are somewhat less recalcitrant - we are on BDS 2006 as the IDE improvements were worth it. Blaming the

Re: [DUG] Developers not upgrading

2008-05-08 Thread Phil Scadden
The only issues experienced on D2006 IDE exit were ones from 3rd party components and our own - which are now fixed. If D2007 fixes these, then I am interested in upgrading but could find anything which suggested it did. I have used DSpeedup. While crashes might be due to 3rd party

RE: [DUG] Developers not upgrading

2008-05-08 Thread Myles Penlington
Of Phil Scadden Sent: Friday, 9 May 2008 12:06 p.m. To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Developers not upgrading The only issues experienced on D2006 IDE exit were ones from 3rd party components and our own - which are now fixed. If D2007 fixes these, then I am

Re: [DUG] Developers not upgrading

2008-05-08 Thread Phil Scadden
Do you have any tips/pointers on tracking down this shutdown issues? I agree that it's most likely our own components that are causing these errors for me; just wondered if you have any general suggestions about solving them. Yes. If its not memory leaks then what other sin does a

RE: [DUG] Developers not upgrading

2008-05-08 Thread Alan Rose
Group - Delphi List Subject: Re: [DUG] Developers not upgrading The only issues experienced on D2006 IDE exit were ones from 3rd party components and our own - which are now fixed. If D2007 fixes these, then I am interested in upgrading but could find anything which suggested

RE: [DUG] Developers not upgrading

2008-05-08 Thread Conor Boyd
To be honest, I had been hoping for something more helpful. Because it's not immediately obvious to me how to go about tracking down a memory leak in any one of a few dozen components on IDE shutdown without just eyeballing the code, which I would think would take a prohibitive amount of time,

RE: [DUG] Developers not upgrading

2008-05-08 Thread Myles Penlington
PROTECTED] On Behalf Of Conor Boyd Sent: Friday, 9 May 2008 1:09 p.m. To: NZ Borland Developers Group - Delphi List Subject: RE: [DUG] Developers not upgrading Myles, Do you have any tips/pointers on tracking down this shutdown issues? I agree that it's most likely our own components that are causing