Installing FireDAC 8 for Delpi 2007
Posted by jpluimers on 2015/08/19
Installing FireDAC 8 for Delpi 2007
Installation
- Obtain
29458_firedac_xe4_update_2_for_rad_studio_delphi_c_ent_ult_arch.zipfrom a registered Delphi XE4 or higher license: http://cc.embarcadero.com/item/29458: - Extract it into
FireDAC_8.0.5.3365.exe. - Run
FireDAC_8.0.5.3365.exewith the/showideparameter as described in http://support.embarcadero.com/article/42970: FireDAC_8.0.5.3365.exe /showide- (When not running as Administrator: elevate to Administrator)
- Welcome screen: press
next - License screen: accept, then press
next - Destination selection screen: keep
C:\Program Files (x86)\Embarcadero\FireDAC, then pressnext - Select components screen: keep the selection (Full installation), then press
next - Select IDEs screen: choose Delphi 2007 (but not Delphi 2006), then press
next - Select Demo Databases screen: keep the settings (do not choose
Interbase / Firebird serveras then you have to provide the credentials for the server), then pressnext - Start menu screen: keep
Embarcadero FireDAC, then pressnext - Ready to install screen: press
install - After installation: press
finish, then read thereadme- or later browse to <file:///C:/Program%20Files%20(x86)/Embarcadero/FireDAC/Readme.html>
- That’s what actually tells you:
The installer automatically installs FireDAC in the Delphi XE4 and C++ Builder XE4 IDEs. For older versions of the IDEs, you can run the installer with the /SHOWIDE command line parameter.
After installation
To fix this when starting Delphi:
[Window Title] Error [Content] Can't load package C:\Users\Public\Documents\RAD Studio\5.0\Bpl\AnyDAC_Dcl_D11.bpl. The specified module could not be found. Do you want to attempt to load this package the next time a project is loaded? [Yes] [No]
The actual BPL sometimes is in C:\Users\<username>\AppData\Local\Documents\RAD Studio\5.0\Bpl\AnyDAC_Dcl_D11.bpl
The cause is that the BPL gets loaded from %BDSCOMMONDIR% which on some systems points to
%PUBLIC%\Documents\RAD Studio\5.0
and on others points to
%LOCALAPPDATA%\Documents\RAD Studio\5.0
This seems to be the case on machines where more different Windows users are using Delphi.
The installer does not fully recognize this distinction, so copies the BPL to %LOCALAPPDATA%\Documents\RAD Studio\5.0\Bpl and registers it as being in %PUBLIC%\Documents\RAD Studio\5.0\Bpl.
On these machines there is a difference between the definition of BDSCOMMONDIR in these registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment- points to
C:\Users\Public\Documents\RAD Studio\5.0
- points to
HKEY_CURRENT_USER\Environment- points to
C:\Users\<username>\AppData\Local\Documents\RAD Studio\5.0
- points to
Solution
reg delete "HKCU\Software\Borland\BDS\5.0\Known Packages" /v "%PUBLIC%\Documents\RAD Studio\5.0\Bpl\AnyDAC_Dcl_D11.bpl" /f reg add "HKCU\Software\Borland\BDS\5.0\Known Packages" /v "%BDSCOMMONDIR%\Bpl\AnyDAC_Dcl_D11.bpl" /t REG_SZ /d "Embarcadero FireDAC Components" /f
–jeroen
The Wiert Corner - irregular stream of stuff 
NCook said
When we use FireDAC in Delphi 2007, our applications wont run correctly until we turn OFF the “Optimisation” check box in the compiler options for the project, and the rebuild the application.
We are using the version of FireDAC indicated above (8.0.5.3365).
With optimisation turned ON, we get an Access violation as soon as we attempt to open a FireDAC object (eg: TADQuery). The same code works perfectly with optimisation turned OFF.
Is anyone else having the same problem?
Does anyone have any idea what could be causing this, or even better, have a solution?
jpluimers said
We didn’t have that with our InterBase application. Or maybe we didn’t bump into it yet. What database are you using? Can you reproduce it with a very small application? If so, can you post it somewhere?
Peter said
Use ZEOS and you have no problems anymore.
jpluimers said
Been there, done that. Zeos has it’s own share of problems.
Or on others words: “Lets try another library. Now I’ve two problems”.