Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread #12035 Table is not the correct version
Thu, Jan 8 2009 4:14 PMPermanent Link

"John Taylor"
Hello,

I am upgrading my app from dbisam 3 to dbisam 4.

I copied my version 3 tables to a new folder and used dbsys to upgrade
the tables.  I can open the tables fine with dbsys.

When I try to open the tables in my new skeleton app using the
dbisamsession, dbisamdatabase and dbisamtable components, I'm
getting #12035 table is not the correct version

I then tried repairing the tables in dbsys.  I'm still getting the same
error.

I am using DBIsam 4.27 build 3 and I checked to make sure that
the components on the data module are the correct version for
dbisam 4 and that the dbisamdatabase directory is set correctly
to the location of the upgraded tables.

Anyone know what might cause this ?

Thanks.

John Taylor
Thu, Jan 8 2009 5:04 PMPermanent Link

"Robert"

"John Taylor" <jcta@snappysoftware.com> wrote in message
news:765A7263-134D-4D1E-8FA7-47E78E9D812D@news.elevatesoft.com...
>
> I copied my version 3 tables to a new folder and used dbsys to upgrade
> the tables.  I can open the tables fine with dbsys.
>
> When I try to open the tables in my new skeleton app using the
> dbisamsession, dbisamdatabase and dbisamtable components, I'm
> getting #12035 table is not the correct version
>

Obviously, your datamodule is compiled with the V3 components, or you are
pointing to the V3 tables. Have you tried doing a build of the whole
application?

Robert

Thu, Jan 8 2009 9:39 PMPermanent Link

"John Taylor"
not true, all the d2007 executables, v4 libraries are on a removeble
hard drive.  Same drive d2007 and all d2007 compatible components
are installed on and all the library paths point to the same drive


"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote in message
news:B18AED84-7CA6-4DBA-B861-A87C2BA559A2@news.elevatesoft.com...
>
> "John Taylor" <jcta@snappysoftware.com> wrote in message
> news:765A7263-134D-4D1E-8FA7-47E78E9D812D@news.elevatesoft.com...
>>
>> I copied my version 3 tables to a new folder and used dbsys to upgrade
>> the tables.  I can open the tables fine with dbsys.
>>
>> When I try to open the tables in my new skeleton app using the
>> dbisamsession, dbisamdatabase and dbisamtable components, I'm
>> getting #12035 table is not the correct version
>>
>
> Obviously, your datamodule is compiled with the V3 components, or you are
> pointing to the V3 tables. Have you tried doing a build of the whole
> application?
>
> Robert
>
>
Fri, Jan 9 2009 2:21 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

John


I support Robert on this. The only way you should get such an error is if there's a mismatch between the tables and the components. That can only mean the following:

1. The tables are V3 and the components are V4

or

3. The tables are V4 and the components are V3

My bet would be the components. One problem I have encountered on occasions after a component upgrade is that when you look at the component on a form in the IDE it says its the right version BUT because the form hasn't been interactively changed in the IDE a recompile doesn't do anything (the IDE sees no timestamp change on the form so doesn't bother to recompile it).

Check the dcu timestamp. If that looks wrong open the datamodule, insert a space, delete it, save the datamodule and recompile.


Roy Lambert [Team Elevate]
Fri, Jan 9 2009 7:40 AMPermanent Link

"John Taylor"
Robert and Roy,

Thank you both.  The problem was with the table not the components.
A good nights sleep and a fresh look brought things into perspective.





"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:1D249B07-F673-47E4-BA5D-8EABA0227DCF@news.elevatesoft.com...
> John
>
>
> I support Robert on this. The only way you should get such an error is if
> there's a mismatch between the tables and the components. That can only
> mean the following:
>
> 1. The tables are V3 and the components are V4
>
> or
>
> 3. The tables are V4 and the components are V3
>
> My bet would be the components. One problem I have encountered on
> occasions after a component upgrade is that when you look at the component
> on a form in the IDE it says its the right version BUT because the form
> hasn't been interactively changed in the IDE a recompile doesn't do
> anything (the IDE sees no timestamp change on the form so doesn't bother
> to recompile it).
>
> Check the dcu timestamp. If that looks wrong open the datamodule, insert a
> space, delete it, save the datamodule and recompile.
>
>
> Roy Lambert [Team Elevate]
>
Image