R-code execution with CRCsSave PDFSave selected topicSave selected topic and subtopicsSave all topicsShareShare to emailCopy topic URLPrintLast Updated: February 11, 20261 minute readOpenEdgeVersion 13.0Documentation R-code execution with CRCs When executing a procedure using CRC validation, OpenEdge follows these steps: For each table accessed by the r-code, check the time stamp. If it matches, execute the procedure. Otherwise, go to Step 2. Check the CRC. If it matches, execute the procedure. Otherwise, reject the procedure. Thus, if the time stamps match, OpenEdge assumes that the database schema and r-code must be compatible. Otherwise, the CRCs determine the outcome.
R-code execution with CRCs When executing a procedure using CRC validation, OpenEdge follows these steps: For each table accessed by the r-code, check the time stamp. If it matches, execute the procedure. Otherwise, go to Step 2. Check the CRC. If it matches, execute the procedure. Otherwise, reject the procedure. Thus, if the time stamps match, OpenEdge assumes that the database schema and r-code must be compatible. Otherwise, the CRCs determine the outcome.
R-code execution with CRCs When executing a procedure using CRC validation, OpenEdge follows these steps: For each table accessed by the r-code, check the time stamp. If it matches, execute the procedure. Otherwise, go to Step 2. Check the CRC. If it matches, execute the procedure. Otherwise, reject the procedure. Thus, if the time stamps match, OpenEdge assumes that the database schema and r-code must be compatible. Otherwise, the CRCs determine the outcome.