Hello;
Stats DBISAM 4.25
I included
“Engine.largeFileSupport := true” in an application I wrote to build a table from an existing table.. I was expecting to see 6,207984 records but I can only see 5,739012 records using
Dbsys.
I know there are more records than that because of the size of the data and index files 2,259,221 KB and 1,479,603 Kb resp. and the time it took to build.
Now I need to look at the table and run some queries on it using DBsys.exe

Questions:
1) Am I risking corruption of table header records if I use the existing dbsys.exe?
2)  Should I recompile dbsys and add the "Engine.largeFileSupport  := true" code?

if yes to 2 ; I tried to recompile dbsys with the new code but am getting the errors at compile time(see in the attached file).
When I remove the “versioninfo.res” file ; I can compile DBsys; but,  then I'm getting errors on the close of the application.  Errors that the OS wants of send to MS.

I am still seeing only 5.7m records. This may be correct in that yesterday I tried to take a peek at the file with the "original dbsys.exe" and received a message warning me that the
header may get corrupt.  I could have corrupted the header??

Please Advise

Allan

Allan,

<< “Engine.largeFileSupport := true” in an application I wrote to build a
table from an existing table.. I was expecting to see 6,207984 records but I
can only see 5,739012 records using Dbsys. >>

The LargeFileSupport property has no bearing on the number of rows in the
table until you hit 200,000,000 rows.  And, even then, it simply prevents
any more rows from being added.

<< 1) Am I risking corruption of table header records if I use the existing
dbsys.exe? >>

No, unless other users are currently using the table and you plan on
modifying the table.  The LargeFileSupport property does not change anything
about the actual tables themselves.  It simply controls how locking is
performed on the table.

<< if yes to 2 ; I tried to recompile dbsys with the new code but am getting
the errors at compile time(see in the attached file).  When I remove the
“versioninfo.res” file ; I can compile DBsys; but,  then I'm getting errors
on the close of the application.  Errors that the OS wants of send to MS. >>

Did you rename the project or re-create it in any way ?

<< I am still seeing only 5.7m records. This may be correct in that
yesterday I tried to take a peek at the file with the "original dbsys.exe"
and received a message warning me that the header may get corrupt.  I could
have corrupted the header?? >>

Not by just looking at the table contents.  More than likely the table got
corrupted in some other fashion, and it has nothing to do with the
LargeFileSupport property.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Allan,

<< “Engine.largeFileSupport := true” in an application I wrote to build a
table from an existing table.. I was expecting to see 6,207984 records but I
can only see 5,739012 records using Dbsys. >>

The LargeFileSupport property has no bearing on the number of rows in the
table until you hit 200,000,000 rows.  And, even then, it simply prevents
any more rows from being added.

<< 1) Am I risking corruption of table header records if I use the existing
dbsys.exe? >>

No, unless other users are currently using the table and you plan on
modifying the table.  The LargeFileSupport property does not change anything
about the actual tables themselves.  It simply controls how locking is
performed on the table.

<< if yes to 2 ; I tried to recompile dbsys with the new code but am getting
the errors at compile time(see in the attached file).  When I remove the
“versioninfo.res” file ; I can compile DBsys; but,  then I'm getting errors
on the close of the application.  Errors that the OS wants of send to MS. >>

Did you rename the project or re-create it in any way ?

<< I am still seeing only 5.7m records. This may be correct in that
yesterday I tried to take a peek at the file with the "original dbsys.exe"
and received a message warning me that the header may get corrupt.  I could
have corrupted the header?? >>

Not by just looking at the table contents.  More than likely the table got
corrupted in some other fashion, and it has nothing to do with the
LargeFileSupport property.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim;
Thanks. I was a bit gun shy on this

Allan