Professional Documents
Culture Documents
Readme
Readme
0 for Windows
Installation
New features. For a list of new features in the latest SPSS for Windows
release, please visit
http://www.spss.com/spss/whats_new.htm
For a list of new features in SPSS, see the What's New in SPSS 16.0?
topic in the online help or the cover letter that was included with your
system.
Saving Stata and SAS files with multi-byte variable names. When saving
data files in Stata or SAS format, SPSS variable names that contain
multi-byte characters (e.g., Japanese or Chinese characters) are
converted to variables names of the general form Vnnn, where nnn is an
integer value. an integer value.
Dimensions DMOM Libraries. This version of SPSS will not work with
Dimensions DMOM Libraries Version 3.5.0.1 or lower. Please use the
Dimensions Component Pack Version 4.0(included with the SPSS install) or
use a DMOM Version 4.0 or higher product.
SPSS doesn’t work with Altiris Vision User Module 3.1. There is a memory
conflict with Microsoft DirectDraw and SPSS when Altiris Vision is
installed using the "Run before logon" option. In order to resolve this
problem you must not install Altiris Vision with this option - use "Add
to startup menu" or "Run manually" instead. You must uninstall and re-
install Altiris Vision if you already have an installation using "Run
before logon" and are experiencing problems.
Known Problems
Graphics
* Reading OLE DB and Dimensions data sources. OLE DB and Dimensions data
sources are only available on Windows 2000 and Windows XP. You cannot
install the Dimensions Data Model and OLE DB Data Access on non-
supported platforms. OLE DB data sources are not available in the
Database Wizard, Read Dimension Data (on the File menu) is not
available, and GET DATA TYPE=OLEDB will generate an error on non-
supported operating systems.
* Reading Oracle OLE DB Data Sources. When using GET DATA /TYPE=OLEDB
to read Oracle data sources, SQL statements should not include owner
information. For example: SELECT * FROM "ownername"."tablename" will
only read the field names and will not include any data. To read the
table correctly, omit the owner information, as in: SELECT * FROM
"tablename" .
* SPSS Connect ODBC drivers for SQL Server. The SPSS Connect ODBC driver
to use depends on the version of SQL Server at your site. Use the SPSS
OEM 5.0 SQL Server Wire Protocol driver for SQL Server versions 7.x and
2000. Note that you can use the Microsoft SQL Server driver for SQL
Server versions 6.x and higher.
* The SPSS OEM 5.2 DB2 Wire Protocol ODBC driver provided in the SPSS
Data Access Pack is not compatible with DB2 9.1. When updated drivers
are available, you can download them from
http://www.spss.com/drivers/clientSPSS.htm.
* Oracle and SequeLink Server. If you are using the SequeLink Server at
your site, it might not work correctly with Oracle 8. Use Connect ODBC
instead. Connect ODBC is included in the SPSS Data Access Pack.
* Using data files saved in SAS formats in SAS JMP and the SAS Viewer.
Data files saved in various SAS formats from SPSS should work in SAS.
There are known problems using SAS files saved in SPSS with the SAS
Viewer and SAS JMP 5 - these applications have a different mechanism for
reading files which isn’t the same or as stable as the one used in SAS.
* SAS formats and string length limitations. If you use SPSS to open SAS
data file types, you may not be able to get string values longer than
255 bytes. If your data contain values longer than 255 bytes, SPSS will
get only the first 255 bytes.
* Text Wizard data caching. The Text Wizard provides an optional setting
that automatically caches the data that it imports. By default caching
is on and the wizard creates a copy of the entire dataset. If you turn
caching off, SPSS does not have access to the entire data file -- the
original data source is re-read as needed -- and the total number of
cases is unknown. When the total number of cases is unknown, Go to Case,
Copy, and Paste do not work as expected in the Data Editor. You can
correct the problem by using the File menu to Cache Data.
* Using syntax to read data with ODBC. If you use syntax to read data
from a database with ODBC, we recommend caching your data. Caching your
data ensures that the data are in the same order each time that SPSS
needs to make a data pass. It also ensures that your analysis isn't
affected by updates to the database that occur while the syntax is being
processed. To cache the data, add a CACHE command to the syntax
immediately after your GET DATA command.
* SQL Server ODBC Driver. If you are using the SPSS OEM 5.2 SQL Server
Wire Protocol, you should modify the driver setup to ensure proper
handling of quoted field and table names in SQL statements generated by
the Database Wizard and Export to Database Wizard or specified in the
GET DATA and SAVE TRANSLATE commands. In the Advanced tab of the driver
setup, select (check) "Enable Quoted Identifiers". In local analysis
mode, you can modify the driver setup using the Windows ODBC Data Source
Administrator, which you can access from within SPSS via the "Add ODBC
data source" button in the Database Wizard or Export to Database Wizard.
For database access in distributed analysis mode (using SPSS Server),
contact your database administrator.
Procedures
* Linear Mixed Models. In the Random dialog box if the Include Intercept
checkbox is checked but no factors or covariates are specified as random
effects, the Next button will not become available. Therefore, in order
to generate a RANDOM subcommand with no effect(s) other than an
intercept, that subcommand must be the last one specified in the Random
dialog box. If there are multiple subcommands specified, the last of
which contains only the intercept, that specification will not be
generated unless Continue is clicked while remaining at that last
specification, unless that specification also includes a subject
combination
Other
* Customers who have licensed the PES Adaptor and are upgrading from
SPSS 14 may have problems storing and retrieving Complex Samples plan
files. If problems occur you should redefine MIME-type mappings for
Complex Samples plan files. Open the Predictive Enterprise Administrator
(http://<pes server>/config/mimeManager) and delete any existing
definitions for .csplan and .csaplan files. Then redefine the mappings
for the two file types using a single dash (-) instead of a double dash
(--) in the MIME type definition.
The temporary folder location specified on the File Locations tab of the
Options dialog does not change the location of temporary data files
created by SPSS in SPSS 16.0. The location of temporary data files can
be controlled by an environment variable setting specified by the
operating system.
SPSSTMPDIR
SPSSTEMPDIR
TMPDIR
TEMP
* Syntax files can be saved in Unicode or in the local code page (local
encoding). In most cases, when you open a file in the syntax window,
SPSS automatically determines the correct encoding. Sometimes it will
be wrong. If you see three funny characters at the start of the file,
close it and reopen specifying Unicode. If the contents look scrambled,
try a different encoding setting. If it still looks wrong, your SPSS
locale may be different from the way the file was saved. Use an
appropriate SET LOCALE command to resolve this.
* If you use the Browse button in the Menu Editor to select a syntax or
script file for a custom menu item, the value displayed in the Filename
field will be enclosed in quotes. You should remove these quotes,
otherwise the file will not be found when you use the custom menu item.
For syntax files, this problem manifests as an alert of the general form
"Cannot start ['filename']." For script files, you will see this message
in the Viewer window: "No language is configured to execute this script.
Cannot run the script."
* Citrix and Sax BASIC error. When you run SPSS as a published Citrix
application, you may encounter a Sax BASIC error when you attempt to run
a procedure. The problem can be corrected by editing the location of the
global procedures file on the SPSS Options Scripts tab.
Resources
Legal Notices
Portions of the Software are licensed under the Apache License, Version
2.0 (the ""License""); you may not use applicable files except in
compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Portions of the Software have been licensed under the Apache License,
Version 2.0 (the ""License""). You may not use those relevant files
except in compliance with the License. You may obtain a copy of the
License at:http://www.apache.org/licenses/LICENSE-2.0. Unless required
by applicable law or agreed to in writing, software distributed under
the License is distributed on an ""AS IS"" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for
the specific language governing permissions and limitations under the
License
The contents of this file are subject to the IBM Public License v. 1.0
(the ""License""); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.opensource.org/licenses/ibmpl.php Software distributed under
the License is distributed on an ""AS IS"" basis, WITHOUT WARRANTY OF
ANY KIND, either express or implied. See the License for the Specific
Language governing rights and limitations under the License.
Portions of this software are 3rd party code, WSDL4J 1.4 that licensed
under Common Public License 1.0 and the source code for this 3rd party
code is available : http://sourceforge.net/projects/wsdl4j
The contents of this file are subject to the Mozilla Public License
Version 1.1 (the ""License""); you may not use this file except in
compliance with the License. You may obtain a copy of the License at
http://www.mozxilla.org/MPL/. Software distributed under the License is
distributed on an ""AS IS"" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the License for the Specific Language governing
rights and limitations under the License.",
2. Redistributions in
binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.
4. Products derived from this Software may not be called ""Castor"" nor
may
""Castor"" appear in their names without prior written permission
of Intalio Inc. Exolab, Castor and Intalio are trademarks of
Intalio Inc.
Portions of the Software are licensed under the Apache License, Version
2.0 (the ""License""); you may not use applicable files except in
compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Permission to use, copy, modify, and distribute this software for any
purpose
with or without fee is hereby granted, provided that the above copyright
notice and this permission notice appear in all copies.
* Neither the name of the NumPy Developers nor the names of any
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
This product includes ZSI 2.0 software licensed under the following
terms.