• <GetStart>
  • CSPro User's Guide
    • The CSPro System
    • Data Dictionary Module
    • The CSPro Language
      • Introduction to CSPro Language
      • Data Requirements
      • CSPro Program Structure
      • Programming Standards
      • Code Folding
      • Debugging CSPro Applications
      • Declaration Section
      • Procedural Sections
        • Statements
        • Proc Statement
        • PreProc Statement
        • OnFocus Statement
        • OnOccChange Statement
        • KillFocus Statement
        • PostProc Statement
      • Logic
      • Language Elements
    • Data Entry Module
    • 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>

KillFocus Statement

Format
killfocus
Description
The killfocus statement declares that the statements following it are executed when a form, roster, or field stops being active.
Statements in an killfocus procedure are executed when you move off the object in which they are coded. When moving forward, any killfocus statements are executed before any postproc statements. However, when moving backward, the postproc statements are not executed and only the killfocus statements are executed.
The killfocus statement is not very common as most logic operations and checks only occur when moving forward in the application, in which case they can be coded in a postproc.
Example
PROC CEB_MALE

killfocus

    CEB_TOTAL = 
visualvalue(CEB_MALE) + visualvalue(CEB_FEMALE);
See also: Proc Statement, PreProc Statement, OnFocus Statement, OnOccChange Statement, PostProc Statement, Order of Executing Data Entry Events, Order of Executing Batch Edit Events