Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Cannot open tables from v4.27 in v4.41 using Dbsys
Thu, Sep 3 2015 12:13 AMPermanent Link

Kong Aw

In my v4.27 version of dbsys I have the following initialization for the MainForm:

Initialization
  Engine.EngineSignature := 'mct#####';            {akk}
  Engine.LargeFileSupport := True;
  Engine.TableDataTempExtension := '.edat';        {akk}
  Engine.TableIndexTempExtension := '.eidx';
  Engine.TableBlobTempExtension := '.eblb';        {akk}  

I added this same initialization to the v4.41 version of dbsys.

I can compile the new dbsys but when I try to open or upgrade tables I get the following error 12036.

What have I missed?

KK Aw
Thu, Sep 3 2015 1:14 AMPermanent Link

Raul

Team Elevate Team Elevate

On 9/3/2015 12:13 AM, Kong Aw wrote:
> I can compile the new dbsys but when I try to open or upgrade tables I get the following error 12036.
> What have I missed?

This error i believe indicates that your engine signature does not match.

The dbsys now allows most of those settings to be controlled directly
thru INI so my guess is that your changes get over-ridden when actual
INI settings are read (which likely happens after in code after main
form is initialized).


Raul
Thu, Sep 3 2015 1:18 AMPermanent Link

Kong Aw

The problems seem to have gone away after I put back some of the changes I have made to the codes.

BTW, when I use the tables created by v4.27 with newer version of Dbisam 4 what do I need to do to make sure that the blob structure is up-to-date? Should I alter, repair or upgrade the tables?

KK Aw
Thu, Sep 3 2015 3:42 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

KK,

<< BTW, when I use the tables created by v4.27 with newer version of Dbisam 4 what do I need to do to make sure that the blob structure is up-to-date? Should I alter, repair or upgrade the tables?  >>

You don't need to do anything special.  Just make sure that you don't use an older version of DBISAM on those same tables.

Tim Young
Elevate Software
www.elevatesoft.com
Image