Saving and Storing Frame SCL Programs

There are several important items to remember when you are saving SCL programs for FRAME entries:

• If an SCL entry that is associated with a frame is saved from the Source window, then both the FRAME entry and the SCL entry are saved.

• Although you can compile an SCL program independently of its FRAME entry, the compiled code is stored with the FRAME entry only if you compile the SCL source either through the Source window or through the Build window that contains the FRAME entry. Compiling the FRAME entry always compiles the associated SCL entry.

• The SCL program is automatically compiled and saved when you save the FRAME entry if you set the frame's automaticCompile attribute to Yes.

• When you compile a FRAME entry, the FRAME entry's SCL source is compiled, and the compiled code is stored in the FRAME entry. Since the compiled SCL program is stored in the FRAME entry, the SCL entry that contains the source statements does not have to exist when you install and run the application.

• If you change the name of a frame that has an associated SCL entry, you must also remember to either

  • change the name of the SCL entry to match the FRAME entry if it is not *.SCL, and then recompile the frame; or

  • edit the frame's SCLEntry attribute to use the existing frame SCL entry.

Copyright © 2007 by SAS Institute Inc., Cary, NC, USA. All rights reserved.