Because SetRange was not working properly for me after hours of chasing it
with 4.21, I just downloaded and installed 4.27. The installation went OK
and I adjusted the Library paths and deleted all DCUs but continue to get
this error:

"Unit dbisamsq was compiled with a different version of
dbisamst.DBISAM_TYPESTR_INT32"

I even had the library point to the DBISAM code source and still get it.

How to fix this?

Jerry

I should note that this is urgent as I can compile nothing now.
Jerry

"Jerry Clancy" <jclancy@billtrak.com> wrote in message
news:1285AC99-14A4-4899-BF84-7C16977308E9@news.elevatesoft.com...
> Because SetRange was not working properly for me after hours of chasing it
> with 4.21, I just downloaded and installed 4.27. The installation went OK
> and I adjusted the Library paths and deleted all DCUs but continue to get
> this error:
>
> "Unit dbisamsq was compiled with a different version of
> dbisamst.DBISAM_TYPESTR_INT32"
>
> I even had the library point to the DBISAM code source and still get it.
>
> How to fix this?
>
> Jerry
>

While I haven't yet found the abberent DCU, we have solved this issue by
moving the dbisam code library ahead of the IntraWeb one in the Tools
library paths.

We are productive and now a happy camper again.

Jerry

"Jerry Clancy" <jclancy@billtrak.com> wrote in message
news:1285AC99-14A4-4899-BF84-7C16977308E9@news.elevatesoft.com...
> Because SetRange was not working properly for me after hours of chasing it
> with 4.21, I just downloaded and installed 4.27. The installation went OK
> and I adjusted the Library paths and deleted all DCUs but continue to get
> this error:
>
> "Unit dbisamsq was compiled with a different version of
> dbisamst.DBISAM_TYPESTR_INT32"
>
> I even had the library point to the DBISAM code source and still get it.
>
> How to fix this?
>
> Jerry
>

As this problem is solved, I also want to say that SetRange was working
properly even earlier. The problem turned out to be a truncated list because
years ago I had set a max row value on a grid and totally forgot about it
until I finally had one of those "Eureka" moments. All is working as
intended now.

Jerry

"Jerry Clancy" <jclancy@billtrak.com> wrote in message
news:1285AC99-14A4-4899-BF84-7C16977308E9@news.elevatesoft.com...
> Because SetRange was not working properly for me after hours of chasing it
> with 4.21, I just downloaded and installed 4.27. The installation went OK
> and I adjusted the Library paths and deleted all DCUs but continue to get
> this error:
>
> "Unit dbisamsq was compiled with a different version of
> dbisamst.DBISAM_TYPESTR_INT32"
>
> I even had the library point to the DBISAM code source and still get it.
>
> How to fix this?
>
> Jerry
>

Jerry,

<< I even had the library point to the DBISAM code source and still get it.

How to fix this? >>

Did you try a Build instead of a Compile ?  Usually, this type of thing is
caused by a .pas file not being compiled to match other .dcus that are
referencing it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Yeah, I was smart enough to do that. Also wiped out all DCUs, etc. The
problem was the library path. The path immediately above the one for dbisam
had the culprit DCU. Correcting the path hierarchy solved it. Thanks for the
thought, nonetheless.

Jerry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:D6D47C31-C40D-45A5-A764-82A69CACA04C@news.elevatesoft.com...
> Jerry,
>
> << I even had the library point to the DBISAM code source and still get
> it.
>
> How to fix this? >>
>
> Did you try a Build instead of a Compile ?  Usually, this type of thing is
> caused by a .pas file not being compiled to match other .dcus that are
> referencing it.
>>