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


50025 - Transporting an FSVIEW formula corrupts the catalog- Problem Note

When you transport a catalog that contains an FSVIEW formula using PROC CPORT and then attempt to use that formula after importing, the formula becomes corrupted. After you import using PROC CIMPORT and attempt to use ...

http://support.sas.com/kb/50/025.html, 24KB


47226 - SAS® might stop working when scrolling the FSVIEW window on a dual-monitor system- Problem Note

SAS 9.3 might stop working when you are scrolling through the data in an FSVIEW window. This problem has been observed on Windows systems with multiple monitors. This problem happens less frequently when you do not ...

http://support.sas.com/kb/47/226.html, 22KB


41515 - Your SAS session might become unresponsive when the FSVIEW window is stretched across multiple monitors- Problem Note

If you are using a dual-monitor desktop configuration and you stretch your FSVIEW window across both monitors, then your SAS session might become unresponsive. Once you encounter this problem, your SASUSER.PROFILE ...

http://support.sas.com/kb/41/515.html, 22KB


39696 - Access Violation or format error received when accessing a SAS® 8.2 formula catalog in SAS® 9.2- Problem Note

If you attempt to load an FSVIEW formula catalog created in SAS 8.2 into SAS 9.2, you could receive one or both of the following errors: ERROR: Read Access Violation in Task [ FSVIEW ] Exception occured at (6699001E) ...

http://support.sas.com/kb/39/696.html, 23KB


39006 - NAME/LOCATE search sequence in FSEDIT causes Read Access Violation on long column- Problem Note

When attempting to use the NAME and LOCATE search sequence in FSEDIT on a column with a length greater than 200 characters, the FSEDIT window might close down with the following error written to the SAS log. ERROR: ...

http://support.sas.com/kb/39/006.html, 22KB


18155 - Unable to mark text in a field in the FSEDIT window- Problem Note

If you mark text in a field displayed in the FSEDIT window and then issue the STORE command so that you can copy and paste the text into another field, you might receive the following error after issuing the STORE ...

http://support.sas.com/kb/18/155.html, 22KB


20731 - Abend reading a FORMULA entry in a catalog defined to a SAS/SHARE® server- Problem Note

You might receive one of the following errors in the SAS® Log when you attempt to display a table in the FSVIEW window with a FORMULA entry that is stored in a catalog which is allocated through a SAS/SHARE® server: ...

http://support.sas.com/kb/20/731.html, 23KB


14026 - Generic critical error when resizing the FSVIEW window in X Window System environment- Problem Note

If you are using the FSVIEW window in the X Window System environment to display the contents of a data set with more than 1000 observations, you may experience a generic critical error after resizing and scrolling the ...

http://support.sas.com/kb/14/026.html, 22KB


10748 - Underscores or pad character may remain as part of value- Problem Note

Within the FSEDIT window of SAS/FSP software, if you zoom or unzoom either the FSEDIT window or the SAS window and then type text into a field that is displaying its underscores (default pad character) to indicate a ...

http://support.sas.com/kb/10/748.html, 23KB


9294 - Long character value might not be visible in the FSVIEW window- Problem Note

If you have installed hot fix 82BB16 for Base SAS Software or the hot fix bundle 82BX04 and you use the FSVIEW window to view a variable whose value cannot be fully displayed, such as a character variable with a length ...

http://support.sas.com/kb/9/294.html, 23KB


8166 - Abend in FSVIEW when saving a data set with integrity constraint- Problem Note

If you attempt to create a new data set in the FSVIEW window via the CREATE command or the File -> Save as pmenu selection, you may experience an abend if the data set currently displayed in the FSVIEW window was opened ...

http://support.sas.com/kb/8/166.html, 22KB


6147 - Potential security exposure with SAS/FSP- Problem Note

We have identified a potential for the integrity of password protected data sets to be compromised when accessed via some of our SAS/FSP procedures. As soon as this issue was identified, a fix was created for SAS ...

http://support.sas.com/kb/6/147.html, 22KB


5834 - Cursor may not be visible in FSEDIT window until ENTER is pressed on Japanese versions of the operating system- Problem Note

If you run SAS on a Japanese version of a Microsoft Windows operating system, the cursor may not be visible within the FSEDIT window until ENTER or TAB is pressed. One circumvention for the problem is to specify a ...

