@# /*@ strfix -d /u/sw/s/buildlib/infodict.D @F | hoff
@# /*@ strfix -d @INFODICT @F | hoff
@#	SID	%W% - %E%
---------------------------------------------------------------------
.br
.ti 15
Changes to the Application Environment
.ti 17
and Upgrading an Old Application
.ti 32
@REVISION@
.br
---------------------------------------------------------------------
.sp
Changes since Version 2.20.
.TP 3
1)
The manner in which user activity logs and working
directories has been changed.
.sp
.in 5
.ti 3
- All user activity logs are stored in the sub
directory, system/log.
If you are upgrading an
application from 2.20 or earlier, you must make this directory.
.in 5
.ti 3
- Working directories ($$workdir) are still in the
system/users directory, however, an extension is used.
This allows a user to be logged into the application
twice using the same User ID.
The first process/user
that starts the application, uses the directory with an
extension of 0, the 2nd uses an extension of 1 and so on.
If you are using an application that involves
external procedures, or frequent module changes, it is
recommended that unique user id's be used.
.TP 3
2)
The IMPORT command in the User Activity Log allows you to
specify a path, thus allowing you to import the
activity log from one system, into another.
.TP 3
3)
The CLEAN_UP command available at the User Data base will
delete all files in the working directories.
.TP 3
4)
The Change Application action (CHAP) requires that the
object contain the path and file name of the start up
script of the destination application.
Previous versions required the home directory of the destination
application.
.TP 3
5)
The Developer's System access, (via the Ctrl-A) is faster.
.TP 3
6)
Various spelling mistakes, and bugs have been corrected.
.TP 3
7)
In DOS, the start up batch file can no longer validate the user ID.
(This is done once the data base module is active).
If you are upgrading an application created
on version 2.20 or earlier, delete the lines that check
for the .PSD file; for example, the following line
should be removed:
.sp
.ti +4
.nf
"if not exist %ANGIIAPL%\system\users\%1\%1.psd goto baduser"
.fi
.TP 3
8)
In DOS, the start up command of the underlying office automation
software has changed.
In previous versions, typically
the command "SMART2" was used.
In 2.30, the command is
either "ANGOSS" or "ANGOSSP".
In 2.50, the command is
either "ANGOSS" or "ANGOSSX".
In 4.00, the command is
either "smart" or "smartx".
You should edit the
start up batch file to reflect this difference.
Alternatively, the environment variable SMTCMD can be
used to specify the office automation start up command.
.sp
.in 0
2.20 Features
.sp
If you have been using an SmartWare version of 2.11 or earlier,
the following features are new:
.TP 3
1)
New Report Features
.sp
Report printing from the data base has been dramatically
improved.
You can now associate a query definition, sort
definition, key, input-screen and program with a report.
Reports can also be included in job streams.
.TP 3
2)
Documentation Generation
.sp
There are a variety of new features and improvements in the
documentation generation module.
Briefly, they are:
.sp
.in +2
.ti -2
- Choice between Cascading or Box Style Menus
.ti -2
- Ability to specify which sample reports to include
.ti -2
- Ability to include listing of all data files
.ti -2
- Ability to print view & data file layouts in condensed format
.ti -2
- New Font handling
.ti -2
- Improved pagination control
.TP 3
3)
Calculate Totals
.sp
The Totals action has been improved.
The new features are:
.sp
.in +2
.ti -2
- Up to 14 calculations
.ti -2
- Ability to specify format
.ti -2
- Link in help file when displaying results
.ti -2
- Print Option
.TP 3
4)
Automatic Case Conversion for Key Fields
.sp
The FIND and ORDER commands now can automatically change the
User's Input to upper case, lower case, proper case or use
up to 10 predefined input masks.
.TP 3
5)
User Utilities
.sp
The User Utilities Query, Custom Report, Send to
Spreadsheet, Mail Merge, Sort and Macro have all been
enhanced.
The new features available are:
.sp
.in +2
.ti -2
- Cleaner user interface
.ti -2
- New "This_View" command to isolate all definitions
for the current view
.ti -2
- Last modification and used dates for each definition
.TP 3
6)
Browse Fields
.sp
A new Developer command allows users to use a field prompter
to select the browse fields.
It is obtained by ^A Modify
when at a data view.
.in 0
.sp
Upgrading SmartWare 2.11 to SmartWare 2.3 or 2.4
.sp
If you are upgrading an SmartWare application that was running
on version 2.11, you must follow these steps.
If you are
converting an application from a version older than version
2.11 then call SmartWare Software services for details.
.TP 3
1.
Uninstall SmartWare 2.11 and Install the latest version
.br
.ti +10
-- or --
.br
Install the latest version into a different directory
.TP 3
2.
Backup all applications that are to be converted
.TP 3
3.
Repeat the following for each application to be
converted:
.sp
.in +3
.ti -3
A. Configure Start Up batch file and SMART.CFG to
reference the proper SmartWare directories.
Also, in the start up batch file, change the office
automation startup command and delete the line:
.sp
.ti +4
\if not exist %ANGIIAPL%\system\users\%1\%1.psd goto baduser
.fi
.ti -3
.sp
B. Make the system log directory.
For example:
.sp
.ti +4
.nf
@{ @HOSTSYS:UNIX@
@| DOS
md \myapp\system\log
@| UNIX
mkdir myapp/system/log
@}
.fi
.sp
.ti -3
C. Start the Application to be converted
.sp
.ti -3
D. Press Control V to insure that SmartWare is running
.sp
.ti -3
E. Press
.sp
.in +3
.nf
CONTROL A
Utilities
Remember
Execute
SysDir\CONVERT.RF3
.sp
.in -3
.fi
where, SysDir is the directory path
in which the SmartWare Developer System is installed
(i.e.: C:\ANGIIDEV).
.sp
.ti -3
F. Exit the Application - Conversion is complete
.in 0
.sp
.fi