Prev: Problem with ODBC XLS
Next: Search in Treeview values
From: Takumo on 14 Feb 2010 05:03
Hi all!
Created an app in VO 2.7. All is working fine, RDD - DBFCDX. Several
DBFs.
Then moved this app to VO 2.8. All data files were merely copied in
another folder. No changes in the code. All is working as expected.

But now I found out that the size of 2 DBFs changed - in VO they
become 1 byte longer.

Clients.dbf: VO2.7 - 3058 b., VO 2.8 - 3059 bytes.
Advokat.dbf: VO 2.7 - 636 b., VO 2.8 - 637 bytes.

Plus 1 byte in both cases.
Used VO 2.8 SP3 and VO 2.7b (2740).

Any ideas?
From: Geoff Schaller on 14 Feb 2010 06:25
Wow! One whole byte!

<g>

Seriously... are you worried? Open the DBF with a Hex editor and inspect
the last byte. I suspect an EOF character has been added by the file
copy process. Ignore it. DBF can live or without this character but its
existence may help other processes.

Geoff



"Takumo" <advokat.bond(a)gmail.com> wrote in message
news:4a5db6bc-a59e-4004-8cb3-e314f2465ab0(a)j31g2000yqa.googlegroups.com:

> Hi all!
> Created an app in VO 2.7. All is working fine, RDD - DBFCDX. Several
> DBFs.
> Then moved this app to VO 2.8. All data files were merely copied in
> another folder. No changes in the code. All is working as expected.
>
> But now I found out that the size of 2 DBFs changed - in VO they
> become 1 byte longer.
>
> Clients.dbf: VO2.7 - 3058 b., VO 2.8 - 3059 bytes.
> Advokat.dbf: VO 2.7 - 636 b., VO 2.8 - 637 bytes.
>
> Plus 1 byte in both cases.
> Used VO 2.8 SP3 and VO 2.7b (2740).
>
> Any ideas?

From: Jean3Riv on 14 Feb 2010 14:55
On 14 fév, 05:03, Takumo <advokat.b...(a)gmail.com> wrote:
> Hi all!
> Created an app in VO 2.7. All is working fine, RDD - DBFCDX. Several
> DBFs.
> Then moved this app to  VO 2.8. All data files were merely copied in
> another folder. No changes in the code. All is working as expected.
>
> But now I found out that the size of 2 DBFs changed - in VO they
> become 1 byte longer.
>
> Clients.dbf: VO2.7 - 3058 b., VO 2.8 - 3059 bytes.
> Advokat.dbf: VO 2.7 - 636 b., VO 2.8 - 637 bytes.
>
> Plus 1 byte in both cases.
> Used  VO 2.8 SP3 and VO 2.7b (2740).
>
> Any ideas?

If you look with an hex editor...
When creating a DBF or copy it, then the header termination bytes are
as follow:
CAVO25 = 0d00 // 0d + NULL byte
CAVO26 = 0d // 0d
CAVO27 = 0d // 0d
CAV028 = 0d00 // 0d + NULL byte

Since the standard DBF structure is design to terminate with 0d00
they just corrected the design in version 2.8 as it should be

This is your byte of difference

Jean Raymond
www.rayonline.com
From: Takumo on 14 Feb 2010 16:34
Thank you, guys.

I compared the headers and found this last additional byte - 00 in
VO2.8.
Now I know a bit more :) .

Thanks.
 | 
Pages: 1
Prev: Problem with ODBC XLS
Next: Search in Treeview values