Devart Forums

I've just downloaded and installed ODAC 8.2.8 for Delphi XE2, and Devart Oracle Data Access Components (dclodac160.bpl) has dependencies on FMX (Firemonkey Max OSX) packages.

I have a Windows only application with reliance on a Windows only package that needs to reference Devart Oracle Data Access Components, but it now has a requirement on FireMonkey packages! Why???? This is unnecessary and because of this I am now unable to build our applications and I can't uninstall FMX packages.

There should be NO dependencies from a Windows package to FireMonkey package - this is a mistake, I can understand that the other way round may be required but that should be scoped accordingly. Please can you address this as soon as possible!

I think the problem is in the dclodac160.dpk source, and a reference (probably unnecessarily) to odacfmx160 highlighted below....

requires
odac160,
dcldb,
dcldac160,
odacvcl160,
odacfmx160,
designide;

Perhaps it needs removing or made conditional. Either way it is currently incorrect. When can you release a fix?

requires
odac160,
dcldb,
dcldac160,
odacvcl160,
{$IFDEF POSIX}
odacfmx160,
{$ENDIF}
designide;

hello,

Thank you for the information, we know about this problem.
At the time being, our products require FireMonkey packages to be installed, we will try to remove this dependence in the next version.

AlexDP

Whilst I appreciate your reply it doesn't help me to build and deliver our application to our customers, who are currently screaming at me for delivery of a critical fix. At the moment I am stuck, as like I said, we have our own packages dependent on dclodac160, and FireMonkey is not installed.

On further investigation, I believe the problem is that OraReg.pas (which registers items for dclodac160.dpk) refers to OdacFMX in its uses clause and also TConnectDialogFmx in its register clause when you are using Delphi XE2, regardless of the target platform requirements. This in turn then links in practically all of the FMX library - completely unnecessary, unwarranted and poor implementation.

Problem lines are below in red.... I think you either need another conditional define - outside of the {$IFDEF VER16P} Delphi XE2 conditional to avoid this situation or an OraRegFMX.pas to correct your incorrect dependency issues.

unit OraReg;

uses
Classes, DB,
[SNIP...]

OdacVcl, {$IFDEF VER16P}OdacFmx,{$ENDIF}
DacReg, DBAccess, Ora, OraSmart, OraScript

[SNIP...]

{$IFDEF VER16P}
RegisterComponents('Oracle Access', [TConnectDialogFmx]);
{$ENDIF}

Any news on resolution for this issue?!

hello,

Yes, it will be enough for you to delete these lines for ODAC compilation without installed FireMonkey. As I wrote earlier, we will fix this problem in the next versions

OK, well it seems no update of ODAC is imminent, so I tried to fix this FMX dependency issue myself which worked. I built the components and installed them.

However, trying to build any project using these ODAC components gives me Seeing as OraNet is only provided as a dcu, I'm pretty much stuck!

Any ideas?

Has ODAC 8.5 finally addressed this incorrect FMX package dependency issue?

Hello

We have resolved the issue with FMX dependencies. This fix will be included in the next build (8.5.10), that we plan to release in few weeks.

Can the fix be released any sooner? I've been waiting over a month for this already!!!

hello,

Please send your license number and e-mail to alexp*devart*com, in order that we can send you the fixed version of ODAC