Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Converting App Issue V3 to V4
Mon, Oct 26 2009 8:37 AMPermanent Link

"Al Vas"
Hi,

Just playing around and scoping a version change and after upgrading the
database from V3 to V4 I receive an error on running the application as
follows:

EReadError with message 'Error reading TDBISAMFieldDef.Size: Invalid field
size'

As we have a lot of fields, any ideas which particualr field type might be
causing this issue?

Thanks

Alex
Mon, Oct 26 2009 1:43 PMPermanent Link

"Robert"

"Al Vas" <noreply@noreply.com> wrote in message
news:1B7C772C-CB05-4239-BCD5-A18A89301CA4@news.elevatesoft.com...
> Hi,
>
> Just playing around and scoping a version change and after upgrading the
> database from V3 to V4 I receive an error on running the application as
> follows:
>
> EReadError with message 'Error reading TDBISAMFieldDef.Size: Invalid field
> size'
>
> As we have a lot of fields, any ideas which particualr field type might be
> causing this issue?
>

The result of aggregate functions in queries is now a large integer. That
might be the problem

Robert

> Thanks
>
> Alex

Tue, Oct 27 2009 7:00 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

<< Just playing around and scoping a version change and after upgrading the
database from V3 to V4 I receive an error on running the application as
follows:

EReadError with message 'Error reading TDBISAMFieldDef.Size: Invalid field
size' >>

Do you get the error when you open the table using the V4 DBSYS utility ?
If not, then there's an issue with the field definitions (FieldDefs) for a
TDBISAMTable or TDBISAMQuery component, most likely they are stored in the
form or data module (StoreDefs=True) and they are not valid for DBISAM 4.x.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image