• <GetStart>
  • CSPro User's Guide
    • The CSPro System
    • Data Dictionary Module
    • The CSPro Language
    • Data Entry Module
      • Introduction to Data Entry
      • Data Entry Application
      • Data Entry Editing
        • Introduction to Data Entry Editing
        • Editing Concepts
        • Writing Logic
          • Data Entry Logic Screen Layout
          • Moving Around a Logic Application
          • Order of Executing Data Entry Events
          • Sequence Dictated by Designer
          • Run as Batch
      • CAPI Data Entry
      • Network Data Entry
      • Android Data Entry
    • Batch Editing Applications
    • Tabulation Applications
    • Data Sources
    • CSPro Statements and Functions
    • Templated Reporting System
    • HTML and JavaScript Integration
    • Action Invoker
    • Appendix
  • <CSEntry>
  • <CSBatch>
  • <CSTab>
  • <DataViewer>
  • <TextView>
  • <TblView>
  • <CSFreq>
  • <CSDeploy>
  • <CSPack>
  • <CSDiff>
  • <CSConcat>
  • <Excel2CSPro>
  • <CSExport>
  • <CSIndex>
  • <CSReFmt>
  • <CSSort>
  • <ParadataConcat>
  • <ParadataViewer>
  • <CSCode>
  • <CSDocument>
  • <CSView>
  • <CSWeb>

Moving Around a Logic Application

To move around your edit application, select individual items from the Forms (in a data entry application) or Edits (in a batch application) tree tab. The logic view will update to display the programming logic (if any) for that item. If you select the root of the tree, all logic written for the entire edit application is displayed.
For example, suppose you select AGE from the tree and there is no associated programming logic, you will see in the logic view:
PROC AGE
Since there is no logic, PROC AGE is generated "on-the-fly" and will not be saved in the logic file. If there was associated logic, you might see something like this:
PROC AGE

   
if not ( AGE in 0:99 ) then
       
errmsg("Invalid age found");
   
endif;