Consultor Eletrônico

V7 & V8 16-bit Client Packaging
PC Platforms

PRODUCT | DB | COMPILE | LOAD | V7 User
| Conn | | df d | Intreface*
==============+======+=========+========+=============
ProVision | L/R | Y | Y Y | GUI and CHAR
4GL | L/R | Y | Y Y | GUI or CHAR
Personal DB | L | -rx |-rx N | GUI or CHAR
Cl. Networking| R | -rx |-rx N | GUI or CHAR
Query/RESULTS | (2) | (3) |-rx N | GUI or CHAR
Report Builder| (2) | (4) |N/A N/A| GUI only

L Local
R Remote
(1) Must be combined with a development or deployment license for
connectivity
(2) Must purchase Client Networking or Personal DB for connectivity
(3) Only procedures that don't update DB
(4) Can compile RB reports
-rx Compiles only encrypted code with -rx startup parameter or loads
df with -rx startup parameter
LIC The answer depends on the license it's combined with. Yes, if
combined with a development license No, if combined with a
deployment license
* V8.0 and v8.1 did not include a character mode executable.
Version 8.2 re-introduced character mode for PC platforms. That
is a 32-bit release and packaging for it is discussed in the 8.2
Client Packaging document. See the "Notes on Character vs. Gui
mode" section below for more details about this.

Notes on DB Connections
=======================
Local means connecting to a database in single-user mode. This type
of license is sometimes referred to as stand-alone.

Remote means connecting to a database that has had a server started in
multi-user mode.

Results and Report Builder can be purchased as separate licenses, but
they are also included in the Provision package. When they're part of
ProVision, they can make either local or remote connections to a
database.
When purchased as separate licenses, they must be purchased and
installed with a deployment license (either Client Networking or
Personal DB) in order to be able to connect to a database. If a
customer wants a Query/Results license to be able to access both local
and remote data, they would need three components: Query/Results,
Client Networking and Personal Database. The same is true for Report
Builder.

WIPC: Development licenses come with the ability to start a local
server (using the executable wproserv.exe) which will allow multiple
local sessions to connect to a database. The protocol for these
connections is WIPC. Only sessions running on the PC where
wproserv.exe is running can connect to the DB. The idea behind this
is to give developers the ability to test multi-user applications on a
stand-alone PC. (This is sometimes referred to as "beach"
development-- a developer can take her laptop to the beach and still
write/test a multi-user application.) There is information on
wproserve.exe in the System Administration Guide.


Notes on Compiling Issues
=========================

Client Networking and Personal Database are sometimes referred to as
"runtime" licenses. (In Version 6 of Progress there was a license
type call Runtime.) They are deployment licenses that get sold as
ways to provide the Progress "engine" to run precompiled applications.
However, they can compile encrypted source code. A special startup
parameter is needed to turn on the ability to compile encrypted source
code: -rx. This is the parameter that also enables the option in the
Data Dictionary that lets you load .df (data definition) files.

On the development side, an additional Progress product is required
for encrypting source code. It's called Developers Toolkit. It is
not part of the Provision License. See the Product Configuration
Guide for a description of Developers Toolkit. See Kbase number 14068
(QBW: encrypt) for some important information on how to deploy
encrypted source code.

The two runtime licenses (Client Networking and Personal DB) include
the Report Engine, so that they can run programs that use reports
developed with Report Builder.

Kbase number 16291 has useful information about errors customers might
see with respect to their compile capabilities.


Notes on Character vs. Gui mode (v7 only)
=========================================

The character mode product is often referred to as the DOS product,
and the gui mode product is often referred to as the Windows product.
This is how they're listed in Marketwatch.

As of 7/98 the latest character release for version 7 is 7.3B. That
release was originally not compatible with Win95, but the latest patch
for 7.3B provides Win95 compatibility.

As of 7/98 the latest release for gui mode on PCs is 7.3E.

There are two main sources of confusion about dos/character and
gui/windows:

1. People assume that if they're running Progress on a Windows machine
they should get the Windows release. But the important thing is
whether they want to run gui or character mode. If they want to run
character mode on a Win95 PC, they still need the 7.3B "DOS" release
because that's what provides the character mode executables. However,
the ProVision "windows" release provides both gui and character mode,
so that may be what they want to use.

2. As mentioned above, ProVision does both gui and character mode.
It is the only license that "officially" includes both. All other
licenses just have one or the other, but not both. However, the
gui/windows 4GL license accidentally includes _progres.exe (the
character mode executable). That was logged as a bug but never
addressed. This leads some people to think that they can do both
character and gui development with the 4GL license. However the 7.3E
4gl license does not include all files needed by the character
executable, and customers may run into problems. (One example of this
is that the file rundos.exe is not included.) Customers who want to
do character mode development should purchase either ProVision or 7.3B
(DOS) 4GL.


Packaging Issues That are Important When Installing
===================================================

The media we ship (both the CD-ROM and the set of diskettes) contain
all the files needed for any of the licenses for a particular version
of Progress. (This was not true in Version 6.) The serial number and
control codes entered dictate what the license type is and what files
get installed for the license. This fact can come in handy if a
customer forgets to order something (for example, they ordered only
Query/Results and they need to get Client Networking too). They just
need to get a serial number and control codes for the piece they are
missing. They do not need to be shipped new media. However, there
will be charges for purchasing an additional license-- Sales
Administration handles those details. Tech Support cannot place an
order for an additional license.

When query/results is ordered with client networking, those two
products need to be installed together. In order for products to work
together, they need to be listed in the same progress.cfg file. The
way to achieve that is installing them together. The same sort of
thing holds true for Report Builder.


Checking on What License(s) a Customer Has
==========================================

The serial numbers, names of the products and other useful information
about licenses that a customer has installed are stored in a file
called progress.cfg that is put by default in the DLC directory. In
V7 there is an executable in the DLC\BIN directory called showcfg.exe
that displays the information in the progress.cfg file. The syntax
for this command is:

showcfg path\progress.cfg [ |more ]

The progress.cfg file is not a text file, but you can see some of the
information in it by just typing it from the DOS prompt (e.g. type
progress.cfg). This comes in handy if the customer needs a quick way
to get their progress serial number. Another useful thing to know is
that you can display the serial number in the Progress procedure
editor by typing: display _serial.

In Version 8, the showcfg command is a windows command and there is an
icon in the Progress Program group and also an icon in the PRO*Tools
menu bar that will execute the showcfg command. The icon in the
Progress Group is labeled Progress Config. Both icons have a large
blue lower case i. In V8 there is also a DOS version of the showcfg
command if you want to run from the DOS prompt. The executable name
for that is showcfgd.exe.

Kbase number 16249 has information on errors customers might see if
they don't have the correct product for what they're trying to do.

VZA (Oct 06 1999)