1 - 25 of 58 results
Previous   |    1 , 2, 3   |    Next >
Sort by:
Date | Relevance

2011-12-08

44875 - "ERROR: THE NUMERIC VARIABLE MYVAR MAY NOT BE CONTINUED" might appear in FSEDIT if a numeric field is continued to more than one line- Usage Note

When opening a table into FSEDIT, you might receive the following error if your table contains a numeric field that is continued to the next line because the formatted value is too long to display on the same line. ...

http://support.sas.com/kb/44/875.html, 27KB

2008-01-18

22070 - How to display a custom error message in the FSEDIT window when a field is in error- Usage Note

If you have an FSEDIT SCL program that places variables in error and generates a custom error message, you should see this custom error message after you enter incorrect values in more than one field and press ENTER. ...

http://support.sas.com/kb/22/070.html, 25KB

2008-01-18

22078 - How to perform initial processing in the FSVIEW window- Usage Note

To perform initial processing in the FSVIEW window, your FORMULA entry must contain a computed variable. For example, suppose you want to suppress the note that appears on the message line in the display window ...

http://support.sas.com/kb/22/078.html, 26KB

2008-01-18

22067 - Cannot tab to or view data in some fields within the FSEDIT window- Usage Note

It sounds like these fields are no longer defined to your custom FSEDIT screen. First, check that the variables are still in your data set. Then invoke FSEDIT and go into screen modification mode by issuing the MODIFY ...

http://support.sas.com/kb/22/067.html, 26KB

2008-01-18

22071 - How to access the FSEDIT Menu window when SCL logic removes all procedure-specific commands from the command line- Usage Note

If you accidentally add SCL logic to your FSEDIT screen that removes all procedure-specific commands from the command line, you might find that you cannot get back to the SCL program via the MODIFY command. If this ...

http://support.sas.com/kb/22/071.html, 25KB

2007-11-20

22079 - Unable to edit observations in the FSVIEW window when the data set is open in edit mode- Usage Note

By default, when the FSVIEW window is opened for editing, the procedure selects a control level of RECORD. To edit an observation with RECORD level control, you must first lock an observation for editing before you can ...

http://support.sas.com/kb/22/079.html, 25KB

2007-11-20

22068 - How to move the cursor down a column instead of across a row when pressing ENTER in SAS/FSP® software- Usage Note

To move the cursor down a column instead of across a row when pressing ENTER in SAS/FSP software, specify the VTAB option in either the SETCR command or the SETCR function in SAS Component Language.

http://support.sas.com/kb/22/068.html, 25KB

2007-11-20

22065 - How to add a new variable to the data set and a custom FSEDIT screen- Usage Note

The variable must first be added to the data set outside of the FSEDIT procedure. You can use the LENGTH statement in a DATA step to add the variable. Then reinvoke the FSEDIT procedure specifying your custom screen. Go ...

http://support.sas.com/kb/22/065.html, 26KB

2007-06-14

795 - Your custom pmenu might not be displayed if SASHELP contains pmenu of the same name- Usage Note

If the name of the custom pmenu you attempt to associate with an FSP or AF window is the same as the name of a PMENU entry in the SASHELP.FSP or SASHELP.CORE catalog, then SAS might use the PMENU entry from the catalog ...

http://support.sas.com/kb/00/795.html, 26KB

2007-06-05

20337 - Messages not visible in the FSEDIT Identify window within the Microsoft Windows environment- Usage Note

If you are in the FSEDIT Identify window and you cannot see the following prompt to associate a variable to a field, Please put cursor on field: fieldName and press ENTER .. or UNWANTED this is, most likely, because ...

http://support.sas.com/kb/20/337.html, 26KB

2007-06-05

20140 - Interactive procedures which set the SYSERR automatic macro variable- Usage Note

The following interactive procedures set the SYSERR automatic macro variable: SAS/AF software PROC BUILD SAS/FSP software PROC FSBROWSE PROC FSEDIT PROC FSLETTER PROC FSVIEW Base SAS software PROC ...

http://support.sas.com/kb/20/140.html, 26KB

2007-02-15

9118 - Information needed to remove password from FSEDIT screen- Usage Note

While we cannot tell you how to remove a password from an FSEDIT screen over the phone, we will tell the Site Representative what the password is if they send the screen in to us. There are certain requirements before ...

http://support.sas.com/kb/9/118.html, 27KB

2006-07-06

10253 - Terminal might beep when INSERT is turned on and you try to enter a value- Usage Note

