Delphi 2009 Upgrade Question - delphi

i bought yesterday an upgrade to Delphi 2009 Pro. Now i have the problem that i have a version of Delphi 5 Enterprise, but it's registered, but the account has been lost.
Is there a way to get the Delphi 5 version to be moved to my account, so that i can register the Delphi 2009 Pro.
Otherwise i also got a Delphi 3 Pro laying around here, which also should be enough for upgrading, but how can i get this registered?
My other Delphi's are Delphi 1, Delphi 2 Developer and Delphi 3 Standard as well as some Personal Versions.
Has anybody a good idea what i should be doing now? The best would be to move the Enterprise Delphi to my current account.
Cheers, murphy

You can try to contact Embarcadero. If you have a registered version they must have records of that. It will be helpful if you know the email address that was used to register the account.

Delphi 2009 upgrade is available to owners of any earlier version of Delphi, so you should be able to upgrade from Delphi 3.

You are probably making a mountain out of a molehill. If you haven't tried to install it yet then I would cross that bridge when you come to it. I don't believe having your Delphi 5 or 3 install associated with your account will make any difference. I am pretty sure Delphi 5 and earlier didn't have an activation, so there probably isn't anything to transfer.
More likely you will have trouble if the person you purchased it from used up the activations for 2009. Additionally, last I checked, they only support purchasing Delphi from a licensed reseller, which it sounds like wasn't the case.
I hope it works out for you though. Delphi 2009 is a great release and well worth the upgrade!

Delphi 5 doesn’t require online activation. The key should be enough to get it properly installed.

Related

Will programs developed using Embarcadero Delphi XE3 work with Embarcadero Delphi 2010

We are trying to develop a form that will be added to a project written and created using Embarcadero Delphi 2010 , We will use Embarcadero Delphi XE3 as our Development Environemt, will the code that we will write work on Embarcadero Delphi 2010 ?
If not where can I download Embarcadero Delphi 2010, I can't find it on the Embarcadero official site.
Thanks
Previous versions can be downloaded here:
http://www.embarcadero.com/xe3-earlier-versions
Depends ....
if you don't use rtti and generics and remove qulified namespaces, restrict the use of foreign components it could work, but i think it's not recommended.
If you are properly registered you have an edn account:
Pick Downloads / Registered User Downloads
It is in there. You should be able to go back to Delphi 7. 2010 is at the bottom of the page.
The latest stuff in XE3 is highly recommended. The improvements over the last few years are definitely worth it, and the upgrade will pay for itself in very short time even if you only gradually learn and use the new stuff.

How to install TAdoConnection in delphi XE2 starter?

I just bought Delphi XE2 starter and want to upgrade my projects. One of them is failing because Delphi doesn't know what TAdoConnection is.
I stupidly didn't keep a copy of the package when I D/Led it a few years ago now can't remember where I cgot it from
How to install TAdoCOnnection et al into Delphi XE2? Thanks
Update: alas, I have the Starter edition (who can afford anything else?)
Later update, just in case anyone else wants to do some database stuff with a starter edition.
I paid for AnyDac and was very happy, but then it was bought by Embarcadero, so you can't purchase it separately any more. I have a bug with Sqlite, so am looking for alternates.
Start here http://www.freebyte.com/programming/delphi/#freedelphidatabasecompone
ZeosLib looks very promising http://zeoslib.sourceforge.net/portal.php
It comes with Delphi, as long as you don't just have the "starter" edition, so you should already have it installed. Look in the ADODB unit. There is no other package to download.
It should be there, under ADODB:
http://docwiki.embarcadero.com/VCL/en/ADODB
http://docwiki.embarcadero.com/VCL/en/ADODB.TADOConnection
http://docwiki.embarcadero.com/CodeSamples/en/ADOQuery_%28Delphi%29
ADDENDUM:
Here's the XE2 feature matrix:
http://www.embarcadero.com/images/Delphi/delphi_short_feature_matrix_large.png
ADO is available on all versions ... EXCEPT the "starter version".
Since you have the Starter version, there is no direct option for TADOConnection. You either upgrade your version of Delphi, or use something other than TADOConnection.

What testing framework/unit testing to use with Delphi XE Starter Edition

