Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Compiled with a different version issue
Thu, Jan 24 2008 12:10 PMPermanent Link

Jon Lloyd Duerdoth
I've updated to newer releases of DBISAM many times with no problem
(in the past) Updating from 4.25 to 4.26 caused me a problem that
I have yet to track down.

I uninstalled 4.25 and all dependent modules.
I changed the folder names of previously installed (added an x) to hide
them from Delphi (just in case)
I installed 4.26 to a custom folder
I re-installed some dependent custom modules (recompiling them)
Reloaded my app and tried to re-compile


Ended up with dbisamen was compiled with a different version
of dbisam engine.

I did check all the library paths etc but I'm obviously missing
something (& I know it will be sooo simple Frown )

Any guesses as to what I missed?

Jon
Thu, Jan 24 2008 2:29 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jon,

<< Ended up with dbisamen was compiled with a different version of dbisam
engine. >>

See here:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=5&msg=60400&page=1#msg60400

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Jan 24 2008 6:40 PMPermanent Link

"Walter Matte"
I had a bit more trouble doing the 4.26 upgrade too...

Not only did already clean 4.25 and all DBISAM dcu's.... but I had to clean
dependant components.... ReportBuilder End User, Active Query Builder DBISAM
..... when I deleted all them, installed 4.26, recompiles other bpl's,
dcu's.. and reinstalled other components... all was well.

Walter


"Jon Lloyd Duerdoth" <jld@welshdragoncomputing.ca> wrote in message
news:F8F7A57D-F340-4DAF-8F62-D974172AB8BA@news.elevatesoft.com...
> I've updated to newer releases of DBISAM many times with no problem
> (in the past) Updating from 4.25 to 4.26 caused me a problem that
> I have yet to track down.
>
> I uninstalled 4.25 and all dependent modules.
> I changed the folder names of previously installed (added an x) to hide
> them from Delphi (just in case)
> I installed 4.26 to a custom folder
> I re-installed some dependent custom modules (recompiling them)
> Reloaded my app and tried to re-compile
>
>
> Ended up with dbisamen was compiled with a different version
> of dbisam engine.
>
> I did check all the library paths etc but I'm obviously missing
> something (& I know it will be sooo simple Frown )
>
> Any guesses as to what I missed?
>
> Jon

Fri, Jan 25 2008 1:04 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Walter,

<< Not only did already clean 4.25 and all DBISAM dcu's.... but I had to
clean dependant components.... ReportBuilder End User, Active Query Builder
DBISAM .... when I deleted all them, installed 4.26, recompiles other bpl's,
dcu's.. and reinstalled other components... all was well. >>

Yeah, it all goes back to the flaky dbisamtb.pas unit included with the
installation.  It needs to go into the \source subdirectory so that it won't
be re-compiled.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sun, Jan 27 2008 7:39 PMPermanent Link

Jon Lloyd Duerdoth
Deleting dbisamtb.pas fixed thanks.

There was already a copy in the source folder.

Jon

Tim Young [Elevate Software] wrote:
> Walter,
>
> << Not only did already clean 4.25 and all DBISAM dcu's.... but I had to
> clean dependant components.... ReportBuilder End User, Active Query Builder
> DBISAM .... when I deleted all them, installed 4.26, recompiles other bpl's,
> dcu's.. and reinstalled other components... all was well. >>
>
> Yeah, it all goes back to the flaky dbisamtb.pas unit included with the
> installation.  It needs to go into the \source subdirectory so that it won't
> be re-compiled.
>
Image