Hi Tim,

From the manual:

"RecordHash - This property is no longer necessary. ElevateDB does not
use record hashes."

May I ask why this is no longer available in ElevateDB?

Best regards,
Fons Neelen

--

Fons,

<< May I ask why this is no longer available in ElevateDB? >>

Because it isn't necessary anymore.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> Because it isn't necessary anymore.

Can you elaborate on this? Has it been replaced by something?

Thanks,
Fons


--

Fons,

<< Has it been replaced by something?  >>

Yes, a simple update counter.  DBISAM used the hash value to determine
whether a row had changed, and EDB simply uses an update counter.  The
update counter is more efficient and can track BLOB column changes also,
which DBISAM could not do with the hash value.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim, could you write code how to access "update counter" for selected record?

I am trying to move our application from DBISAM to ElevateDB and I need to update DBISAMQuery.RecordHash

Tomas,

<< Tim, could you write code how to access "update counter" for selected
record? >>

The update counter is not accessible from outside of the internal ElevateDB
engine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Now I am not sure how to track record changes, in DBISAM 4.x I have used code below
to find out record changes. How to do this in ElevateDB?

if AOldRecordHash <> qDocument.RecordHash then <Record Updated>

Tomas,

<< Now I am not sure how to track record changes, in DBISAM 4.x I have used
code below to find out record changes. How to do this in ElevateDB? >>

You'll have to track changes via your own method, such as a column for
holding the last update date/time stamp.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim
There was a thread awhile back about calculating record hashes so they could add the hash field in, naminging whatever it is in DBISAM, calculate in a before post trigger and keep on as they are.

That would make a nice little enhancement to make for ElevateDB - calculate record hash.

Roy Lambert

Roy,

<< That would make a nice little enhancement to make for ElevateDB -
calculate record hash. >>

Actually no, it wouldn't.  The record hashes in DBISAM were problematic
in that they didn't include the BLOB data.  ElevateDB doesn't have this
issue *because* it doesn't use record hashes.

--
Tim Young
Elevate Software
www.elevatesoft.com