I'm looking at moving from Delphi 2007 (purchased by my employer) to Delphi XE Starter Edition (purchased by me because my employer is moving away from Delphi) for some open source/hobby work. So, price is definitely a concern.
Delphi XE Starter Edition doesn't appear to have the integrated DUnit stuff. Are there any recommendations for testing frameworks that will work well with XE Starter? The framework must be automatible; for example, it must must be runnable by a Continuous Integration System such as Hudson or CruiseControl. Of course, free would be best. Integration directly into the IDE would also be handy, but not a requirement.
DUNIT is on SourceForge so you can get it from there. The version on SF is 9.4.0, the same that ships with Delphi XE. The code is however not identical. I do not know if it works with Delphi XE Starter edition but I don't see why it should not.
Will DUnit2 do?
Dunit2 is used in tiOPF framework and said to be quite good. The download sites are:
http://sourceforge.net/projects/dunit2/
http://members.optusnet.com.au/~mcnabp/
http://github.com/graemeg/dunit2
DUnit may be a better choice that DUnit2. With DUnit you can use the jcl and USE_JEDI_JCL to get the line numbers of failures. DUnit2 doesn't appear to support this.
DUNit2 doesn't seem to be getting much attention since Peter's death either. I don't know if it has been updated to use the latest version of delphi but it doesn't look like it.

Can Delphi 2009 be installed on the same machine as Delphi 2006 or Delphi 2007?

