This document discusses a C++ sample program called Dictls32.exe that uses the File I/O API to display dictionary information from SPSS data files. It is a multiple document interface (MDI) application that opens SPSS data files and displays their dictionary information in child windows. The document provides instructions on building and running the sample program using Visual C++ and lists the constituent source code files that make up the program.

1. File I/O API - C++ Sample Program
04 Feb 03
Overview
Dictls32.exe is a C++ sample program which utilizes the File I/O API. It is a multiple
document interface (MDI) application which displays the dictionary information from SPSS data
files in one or more child windows. The user simply selects “Open” from the “File” menu to get a
standard Open File dialog. If the selected file is an SPSS data file, its dictionary information is
displayed in an edit control in a child window. The application is terminated by selecting “Exit”
from the “File” menu.
Building
The sample program has been built with version 6.0 of Microsoft Visual C++. Other compilers
may work, but they have not been tested. In order to build the sample program, perform the
following steps:
1. Copy all the files from the SPSSDeveloperio_dllsmpl_cpp directory on the
distribution disk to a directory on your hard disk.
2. Make sure spssdio.h is on the compiler’s search path - either by copying it to the directory
containing the sample program or by modifying the INCLUDE environment variable.
3. Made sure spssio32.lib is on the linker’s search path - either by copying the file to the
directory containing the sample program or by modifying the LIB environment variable.
4. Use the nmake utility to build the application:
nmake -f dictls32.mak DEBUG=1
Each of the makefiles recognizes two options which can either be set as environment variables or
defined on the command line. The first option is “DEBUG”. If this symbol is defined (regardless
of its value), the resulting executable will contain debug symbols. The default is not to include
debug symbols. The second option is “STATICMFC ”. If this symbol is defined (regardless of its
value), the resulting executable will contain statically-linked Microsoft Foundation Classes (MFC)
and C Run-Time. The default is to use DLL-resident versions of MFC and the C Run-Time.
The makefile writes its intermediate and target files to a subdirectory named “32”. In order to
execute the resulting application, spssio32.dll must be accessible at execution time.
Integrated Development Environment
Most users will opt to use Microsoft’s Integrated Development Environment (IDE) to build and
debug an application. The sample application is amenable to being built in this fashion. Simply
open dictls32.mak by selecting “Open Workspace” from the “File” menu. You will have to
select “Settings” on the “Build” menu to specify the name of the target file, the name of the
required DLL, and the debug build command line.

2. File I/O API - C++ Sample Program
04 Feb 03
Constituent Files
The following files are included as part of the sample program:
dictafx.cpp
dictafx.h
dictdoc.cpp
dictdoc.h
dictdoc.ico
dictlist.cpp
dictlist.h
dictls32.mak
dictls32.rc
dictmain.ico
dict-res.h
for building precompiled headers
includes the headers to be precompiled
CDocument class CDictListDoc - does all the work
Interface to class CDictListDoc
Icon for class CDictListDoc
CEditView class CDictListEditView and a CWinApp class
Interface to classes CDictListEditView and CDictListApp
External makefile
Resources
Icon for the application’s MDI frame window
Interface to the resources
-2-