Within an FSEDIT window in SAS/FSP Software, you are not allowed to enter data in a field when INSERT mode is turned on unless you have deleted any existing characters or blanks in the field. This could cause your ...

http://support.sas.com/kb/10/253.html, 27KB

2006-05-12

17664 - SAS code following DM statement that opens VIEWTABLE, FSEDIT, or FSVIEW executes before window closes- Usage Note

The DM statement is only designed to stop when it invokes a SAS/AF window. If you use it to invoke the VIEWTABLE, FSEDIT, or FSVIEW windows, then it continues on to the statements that follow. To allow code following ...

http://support.sas.com/kb/17/664.html, 27KB

2006-01-13

16783 - How to run an FSEDIT application on a Microsoft Windows server platform- Usage Note

To run an interactive FSEDIT application or any other interactive procedure from SAS/FSP software on a Microsoft Windows server platform, you will need the following: 1. SAS/FSP software installed on the server. 2 ...

http://support.sas.com/kb/16/783.html, 25KB

2005-11-11

302 - Information on when SAS/FSP Software is needed- Usage Note

SAS/FSP Software is required to run the SAS/FSP procedures FSEDIT, FSBROWSE, FSVIEW and FSLETTER. The FSLIST procedure is now part of Base SAS Software so it does not require a license for SAS/FSP. Within SAS/ASSIST ...

http://support.sas.com/kb/00/302.html, 26KB

2005-05-17

15146 - OK and CANCEL buttons may not display in Screen Print window- Usage Note

Within the FSEDIT and FSVIEW procedures of SAS/FSP Software, the OK and CANCEL buttons may not display in the Screen Print window when pmenus have been turned off for all windows. With pmenus turned off, a command line ...

http://support.sas.com/kb/15/146.html, 27KB

2005-01-18

14154 - Value may not be found if variable name specified for search value on FIND command- Usage Note

Within the FSEDIT or FSBROWSE windows in SAS/FSP Software, no values may be found if you specify the name of a variable for the search value on the FIND command. The search value must be a literal value and not the name ...

http://support.sas.com/kb/14/154.html, 27KB

2004-07-16

12857 - FSEDIT does not apply informats or formats to continued fields- Usage Note

FSEDIT does not apply informats or formats to values displayed in continued fields. To allow the formatted value to display in a continued field, you can use the PUT function in a SAS Component Language program such as ...

http://support.sas.com/kb/12/857.html, 26KB

2003-12-19

7851 - Performance will be slower if you perform a cancel after an add in PROC FSEDIT on an access view- Usage Note

In SAS Version 6, if you perform an ADD followed by a CANCEL on an access view within PROC FSEDIT, you are taken to the first observation. In Version 8, the same steps take you to the last observation. This process ...

http://support.sas.com/kb/7/851.html, 27KB

2003-07-07

10355 - How to get more blank fields for entering variable names in FSEDIT New window- Usage Note

The FSEDIT New window gives you room to enter 15 new variables at a time. When you have filled in all 15, you will receive 15 more if you move the thumb on the vertical scrollbar at the right of the window or if you ...

http://support.sas.com/kb/10/355.html, 26KB

2003-07-07

10362 - Width of ID variables in the FSVIEW window cannot exceed 53 characters- Usage Note

The publication, SAS/FSP Software, Usage and Reference, Version 6, First Edition, incorrectly documents on page 390 that the combined width for all ID variables cannot exceed 60 columns. It also incorrectly documents ...

http://support.sas.com/kb/10/362.html, 27KB

2003-07-07

10343 - Focus may go to tool bar if leave FSEDIT to display another window and then return- Usage Note

Within the FSEDIT window of SAS/FSP Software, if you are using ReflectionsX as your X window emulator and the default local window manager is set as Microsoft Manager, you may find that focus is sent to the tool bar ...

http://support.sas.com/kb/10/343.html, 25KB

2003-05-08

9919 - ERROR: Program names and symbols do not match- Usage Note

If you have deleted or changed the type of a variable that is referenced in your FSEDIT SCL program, you may receive the following error when you reinvoke your FSEDIT session: ERROR: Program names and symbols do not ...

http://support.sas.com/kb/9/919.html, 27KB

2003-05-06

9480 - Japanese text in multiline fields may display incorrectly- Usage Note

Within the FSEDIT or FSBROWSE procedures of SAS/FSP Software, character variables that display Japanese (or other MBCS) text across multiple lines may display text incorrectly. The last character on the first line may ...

http://support.sas.com/kb/9/480.html, 27KB

1 - 25 of 58 results
Previous   |    1 , 2, 3   |    Next >