Is there any conflict?
All new versions of Delphi can always be installed safely /next/ to older version.
Each new version should be installed in its own directory.
If you are going to install multiple versions, always install the oldest version first, and then work your way to the newest.
We work very hard to make sure that all versions of Delphi coexist together. But again, never install one version directly on top of another.
I am running 2007 and 2009 on the same machine (this machine) just fine. The only problem you might have is if you are compiling components to the same directory - you will just need to rebuild all your DCU's and packages each time, or make version specific packages and directories.
Install them in their own directories, and make sure you keep package binaries separate, you should be fine. I've got 2009, 2007, 2006, 7 and 5 all on this machine with no issues.
I have at least 4 Delphi versions on one machine. They do not bite each other.
I always install older versions first because i had once problems if i did this the other way round.
Yes - as Rob said (Robsoft) I have both working here. Delphi has always been very good at co-existing with other versions.
Obviously you can only have one version as the default for opening Delphi files.
Should not conflict.
I did D2007 on the same machine as D2006 with absolutely no problems (I was shocked, actually).
I haven't tried D2009 yet, but it should be ok.
This guy had problems though. Hopefully his issues were due to the custom setup he describes in that article.
A colleague of mine (think he has an account on here as dcraggs now) has got them both running on the same machine just fine, I believe.
Certainly would be a huge own-goal from Embarcadero if installing D2009 broke an already-installed D2007, given the way that the components and DCUs are not compatible - I suspect a fair number of people will need to have both around for a while (some of us still need D5 and D7 too!)
CodeGear stated (don't have a link handy, sorry) that there should be no conflict. I haven't yet installed D2009 on my workhorse PC so I don't know if that is correct.
The settings in registry have different path and packages have different names so there really should be no problems.
I have Delphi 2007 and I have installed 2009 yesterday with no visible problems so far. Both seem to work fine.
Appears to be no problem. Installed D2009 with TurboDelphi and 2007 and 2, 5 and 7 all on the same Vista machine
Both 2007 and 2009 have Jedi JVC and JVCL installed on them. All appear to work fine. Hope that helps.
.. and if you compile existing packages make sure you give them a new name (e.g. suffix with D12) as each version's BPL directories are in the path.
Installed D2009 Enterprise on VMWare instance running Vista Business with an existing D2007 Enterprise installation. Perhaps I did something incorrectly, but I began to experience errors in the D2007 IDE, as well as a very strange error, unknown fieldtype, in exe files compiled with D2007. I uninstalled D2009, and the errors have gone away.
You should always install the older version first. I tried to install 2009 first and then 2007 but the setup of 2007 failed.
Uninstalling 2009, and starting with 2007 first fixed the install problems.
In theory, it's possible, but if you use many third-party (or your own) libraries, it can get hairy pretty fast. I tend toward developing on Virtual machines, for this and other reasons. But, YMMV.
Should be fine. I have Delphi 7, 2006, 2007, 2009 with 3rd party libs Dev Express and Rem Objects for all (except Dev Express for 2009 - is it out yet?) and all work flawlessly. As others pointed out the versions were installed oldest to newest.
The installations won't interfere with each other, although the Delphi 2009 and Delphi 2007 projects are not compatible, and can't be shared.
Moving along with the order of release is a must. Install older first. Uninstalling may get tricky though.
How to fix Delphi 2009 data explorer?

How to install Delphi 7 on Vista

I tried to install Delphi 7 on Vista several times and Vista prevented me from doing so by telling me that there are known problems with this application (Delphi 7). Several other people in my company experienced problems with installing D7 on Vista.
This lead to the conclusion that we were at risk with our D7 application, as the company could within the lifetime of the app switch to Vista or Windows 7 and newer Delphi versions are not in the policy of the company. Therefore management decided on rewriting the app in C#.
My question(s):
How to install D7 on Vista
Experience with such an installation
Risk assessment concerning stability of IDE and developed programs
Risk assessment concerning executability under Windows 7
Not using any third party components or database - there should be no problem running the developed app under Vista. If not able to develop and debug under Vista (which at the point being will be the only customer platform, yes, internal programming) will result in a sort of cross platform development - if we would be allowed to keep XP as the development platform.
It is not a developers decision to rewrite, it has been done in the company for the last 3 years: if you had to significantly touch an app developed in Delphi or if there was a certain risk of it not to survive the planned life circle/life span, it had to be rewritten. The life cycle just expanded to 2015 due to canceling another project.
So the main issue here would really be: I would like to have educated arguments about the risks.
Running Delphi 7 under Vista is no problem if you can turn UAC off. With UAC on, you get an error message when starting D7, but it still works, just click ok and go on.
Programs compiled with D7 have no problem with Vista. But new features of Vista are supported by Delphi 2007/2009 only.
We use D7 on XP and on Vista, building and maintaining a commercial App which has gone from D2 to D4, D5 to D7. Besides problems with the BDE, which made us switch to DBX (Corelabs) there are no problems.
Just follow these instructions and you'll be fine. No reason to turn off UAC! I've been running Delphi 7 on Vista for about a year without any problem at all. Debugging is totally fine too.
http://www.drbob42.com/examines/examin84.htm
For installing Delphi 7 in Vista, you can try this patch from Microsoft.
http://support.microsoft.com/default.aspx/kb/932246
As for the rest someone else I suspect will have more knowledge.
I have Delphi 7 working fine on my Vista development box. Yes there was a few issues during installation, but no more than other applications and these issues have been resolved in subsequent versions of Delphi.
None of this should cause problems with apps developed by D7 for Vista. We use Delphi as our primary development tool for all our applications and they work just fine with Vista.
It sounds like this is an excuse by someone in the company to get rid of Delphi and move to C#. Typical FUD tactics. There may be genuine reasons for your company to move away from Delphi, but Vista compatibility should not be one of them.
Also, if you'd like all the Vista-ready features in your Delphi 7 application, have a look at this article here: Creating Windows Vista Ready Applications with Delphi
This will make it so that your application correctly appears when doing Flip3D, or when showing a preview thumbnail when hovering over the app in the taskbar. Essentially, this will give you the "Vista-readiness" of Delphi 2007, from within older versions of Delphi (I have used this with Delphi 2006 and it works very well).
You also get the new Vista task dialogs and new Common dialogs with the modifications listed on the linked website.
I think there's a big jump from having trouble installing D7 in Vista (D7 which after all contains low-level bits and pieces for the debugger and which doesn't know about the 'correct' place to put things under Vista), to assuming that your own app will have problems with Vista...
You have the source code, you can test your program running under Vista, you can make whatever (usually minor) tweaks are necessary to your code.... I'm really surprised that you would decide to rewrite the app in another language just because you can't get the (old) development tool to install under Vista.
We need to know more about what your application does, and what components you make use of, to be able to make any guess at your 3rd and 4th questions. They're too general.
FOr instance, I have several D7 applications on the market, one of which uses open-source Interbase 6 with Delphi and can be a problem to get installed/working on Vista Home (the process seems less painful on Vista Business). Another of our apps uses SQL Express 2005 and runs quite happily on Vista. Our newest app, written in D2007, runs fine on Vista. On both Delphi platforms, our two main 'third party' tools are DevExpress controls and ReportBuilder.
I have been using D4 with Vista for year as one of our key products uses it, its good version still and there are workarounds to make it use new Vista features. You can call any win32 API (new functions) so there is no point to update to D7.
I installed/moved D4 to my new machine by hand:
1. by exporting registry hive(s)
2. registering a few components
3. copying files
thats it.. no need to run slow setupper.
As others have noted, there is no problem running Delphi 7 applications under Vista: We do this with a multi-hundred-thousand line Delphi 7 application that uses numerous third-party controls (Developer Express grids, TSILang translation components, etc.).
We use Vista as our primary operating system, but we run the Delphi 7 development environment in a Windows XP Virtual machine. It works perfectly, and there are no installation issues.
It is very simple really.. All what you have to is the following:
Search UAC (User Account Control) off and then intall delphi7 but, you must have no other version of delphi on your computer.
1,2 in Vista) no problems heard if you install http://support.microsoft.com/kb/947562 and configure UAC;
3) None stability issues are known to any of my friends here...
4) Not using Windows 7 with Delphi 7... But heard of many problems with both...

Resources