Rio: Unit PgAccess was compiled with a different version of CRTypes.pidDevartPla

Discussion of open issues, suggestions and bugs regarding PgDAC (PostgreSQL Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
upscene
Posts: 306
Joined: Thu 19 Oct 2006 08:13

Rio: Unit PgAccess was compiled with a different version of CRTypes.pidDevartPla

Post by upscene » Mon 17 Feb 2020 06:32

Hi,

I've got MyDAC, SDAC, IBDAC and ODAC installed. All work fine, but in Delphi Rio (10.3), I get this error when compiling a project with the latest PgDAC version:

Code: Select all

[dcc32 Fatal Error] uDBW_PgSQL.pas(6): F2051 Unit PgAccess was compiled with a different version of CRTypes.pidDevartPlatforms
Any idea?

With regards,

Martijn Tonies

MaximG
Devart Team
Posts: 1822
Joined: Mon 06 Jul 2015 11:34

Re: Rio: Unit PgAccess was compiled with a different version of CRTypes.pidDevartPla

Post by MaximG » Thu 27 Feb 2020 15:50

Please verify that you use the latest version of our products. Remove all installed Devart DAC products, then verify that all .dcu, .dcp и .bpl files associated with our products have been completely removed from the system (make sure the search for dac260.dcp, dac260.bpl, dac*260.dcu doesn't return any results). After that, install the latest versions of our products again.

upscene
Posts: 306
Joined: Thu 19 Oct 2006 08:13

Re: Rio: Unit PgAccess was compiled with a different version of CRTypes.pidDevartPla

Post by upscene » Tue 03 Mar 2020 08:12

I did that, twice.

oleg0k
Devart Team
Posts: 190
Joined: Wed 11 Mar 2020 08:28

Re: Rio: Unit PgAccess was compiled with a different version of CRTypes.pidDevartPla

Post by oleg0k » Mon 16 Mar 2020 15:41

Hello,
Are you still having that issue? Try using the latest version of DAC, which was released a few days ago.
Let us know if this helps.

wbr, Oleg

MaximG
Devart Team
Posts: 1822
Joined: Mon 06 Jul 2015 11:34

Re: Rio: Unit PgAccess was compiled with a different version of CRTypes.pidDevartPla

Post by MaximG » Wed 29 Apr 2020 10:53

Our users haven't reported such an issue after the latest release of our products.

Post Reply