http://support.sas.com/kb/5/834.html, 26KB


2560 - Warning: End of file on entry xxx.screen- Problem Note

If an FSEDIT screen has no variables defined to it, you will receive the following warning when you attempt to invoke it and the screen will not display: Warning: End of file on entry your.screen. Having no ...

http://support.sas.com/kb/2/560.html, 21KB


38804 - Linguistic sorting is not available for the FSVIEW window- Problem Note

The ability to perform linguistic sorting is not available within the FSVIEW window. If you have specified the SAS system option SORTSEQ=LINQUISTIC, and then attempt to sort a data set within the FSVIEW window, the ...

http://support.sas.com/kb/38/804.html, 21KB


35154 - "INTERNAL CODING ERROR..." in FSEDIT when scrolling through data accessed with the XML LIBNAME engine- Problem Note

Some SAS® applications, including FSEDIT applications, require data to be accessed via a random access method. However, the XML LIBNAME engine allows only sequential read data access. Therefore, in FSEDIT, if you ...

http://support.sas.com/kb/35/154.html, 23KB


33 - Data values in an SQL view might not display correctly- Problem Note

Data values from a PROC SQL view of a DBMS table accessed through the DBMS engine on a LIBNAME statement might be displayed incorrectly by the FSVIEW procedure. Although the data may display incorrectly, the actual ...

http://support.sas.com/kb/00/33.html, 20KB


19606 - SAS time value with NLTIMAP informat returns missing value in FSEDIT and FSVIEW windows- Problem Note

If you modify a value of a column that has the NLTIMAP informat in the FSEDIT or FSVIEW window, the column might be assigned a missing value. You will see this with any time value you enter in a row that is either new ...

http://support.sas.com/kb/19/606.html, 22KB


19546 - Might receive error if invoke FSEDIT with FSEDIT command and then zoom the window- Problem Note

On Unix platforms, you might receive the following error if you invoke the FSEDIT procedure with the FSEDIT command and then zoom the FSEDIT window: Segmentation Violation In Task [ FSEdit W ] Fault Occurred at [/ ...

http://support.sas.com/kb/19/546.html, 21KB


19053 - Print Utilities selection missing from File menu in FSBROWSE, FSEDIT, and FSVIEW windows- Problem Note

On the mainframe and in the UNIX environments, the Print Utilities selection from the File menu is missing in the FSBROWSE, FSEDIT, and FSVIEW windows. This menu selection enables you to do a screen print. To ...

http://support.sas.com/kb/19/053.html, 20KB


14158 - Help window may not display for FSEDIT, FSVIEW, or FSLIST procedures- Problem Note

Within the FSEDIT, FSBROWSE, or FSVIEW windows in SAS/FSP Software or the FSLIST window in Base SAS Software, help information may not display if you issue the HELP command or select Help, Using This Window from the ...

http://support.sas.com/kb/14/158.html, 22KB


17339 - Error creating computed column in FSVIEW when name contains underscore- Problem Note

The following error message may be written to the SAS Log when you define and rename a computed column with a name that contains an underscore such as COMP_VAR in the FSVIEW window: ERROR: [Line 2] Multiple label ...

http://support.sas.com/kb/17/339.html, 22KB


16883 - May receive Internal Coding Error if you attempt to scroll past end of file within FSBROWSE- Problem Note

Within the FSBROWSE window in SAS/FSP Software, if you browse a data set that uses a sequential engine such as TAPE or XML, you may erroneously receive an internal coding error in the SAS Log window if you issue a ...

http://support.sas.com/kb/16/883.html, 22KB


16316 - Window size might be limited for new fullscreen window invoked with SYSIN option- Problem Note

If you invoke SAS with the SYSIN system option or by specifying the name of a file on the SAS command (ie. SAS FILENAME) and display a new fullscreen window such as the FSEDIT or FSVIEW window or a SAS/AF FRAME entry, ...

http://support.sas.com/kb/16/316.html, 21KB


16057 - On the mainframe, SAS might hang with VAR command issued from fullscreen window- Problem Note

If you have invoked SAS on the mainframe with the V6GUIMODE system option specified, your SAS session might hang if you invoke a fullscreen procedure such as FSEDIT, FSVIEW, or BUILD with a PROC statement and then issue ...

http://support.sas.com/kb/16/057.html, 20KB

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