Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread  "Unit dbisamsq was compiled with a different version of dbisamst.DBISAM_TYPESTR_INT32"
Tue, Sep 11 2012 7:52 AMPermanent Link

Roger-Ash

Hi, apologies for the double post - originally posted this under General Discussion by mistake.

I finally got around to upgrading to DBISAM 4.33 (from 4.10!)
Trying to compile the demo app, I get the message above.
I found a similar problem on here relating to 4.27 and tried following the instructions to fix the problem.
I've uninstalled, re-installed, checked for old versions, all to no avail.
It seems that the only way I can the program to compile is to copy all the source into the code directory.

I'd be grateful for any suggestions.
Mon, Oct 1 2012 10:51 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roger,

<< I finally got around to upgrading to DBISAM 4.33 (from 4.10!)
Trying to compile the demo app, I get the message above.
I found a similar problem on here relating to 4.27 and tried following the
instructions to fix the problem.
I've uninstalled, re-installed, checked for old versions, all to no avail.
It seems that the only way I can the program to compile is to copy all the
source into the code directory. >>

Per email:

=======================================================

Did you modify the dbisamst.pas unit at all ?  If not, then make sure to
delete all dbisam*.pas units that may be located in the compiler search
path, and make sure that it's all just dbisam*.dcu files from the 4.33
installation.  That should fix the problem.

At one point in the 4.x release cycle a couple of .pas units got included in
the \code subdirectory by accident due to some changes in the build system,
and that's what you're seeing the remnants of.

Tim Young
Elevate Software
www.elevatesoft.com
Image