I'm actually getting to the point where I should purchase a license for EDB. I bet Tim is happy to read this.

I can't see any reason to pay the extra to get source code. Other than the curiosity to take a look at it and
learn something (I am particulary fond of studying lexical analysers and parsers, I think lex and yacc were/are great inventions, but I'm showing my age here) is there any reason to get the source code? I can't see ever changing it.

Thanks

Oliver

Oliver,

The only situations i've run across where source code is useful are
(1) if you need to modify it (and you have already said you are unlikely to do so) \
(2) if you need the components ASAP whenever new Delphi ships.  Tim usually gets a new build out within 1-2 weeks of Delphi release but if you must have it right away then you need ability to compile it yourself.  
(3) if you're writing a commercial app and want to ensure you will always be able to compile it without any external binary dependencies (i.e. 5 years down the road then it might be worthwhile the small expense to have source code version available). If you have escrow requirements then contact Elevate for how the license this but generally you'd need source code access in that case.

Raul

Oliver,

I've always made it a practice to buy source code whenever possible for at least components, especially if the pricing is reasonable, which Tim's is definately reasonable.  

Not all companies like Tim keep up with the IDE's as they come out (or at the speed you need them).  If you have some legacy components that became ophaned, then having the source code allows you to at least attempt to modify them to compile to see if you can keep them.  I have a few that all I've needed to do was change an INC file that set compiler flags based on the IDE version.  So I've been able to keep them going until I'm ready to change them.

There was a Delphi component I was looking at recently that was around 300-400 without source and $3000 with source.  That would give me serious thought to see if it was really worth it.

If you were talking about ActiveX/COM/DAC items, then that could be a little different as those would usually work regardless of IDE changes and the requirement for source code lessens.  I use a very nice ActiveX library that I can't justify the high expense of getting source code for and have never needed to have it either.

Lance


Oliver wrote:

I'm actually getting to the point where I should purchase a license for EDB. I bet Tim is happy to read this.

I can't see any reason to pay the extra to get source code. Other than the curiosity to take a look at it and
learn something (I am particulary fond of studying lexical analysers and parsers, I think lex and yacc were/are great inventions, but I'm showing my age here) is there any reason to get the source code? I can't see ever changing it.

Thanks

Oliver

Lance


I've solved the problem of Delphi upgrades - I'm sticking with D2006 until I have no choice but to upgrade

Roy Lambert

Oliver,

<< I'm actually getting to the point where I should purchase a license for
EDB. I bet Tim is happy to read this. >>

I'm always happy to read that.

<< I can't see any reason to pay the extra to get source code. Other than
the curiosity to take a look at it and learn something (I am particulary
fond of studying lexical analysers and parsers, I think lex and yacc
were/are great inventions, but I'm showing my age here) is there any reason
to get the source code? I can't see ever changing it. >>

The only source code that is part of the source versions that isn't
available in the non-source versions is the core engine source, which you
will most likely never want/need to change.  Even in the non-source
versions, we provide the source code to the outer edbsrvr.dpr project and
the edbmgr.dpr project, so you can customize/brand them without having to
worry about messing around with the core engine code.

--
Tim Young
Elevate Software
www.elevatesoft.com