Checking Converted FoxPro 2.6 Screens

See Also

After you convert a FoxPro 2.6 screen (.scx) file, you should check for the following conditions:

• READ statements with both a MODAL and DEACTIVATE clause. Visual FoxPro processes both these clauses.
  
  
• Conflicting control, object, form, and variable names.
  
  
• Long variable names that have more than ten common characters.

  For more information, see Creating Visual FoxPro Names or Reserved Words.

• Controls under shapes. In FoxPro 2.6, the positions of shapes has no effect on other controls. In converted FoxPro 2.6 screens, shapes are behind all other controls and invisible buttons are always on top of all other controls.
  
  
• UDFs and other code that might be superseded by new Visual FoxPro commands or functions. For more information, see Checking Code After Conversion.
  
  
• Macro substitutions. Replace macro substitutions in the Properties window with variable assignments. For example, a PushButton prompt in FoxPro 2.6 Screen Builder that contains &lcprompt is converted to ="&lcprompt" and must be changed to =lcprompt.

Visual FoxPro runs converted screens from the .spr file created during conversion. Check this .spr file and the code in any programs or other screens that might call the converted screen to determine whether you can eliminate the new .spr file and run directly from the .scx file. For more information, see Checking the .SPR File and Changing Converted Screens to Visual FoxPro Forms. To understand how Visual FoxPro supports converted screens in READ compatibility mode, see Overview of READ Compatibility Architecture.