Try OpenEdge Now
skip to main content
Managing ABL Applications
R-code Features and Functions : Database CRCs and time stamps : CRC versus time stamp validation

CRC versus time stamp validation

The main advantage of using CRC validation is that you can run the same r-code against different databases as long as the databases have sufficiently similar schemas. This allows you to deploy code and database updates while avoiding either of the following effects:
*Forcing the user to dump and reload their data into a new database that you supply with new r-code.
*Forcing the user to compile new source code (possibly encrypted) that you supply with new data definitions to update their database schema.
Depending on the schema changes, the user still might have to dump and reload some data, but you can always supply r-code for their updated database.
* Database changes that affect time stamps
* Database changes that affect CRCs
* Database CRC changes that do not prevent r-code execution
* Time stamp-based deployment
* CRC-based deployment
* Differences in r-code access authorization
* CRC and time stamp availability