Error on updating from version 7.1.14 to 7.1.15

Edison Garcia · Post by **Edison Garcia** » Wed 07 Mar 2012 15:37

Hi
To make a long story short, after installations , unistallations, reinstalations of mydac etc : ....

When I made the updating from MyDac version 7.1.14 to 7.1.15 I experiment an error when trying to start Delphi (2007 in Windows XP pro). The message says something like: " could not found a certain start point in MyDac105.bpl in the directory C:\Arquivos de programas\CodeGear\RAD Studio\5.0\bin. do you want to load in the next time ....

I found that the mydac105.bpl in this directory was from december 2011 and different from the mydac105.bpl present in C:\Arquivos de programas\Devart\MyDAC for RAD Studio 2007\Bin

I copy the bpl from devart bin directory to codegera bin diretory and tryie to start Delphi.

Another error, this time pintint od Dac105.bpl in codebra bin directory - the same fact, was a bpl from december 2011. I copy from dvart bi to codegear bin e everything works fine.

There are something wrong in my instalation. May I remove this bpl from C:\Arquivos de programas\Devart\MyDAC for RAD Studio 2007\Bin ? What I am thinking is why this 2 bpl (Mydac105 e Dac105) are in 2 bin directories ?

thanks
Edison

AndreyZ · Post by **AndreyZ** » Mon 12 Mar 2012 08:59

Hello,

The bpl files in the MyDAC_Install_Dir\Bin directory are not used by an IDE, they are needed in cases like you encountered (to replace the old MyDAC files with the correct ones). MyDAC installation copies all design packages to the IDE\Bin directory and other packages to the C:\Windows\System32 directory. The IDE uses MyDAC packages from these two directories. The problems you encountered show that the IDE tries using the old and new MyDAC files at the same time. The correct way to handle such situations is to perform the following steps:
- remove MyDAC;
- remove all the *dac*.bpl and *crcontrols*.bpl files from your computer;
- remove the *.dcu files from your project;
- reinstall MyDAC.

Edison Garcia · Post by **Edison Garcia** » Mon 19 Mar 2012 17:36

I noted that this error occurs in machines whre you have myDac and UniDac installed.

I had to re-install my machine, and after restore an complete image of the drive I update MyDac and after that update UniDac and get the error

Re-install another time from image - remove UniDac, update MyDac e no error at all - install UniDac and the error comoes back

Edison

AndreyZ · Post by **AndreyZ** » Tue 20 Mar 2012 08:11

All DAC components share common engine, and that is why product compatibility is provided for the current build. To make MyDAC and UniDAC work simultaneously on the same IDE, you should use the compatible versions of them. The latest compatible versions are the following: MyDAC 7.1.5, UniDAC 4.1.5 .

Edison Garcia · Post by **Edison Garcia** » Tue 20 Mar 2012 13:06

Ok Andrey2.

My problem of update the versions of MyDac and UnDac I had solved.

My intention in post this topic was try to show to Devart that it has some problem with the updates at least in some conditions, and not to start a argument about to have or not the correct versions, where to have bpls aqn how IDE uses it or not etc I use MyDac at least for 6 or 7 years and never had any kind of problem during the updates.

I know and I was using the two correct versions of MyDac and UniDac (7.1.5 and 4.1.5) and for the last time I will repeat it: I was using the correct versions and get the problem.

I will not post anything more about this topic. If Devart decides to look for some problem in the update routines: good for you! If decides not to look: good for you also!

AndreyZ · Post by **AndreyZ** » Tue 20 Mar 2012 13:44

We already have several ideas of improving the DAC upgrading process. We will make upgrading easier in the nearest future.