PFW 5.3 Upgrade Guide

Upgrade Guide 5.
4PFWUG640
Information in this document is furnished only under a Customer License Agreement
or non-disclosure agreement, and may be used or copied only in accordance with the
terms of such agreement. The software described in this document is protected by
copyright, and may not be copied on any medium except as specifically authorized in
the license or non-disclosure agreement.
This document is also protected by copyright, and may not be reproduced or

transmitted, in whole or in part, by any means, including photocopying, facsimile
transmission, or reduction to any electronic medium or machine-readable form,
without the express written consent of Best Software Inc.
© 1984-2004 Best Software, Inc. All rights reserved.
Platinum is a trademark licensed to and a product produced by Best. Best is a

trademark of Best Software, Inc. Platinum is a registered trademark of PLATINUM
technology International, Inc. BatchMaster is a trademark licensed from
eWorkplace Solutions, Inc. Adobe and Acrobat are trademarks of Adobe
Systems, Inc. Pervasive, Pervasive.SQL, Scalable SQL, Btrieve, and the Pervasive
Software logo are trademarks or registered trademarks of Pervasive Software.
Microsoft, the Microsoft logo, MS, MS-DOS, and Microsoft Excel are registered
trademarks of Microsoft Corporation. Windows and Windows NT are trademarks of
Microsoft Corporation. FRx is a registered trademark of FRx Software
Corporation. Crystal Reports is a registered trademark of Crystal Decisions, Inc.
Other product names are trademarks or registered trademarks of their respective
owners.
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Compatibility Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Platinum for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
BatchMasterPFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
PFW 5.3 Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Chapter 1: Introducing Platinum for Windows 5.3 . . . .1
What’s New in 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Global Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Platinum for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
BatchMasterPFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Recap of 5.2, 5.11, 5.1, and 5.02 Features . . . . . . . . . . . . . . . . . .15
Version 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Version 5.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Version 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
BatchMasterPFW 5.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Chapter 2: PFW Installation Procedures . . . . . . . . . . .31
Pre-Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Version 4.6 through 5.0x . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Version 5.1x to PFW 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Upgrading from PFW 4.x or 5.0x to PFW 5.3 . . . . . . . . . . .44
Upgrading from PFW 5.1x to PFW 5.3 . . . . . . . . . . . . . . . . .45
Chapter 3: BMPFW Installation Procedures . . . . . . . .47
Pre-Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Platinum for Windows Preparation . . . . . . . . . . . . . . . . . . . .48
BatchMasterPFW Preparation . . . . . . . . . . . . . . . . . . . . . . . .56
Upgrade Process Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . .57
Warning for BatchMaster for DOS Users . . . . . . . . . . . . . . .58
Preliminary Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Versions 4.8a and Earlier . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Integrating with Platinum for Windows . . . . . . . . . . . . . . . .62
I
Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Upgrading Platinum for Windows to PFW 5.3 . . . . . . . . . . . . . . 65
Upgrading from BatchMaster 4.x to PFW 5.3 . . . . . . . . . . . . . . . 67
Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Initializing Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Copying Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Running the Parameter Conversion Utility . . . . . . . . . . . . . 71
Upgrading from BMPFW 5.0x to PFW 5.3 . . . . . . . . . . . . . . . . . 73
Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Chapter 4: Automatic Data Conversion . . . . . . . . . . . . 75
Automatic Data Conversion Wizards . . . . . . . . . . . . . . . . . . . . . 77
PFW Menu Upgrade Wizard . . . . . . . . . . . . . . . . . . . . . . . . 77
Understanding the Automatic Data Conversion Wizard . . . 79
How to Run Auto Data Conversion . . . . . . . . . . . . . . . . . . . 82
Security Data Conversion Wizard . . . . . . . . . . . . . . . . . . . . 84
Post Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Registering Platinum for Windows . . . . . . . . . . . . . . . . . . . 86
Registration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Special Considerations for Registering General Ledger . . . 95
Configuring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Reading the README Files . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 5: Before Processing in PFW Version 5.3 . . . 97
BatchMasterPFW 5.0x and PFW 4.x /5.0x . . . . . . . . . . . . . . . . . 98
Reviewing Your Current Settings . . . . . . . . . . . . . . . . . . . . 98
Generating Reports and Forms . . . . . . . . . . . . . . . . . . . . . . . 99
Special Considerations for Inventory Reports . . . . . . . . . . 101
General Ledger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Enabling Serial/Lot Tracking in PFW . . . . . . . . . . . . . . . . 102
Accounts Payable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Defining Masks and Auto Numbering . . . . . . . . . . . . . . . . 103
Establishing Cash Accounts . . . . . . . . . . . . . . . . . . . . . . . . 105
Posting by User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Reconfiguring Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Refreshing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Customizing Business Desktop . . . . . . . . . . . . . . . . . . . . . 111
II
Crystal Report Template Files . . . . . . . . . . . . . . . . . . . . . . .111
PFW 5.1x and 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Establishing Cash Accounts . . . . . . . . . . . . . . . . . . . . . . . .113
Refine User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Posting by User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Customizing Business Desktop . . . . . . . . . . . . . . . . . . . . . .114
Appendix A: Upgrade Checklist . . . . . . . . . . . . . . . . . 115
Upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Appendix B: Installation Procedures . . . . . . . . . . . . . 125
Server Installation of PFW and Pervasive.SQL . . . . . . . . . . . . .127
Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Installing PFW on the Client Workstation . . . . . . . . . . . . . . . . .135
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Installing Pervasive.SQL V8.1 Client and the PFW Client 136
Pervasive.SQL V8.1 Client Settings . . . . . . . . . . . . . . . . . .142
Files Updated by Platinum for Windows Installation . . . . .143
Installing MDAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Installing Acrobat Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
How to Install Acrobat Reader . . . . . . . . . . . . . . . . . . . . . .147
Post Installation for All Versions . . . . . . . . . . . . . . . . . . . . . . . .149
Additional Steps When Installing to a New Drive . . . . . . .149
Defining the Process Application Server (PAS) . . . . . . . . .151
Next Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Appendix C: Crystal Reports and PFW 5.3 . . . . . . . . 155
Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Platinum for Windows Product Registration Form . . . . . . .167
III
IV
Preface
Preface
Overview
Introduction Welcome to Platinum® for Windows by Best (PFW), version
5.3. Platinum for Windows by Best 5.3 is comprised of the
financial and distribution modules (PFW) and the process
manufacturing modules (BatchMasterPFW). For discussion in
this guide, BatchMasterPFW (BMPFW) and PFW may be
referred to as Platinum for Windows. Enhancements or issues
specific to either the BatchMasterPFW modules or the PFW
modules will be discussed separately.
About this guide This guide is intended for users upgrading from Platinum for
Windows 4.6 and any version of BatchMasterPFW to Platinum
for Windows 5.3.
This guide provides the following:
• Features included in PFW 5.3

• Pre-installation information
• Installation procedures
• Post-installation information
In this section This section provides information on the following topics:
Topic Page
Compatibility Information vi
PFW 5.3 Documentation Set x
Upgrade Guide Version 5.3 v

Preface
Compatibility Information
Overview
Introduction This section discusses the compatibility and upgrade path for
Platinum for Windows 5.3.
Upgrade Path The following table illustrates the installation path you must
follow to upgrade your current version of PFW/BMPFW to
version 5.3.
If your
Use this BMPFW Use this PFW upgrade
current
upgrade path... path...
version is
DOS 2.x 3.2 to 4.6x to 5.02 to 5.3 N/A

DOS 3.x 4.6x to 5.02 to 5.3 4.1a to 4.8a to 5.01
DOS 4.6x to 5.02 to 5.3 4.1a to 4.8a to 5.01
4.1x-4.5x
4.6x 5.02 to 5.3 5.3
4.7 5.02 to 5.3 5.3
4.8a 5.02 to 5.3 5.3
5.0 5.02 to 5.3 5.3
5.01 5.3 5.3
5.02 5.3 5.3
5.1 n/a 5.3
5.11 n/a 5.3
5.2 n/a 5.3
vi Upgrade Guide Version 5.3

Preface
Associated product Many other products interface to Platinum for Windows 5.3.
compatibility The following table displays the products and their compatible
versions.
Product Version
Abra 7.4
Abra Link 5.1
AuditMaster 6.1*
Crystal 8.5
FAS 2004.1
FAS Universal Link 5.3
FRx 6.7*
Pervasive.SQL V8.1
Premier Budgeting and 5.2
Advanced Allocations
StarShip 8.2*
*Version number subject to change.
Upgrade Guide Version 5.3 vii

Preface
Platinum for Windows

Upgrade Notes If you are upgrading from a version other than PFW 4.6 or
earlier, you must perform additional procedures before you can
upgrade to PFW 5.3. Additionally, users upgrading from pre-
4.6 versions may experience data corruption problems due
toY2K issues.
Upgrade to: Perform:

Pre-PFW 4.6
If you are on: PFD 2.x thru 4.x PFD 4.1a
Upgrade Tasks
Perform:
If you are on: PFD 4.1a thru 4.6 Pre-PFW 4.6
Upgrade Tasks
Perform:
If you are on: PFW 4.1 thru 4.5a Pre-PFW 4.6
Upgrade Tasks
Documentation of The additional procedures for upgrading to PFD 4.1a and the
incremental pre-PFW 4.6 upgrade tasks are detailed in the Upgrade Guide
upgrades Addendum available on the PFW 4.8a or 5.3 installation CD
for you to view online from Adobe Acrobat Reader. The file is:
\ \PLATINUM\PFWRES\MASTER\UPGRDADD.PDF
The addendum contains the following:
• Pre-PFW 4.6 Upgrade Tasks

This chapter provides instructions for users upgrading from
PFD 4.1a thru 4.6 or PFW 4.1 thru 4.5a. It includes only
those procedures that are required to prepare files for the
upgrade to PFW 5.3.
Note: If you do not have Acrobat Reader installed, you may

install it from the \\PLATINUM\ACRCLIEN\ directory on the
installation CD. Refer to “Installing Acrobat Reader” on
page 147 for instructions on installing Acrobat Reader.
viii Upgrade Guide Version 5.3

Preface
BatchMasterPFW
Upgrade Notes If you are upgrading from any version of BatchMasterPFW,
other than 5.01 or 5.02, it is required that you first upgrade to
version 5.02 before upgrading to version 5.3.
Upgrade to: Ver. 3.2 to 4.6x to Upgrade to:

If you are on: BMPFW 2.3 BMPFW 5.3
5.02
Upgrade to: Upgrade to:

If you are on: BMPFW 3.1x - 3.6x Ver. 4.6x to 5.02 BMPFW 5.3
Upgrade to:
If you are on: BMPFW 4.x - 5.0 Ver. 5.02 BMPFW 5.3
Upgrade to:
If you are on: BMPFW 5.01 or 5.02 BMPFW 5.3
Upgrade Guide Version 5.3 ix

Preface
PFW 5.3 Documentation Set
Hardcopy Your Platinum for Windows kit contains the following

hardcopy user’s guides:
• System Management
• Upgrade Guide
These are also provided online and are accessible from the
User’s Guide option on the PFW Help menu.
The System Management User’s Guide contains registration

instructions, your software license agreement, and support/
maintenance information.
This guide contains the steps required to upgrade to the new

version of PFW. It provides detailed steps and requirements for
BatchMasterPFW and Platinum for Windows products.
Online guides The following PFW documents are provided online for the
installed applications and are accessible from the PFW Help
menu:
System Basics Production

System Manager Formula
Accounts Payable Costing
Purchase Order Inventory
Accounts Receivable Purchasing
Sales Order Order Entry
Bank Book Laboratory
General Ledger - Standard MRP
Edition
Inventory MSDS
x Upgrade Guide Version 5.3

Preface
Multi-Currency Labeling
Premier Financial Business Insights
Applications
Project Costing
README files Readme files for the PFW applications are provided online
from the PFW Help menu. You must read these files before
you configure PFW 5.3.
You may also open the README files by opening the

following file on the installation CD:
\\PLATINUM\PFWRES\MASTER\DDMASTER.HLP
Miscellaneous The following documents are also provided online as

online documents selections from the Other Online Documents option on the
PFW Help menu:
• Database Reference Guides for version 5.3

• Partner Services Directory (third-party directory) HTML
link to the web.
Upgrade Guide Version 5.3 xi

Preface
xii Upgrade Guide Version 5.3

Chapter 1
Introducing Platinum for
Windows 5.3
Introducing Platinum for Windows 5.3 Chapter 1
Overview
Introduction This chapter provides an overview of the changes and
enhancements made in Platinum for Windows 5.3.
In addition to the enhancements that follow, many Problem

Tracking Reports (PTRs) were addressed in this release. You
can view the fixed PTRs on Best Online Support & Service
(BOSS).
Language Preservation of language translation is not covered in this

translation Upgrade Guide. See your Best Business Partner or Authorized
Consultant regarding translation preservation issues.
In this section This section contains the following topics:
Topic Page
What’s New in 5.3 2
System Requirements 12
Recap of 5.2, 5.11, 5.1, and 5.02 Features 15
Upgrade Guide Version 5.3 1

CHAPTER 1 Introducing Platinum for Windows 5.3
What’s New in 5.3
Overview
Description This section discusses new features available made in the 5.3
release of PFW. The global features are available for both
BatchMasterPFW and PFW.
Global Features
Unified Installation Both BatchMasterPFW and PFW modules install from one CD
and will release together going forward.
Business Desktop The NEW Business Desktop is a powerful alternative to your

standard menu browser. With a flexible TreeView design,
similar to Outlook and Explorer, you will be better organized
and more efficient.
The Business Desktop is designed to improve workflow. You

can easily create and rename tasks as well as drag and drop
tasks from one folder to another. If you use spreadsheets and
other documents daily, you can really take advantage of the
ability to add shortcuts and URLs.
The main page of your Business Desktop also provides

important links and information on the latest features,
education, support, and web resources. The Web Resource
page provides easy access to Best Online Support Services
(BOSS), free Web Events, Education Schedules and more.
2 Upgrade Guide Version 5.3

What’s New in 5.3
Improved Security Due to growing concerns about compliance with regulations

like Sarbanes-Oxley, we have added several configurable
security options. The Admin can control password expiration,
login attempts, and the acceptable format for passwords. The
Admin menu provides a Security Data Conversion to upgrade
the file structure to support the following configurable security
settings:
• Password Format:
Minimum Length
Require Alpha Character
Require Numeric Character
Require Special Character
• Login Attempts Allowed
• Number of Days to Expire
• Force password change next login
Should a user forget his or her password, the Admin can reset
the password and require the user to change their password the
next time they login. In addition, users can easily change their
password on the Login screen. Passwords are encrypted to
ensure the highest level of security.
Many of you will be excited about the User Group Security

Report, because this tool will allow you to quickly and easily
verify menu item access for your users and user groups.
Several parameters are available, so you can print just the
information you require.
Business Insights Business Insights consolidates critical information and enables

single click access to analytical and collaborative tools.
Information is easily accessible and can be displayed in a

variety of graphs and tables. This graphical presentation makes
it possible to interpret large amounts of data and quickly
identify business patterns and exceptions.
Business Insights was introduced in December, 2003, and is

compatible with Platinum for Windows version 5.2 and higher.
In version 5.3, Business Insights Select is automatically
installed with PFW System Manager and additional menu
items will appear in your new Business Desktop. If you do not

see these new menu items, ask your Admin to check your user
security. In addition, be sure to view the demo for the Business
Insights Professional version to see how you can take
advantage of flexible tools such as interactive HTML pages
and powerful PivotTables.
Enhanced Usability The following enhancements have been added to improve

usability throughout BatchMasterPFW and PFW.
Numeric Search Capability

This release includes a new numeric search option to locate
your data without typing the leading zeros. Of course, this new
feature does not impact our current method of search, Alpha,
and is optional for the following keys:
• Batch Number
• Container Key
• Customer Key
• Formula Key
• Item Key
• Ship To Key
• Vendor Key
When these keys are used to search, the system will remember
and default to the last search method, Numeric or Alpha, used
for the company you are in. Of course, with a single click you
can change your search method.
Template Defaults
Save time in your data entry screens by setting default values!
Your template screens now provide you with the ability to
assign default values for most fields. For example, customers
that do not use the Inventory Module have requested the ability
to set the Quantity Ordered field on the Sales Order Entry
screen to 1. A template can be used to assign this value, and the
data entry screen will automatically populate. Since the default
values are defined on templates, you have complete flexibility.
You can establish as many templates as you need to increase
data entry speed and accuracy per company, user group, or
globally as required.

What’s New in 5.3
Context Launcher
You can now quickly and efficiently open related menu options
from your context menu. For example, you could be updating a
customer address in Customer File Maintenance, and right-
click in the Customer Key field to launch the Sales Order Entry
menu option.
The customer account that is active in Customer File

Maintenance will automatically pass to the Sales Order Entry
lookup and display only the orders for that specific customer.
You can select the existing order, or close the lookup screen to
enter in a new order for any customer. The Context Launcher
typically provides several related tasks and is available in most
data entry screens that include a Customer Key or Vendor Key
field.
Drop Down List Boxes

In an effort to minimize the keystrokes required for data entry
and conform to Windows standards, we have changed the
format of fields where the options are provided by PFW or
BatchMasterPFW. For example, the status field of the Sales
Order Entry screen contains a static list of options. To select a
Quote status, you no longer need to open the lookup screen and
select the quote option. Now, you can simply arrow through
the selections available, because they are in a standard
Windows Drop Down List Box. To save time, you can type the
first letter of your selection, Q, in the status field to
immediately change the status to Quote.
Platinum for Windows

Purge and Archive Can you improve your process speed? If you have old data you
Utilities no longer need, increase your processing speed by purging
historic data! These new purge utilities can be scheduled to run
on your Process Application Server during non-peak hours. In
addition, all purged data is automatically printed on a report
and optionally archived to an Access database, so you can still
view the data using MS Access until you delete the archived
file.

Purge Inventory Transaction History

Has your Inventory Transaction History grown beyond a
manageable size? Organizations that process a large volume of
transactions will really benefit from this utility. You can now
Purge Inventory Transaction History by Item Key Range,
Location Key Range, Transaction Type, and through a Period
End Date. In addition, Cost layers will also be purged with the
corresponding transactions that qualify to keep your files in
sync.
Purge Chart of Accounts

Quickly remove accounts from your GL Chart that have not
had activity after a specified Period End date. Flexible
selection criteria can be used to isolate the specific accounts
you need, including: Account Number Range, Account
Number Filter and Account Type.
Purge GL Transaction History

We have had an overwhelming request for a utility that would
remove historical transactions from the General Ledger by
Fiscal Year. It is here! Transactions are deleted by batch using
the apply date of the header for qualification.
Enhanced Inter- With an abundant amount of Inter-Company transactions,

Company many of you will benefit from the ability to import this
information using the GL Spreadsheet Import Utility. Using a
new token, you can import the Inter-Company ID for the entire
batch or define the ID at the line item level. Enjoy this time-
saving feature.
Accounts Payable Locate the information you need with ease. We have enhanced
Features the Lookup for Voucher Entry, so you can locate your voucher
by the Vendor's Purchase Order number.
In response to several requests, the Vendor Invoice Number is

now displayed as a column on the Handwritten Check Entry
screen.

What’s New in 5.3
BatchMasterPFW
Pervasive.SQL V8.1 Pervasive.SQL V8.1 is available to customers that have
Pervasive.SQL included as part of their Best ClientCare plan.
With this version the user license design has changed, so user
counts will be handled with a license key rather than a separate
user count diskette. Additional improvements in
Pervasive.SQL V8.1 include:
• Increased Processing Speed

• Improved User Interface
• Auto-Reconnect Technology
Simplified No longer do you need to install PFW and BatchMasterPFW

Installation and separately. PFW 5.3 now allows you to install both products at
Administration the same time. Plus, the installation and Admin tasks are
completely windows based and wizard driven.
Furthermore, the Chem and Food demonstration companies

can easily be selected during the installation process.
The following utilities can be easily accessed from the Admin

menu:
• Auto Data Conversion

• Data File Recovery
• Data File Initialization
In addition, the Change Key utility has been divided into two
utilities, Change Item Key and Change Formula Key, for better
security control. These menu items can be found on the utility
section of the Inventory and Formula modules respectively.

Field Size Increases Need a little more room for your growing business? As our
customers grow, we continue to receive many requests for
increased field sizes. The entire list of fields can be found in
the table below:
Field Field Length

Ver. 5.02 Ver. 5.3
AP Invoice Number 10 20
Container Key 18 30
Customer Keys 5 12
Customer PO Number 15 20
Formula Keys 18 30
Item Keys 18 30
Labor Cost Keys 18 30
Prop (Property) Keys 18 30
QC Description 15 50
Requisition Number 5 16
Vendor Keys 5 12
In addition, document numbers have been expanded from a

length of 5 or 6 to 16. Each type of document number has a
corresponding user defined mask. This mask defines the static
portion of the document number plus the number of digits
desired (up to nine) for the system-generated portion of the
document number (e.g., 2004-######-12). The total size can
be no larger than 16 characters.
There can be a static portion in the mask both before and/or

after the numeric portion. The auto-increment portion must be
contiguous. In order to easily identify invoices and credit
memos, a new document number sequence, Next Credit Memo
Number, has been added to the OR- Process Options Setup
with a corresponding mask definition. Now when printing
invoices and credit memos in Accounts Receivable, documents
can reflect a specific numbering convention, based on the type
of document being printed.

What’s New in 5.3
Additionally, in Accounts Receivable, the printing and posting

of invoices and credit memos allows you to print and post
invoices independent of credit memos.
However, in order to accommodate those who wish to continue

to use a single auto-number sequence for both Invoices and
Credit memos, we have included a configurable setting that
will allow you use a single sequence for both.
Due to larger field sizes for document numbers, the option of

creating hexadecimal numbers has been removed.
Also, please note:
• Entire "masked" number will be saved as a transaction's

document number.
• Auto Data Conversion will create default masks with nine
digits and no static portion (i.e., #########).
• The Override Invoice Number option will prompt the user
to enter ONLY the auto number portion of the Invoice
Number.
• Reprint features require the user to enter the entire
Document number including the static portions.
• Customers using Serial/Lot numbers must post Invoices
prior to the upgrade.
In addition to field size changes, users may now enter up to

255 Physical Properties per Item. Previously this file was
restricted to 99 Physical Properties.
Notes and Access to critical information inspired the Universal Notes and
Attachments Attachments feature released in Platinum for Windows version
(Customers/ 5.2. Now BatchMasterPFW users can take advantage of this
Vendors) feature by entering notes and attaching vendor contracts or
other documents in Accounts Payable. These notes and
attachments can be viewed from several Purchasing screens
that include the Vendor Key. Similar functionality is also
supported in Accounts Receivable, so important information
for your customers can be accessed in several Order Entry
screens.

Action notes further enhance your ability to communicate

effectively with your employees that interact with vendors and
customers. Order Entry will immediately display any customer
action notes to inform your staff of credit holds or other
sensitive issues plus preserve public vendor and customer
notes.
Enhanced Labeling By popular demand, label sizes have been increased to

accommodate up to a 22 by 22 inch label. Customers printing
labels for gallon and drum containers can now take advantage
of the labeling module.
HMIS® A Personal Protective Equipment Code list has been added to

Compliance Update ensure HMIS® compliance.
The new HMIS® equipment code include:
Protective Equipment Codes

n - Splash Goggles
o - Face shield and eye protection
p - Gloves
q - Boots
r - Synthetic Apron
s - Full Protective Suit
t - Dust Respirator
u - Vapor Respirator
w - Dust & Vapor Respirator
y - Full Face Respirator
z - Airline Hood or Mask
Safety information is easily selected from an include list, and

will be concatenated with the Personal Protection code. This
method of selection will guarantee that each HMIS® value
contains only one capital letter, as required for compliancy.

What’s New in 5.3
Moving and An additional field, UPC, has been added to the Inventory
Enlarging the UPC Master file, offering you the ability to include this information
Field on custom Crystal Reports. This field is defined as
alphanumeric with a length of 14 and is blank by default.
BatchMasterPFW Many BatchMasterPFW customers would like to take

Bonus Items advantage of the PFW Utilities to Change Customer and
Vendor Keys. These utilities have been enhanced to
automatically update the BatchMasterPFW files respectively.
Have you ever used iShip to track your shipments? We have

added a weblink button to the memo field available in the
Order Entry module. The memo field, now labeled Memo/
Tracking, can be used to record the shipment tracking number.
When you use the weblink, this tracking number will
automatically pass to iShip and let you know the status of your
delivery.

System Requirements
Overview
Introduction The recommended system configuration is as follows.
Network File Server Due to the increased number of users that rely on Citrix and
declining customers on Novell Netware, PFW 5.3 will be
certified on Citrix. We will no longer be certifying PFW on
Novell Netware.
Network Operating Systems

Windows 2000 Server, Windows 2003 Server, Citrix
Metaframe XP, using Terminal Server Services, or Red Hat
Enterprise Linux ES Basic Edition (Kernel Version 2.4 or
above).
Windows Servers Minimum Hardware Requirements

• 500 MHz Pentium processor
• 512 MB RAM minimum
• 1 GB or greater free hard disk space
• Monitor: VGA
• 32-bit NIC
Software Recommendation
• Microsoft Access 2002
Hardware Recommendation
• 1.8 GHz Pentium processor
• 1 GB RAM
• Monitor: VGA
• 32-bit NIC

System Requirements
Citrix Metaframe Minimum Hardware Requirements

XP with Feature Operating Systems: Windows 2000 Server (SP4 or later with
Release 2 Server Terminal Services (Application Mode)), Windows 2003 Server
Enterprise Edition (Application Mode)
• 1.8 GHz or more Pentium processor

• 512 MB RAM
• 128 MB additional RAM for each additional client session
• 5 GB or more free hard disk space
• 2 GB free hard disk space for each additional client session
• 1.8 GHz or more Pentium processor
• 1 GB RAM
• 256 MB RAM for each additional client session
• 5 GB or more free hard disk space
• 2 GB free hard disk space for each additional client session
Client Workstations Operating Systems

and Process Windows 2000 Professional (SP4 or later), or Windows XP
Applications Professional (SP1a or later). Note that if you are using a PAS,
Servers it is not supported concurrently on a client machine or on the
PFW Server.
These requirements are valid for clients connected to a Citrix

Metaframe XP server.
Minimum Hardware Requirements

• 256 MB RAM Minimum
• 500 MB free hard disk space
• Monitor: VGA
• CD-ROM drive (one per network)
• 32-bit NIC
Software Recommendation
• Microsoft Access 2002

• 1.8 GHz Pentium processor
• 512 MB RAM minimum
• Monitor: VGA
• 32-bit NIC

Recap of 5.2, 5.11, 5.1, and 5.02 Features
Overview
Description If you are upgrading from any version of BatchMasterPFW or
from a version of PFW prior to 5.2, the following section
discusses the features added to the PFW financial and
distribution modules in the past three releases.
This section contains the following topics:
Topic Page
Version 5.2 15
Version 5.11 20
Version 5.1 21
BatchMasterPFW 5.02 29
Version 5.2
Description This section discusses changes made in the 5.2 release of the
PFW financial and distribution modules.
Note: Any feature that is specific to Inventory, Sales Order, or

Purchase Order is not available to BatchMasterPFW as it is
specific to the PFW Financial modules.
Global Cash In System Manager, you can now define your cash accounts,
Account banking information, auto-number, and masking information
for each bank account. Cash account availability in Accounts
Payable will be based on the bank accounts created in System
Manager. These bank accounts are also used by the Bank Book
module.

Universal Notes and Universal Notes and Attachments is a powerful feature that
Attachments allows you to view or create both notes and attachments. Notes
can be created in various fonts, colors, in bold or italics, and
quickly checked for spelling with the click of a button. You can
attach the notes or other documents directly to master file
records, transaction headers or transaction lines, and control
their behavior. Each note may serve a different purpose. Notes
may have the following options:
• Action flags for pop-up note functionality
• Importance setting for sorting and printing
• Effective and expiration dates
• Post with document flag
• Print note flag
Notes can be entered manually in rich-text format or uploaded

from files (pictures, .xls, .doc, .pdf, etc.). In fact, it may make
sense to include both text notes and an attachment. For
example, it may be helpful to provide a diagram and special
sales instructions for an inventory item that can be viewed by a
salesperson at the time of order entry.
Throughout Platinum for Windows, your toolbar will help you

quickly identify master file records or documents that have a
note or attachment. Note options control the characteristics of
the note. For example, Action notes automatically appear to
the user, and require a response before continuing. In addition,
if the note is flagged to "post with the document," your notes
will remain with the document as it moves through the system.
Therefore, a note entered in Sales Order Entry could be posted
through the system as the order is processed. Eventually, the
notes and attachments could be viewed from the corresponding
Accounts Receivable invoice.
Increased Field Several field sizes have been increased with this version of
Sizes PFW. The field sizes have been increased for:
• Vendor Invoice Number - 20 Characters
• Customer PO Number - 20 Characters
• Requisition Number - 16 Characters
• Manufacturer Part Number - 30 Characters
• Manufacturer Code - 30 Characters

Batch Printing and Platinum for Windows currently offers the ability to print and
Posting by User ID post batches of transactions by User ID in Inventory and
General Ledger. This feature has been added to the parameter
tab for several print and post menu items and report menu
items. They are as follows:
Application Business Desktop Item

Accounts Payable • Select Voucher or Debit Memo to
Post
• Unposted Voucher and Debit
Memo Report
• Post Voucher and Debit Memo
Accounts Receivable • Invoice Edit Report
• Print and Post Invoice and Credit
Memo
• Cash Receipts Register Report
• Bank Deposit Slip Report
• Post Cash Receipts
Purchase Order • Open Purchase Order Report
• Print and Post Purchase Orders
• Print and Post Purchase Order
Receipts
Sales Order • Sales Order Report
• Print and Post Sales Orders
• Invoice Edit Report
• Print and Post Invoices
Provisional Trial This multi-purpose worksheet has options for including/

Balance Report excluding a range of accounts, zero balances, and adjustment
period entries. In addition, the Trial Balance can be used to
compare with FRx reports to troubleshoot missing accounts in
FRx.

Single Check per You can now selectively print a voucher on its own check or
Voucher include it on a check that pays multiple vouchers. This can be
controlled at a vendor level or on a voucher-by-voucher basis.
Each vendor has a default setting in Vendor Maintenance that
can be activated if each voucher should print on a separate
check.
Alternatively, we have added an option for this feature in

Voucher Entry, Additional Cost Entry, Voucher Payment Entry,
and Purchase Order Entry, so the processing of the voucher can
be determined during the transaction processing cycle.
Lost or Damaged This release has a utility to record a check number as lost or
Check Utility damaged and supply a reason. This information prints on your
Accounts Payable Check Register and will then be moved to
history when the period is closed. In addition, the Lost or
Damaged Check Utility will look for a duplicate check number
and prompt the user to allow the entry if a duplicate is found.
Bank Book - Multi- Bank Book Journal Entry and Bank Book Journal Correction
User Journal Entry now include support for multiple users.
Enhanced Crystal With PFW 5.2, additional data files can be added to existing
Reporting PFW Crystal Reports, but only in the PFW Financial modules.
With this enhancement, you can add additional company data
files and custom Btrieve or Access Tables to PFW Access or
TTX based Crystal reports. Make sure you first copy the
original PFW report to your Custom directory to preserve
customizations. ODBC using Pervasive Server Engine, Btrieve
drivers, and Access drivers work great; however, if you will be
adding an Access table to a PFW Access based report, you may
need to address case sensitivity issues depending on your data.
Case sensitivity will not be an issue with Btrieve and ODBC
using Pervasive Server Engine.
Crystal Report If you want to create new reports and would like the standard
Template Files look and feel found on the existing PFW reports, you can use
the new report format files. These files are found on the PFW
Installation CD at the following location:

\\CWB\PFWRES\MASTER
In this directory, you’ll find SMULand.RPT (Landscape

layout) and SMUPort.RPT (Portrait layout). These files are not
installed but reside on the installation CD.
Additional UPC An additional field, UPC, has been added to the Inventory
Field in Inventory Master file, offering you the ability to include this information
on custom Crystal Reports. This field is defined as
alphanumeric with a length of 14 and is blank by default.
Customize Find You now have the ability to customize the find record lookup
Record Lookups windows for the following menu items:
• Accounts Payable
Voucher Entry
Debit Memo Entry
Additional Cost Voucher Entry
• Accounts Receivable
Invoice Entry
Credit Memo Entry
After the Fact Invoice Entry
Lookup Throughout the product, the lookups have been redesigned to

Functionality accommodate the addition of the Universal Notes and
Redesigned Attachment feature.
When you initially enter a lookup, the cursor is in the Search

box. As you enter characters in the Search box, the record most
closely matching your search is lightly highlighted. Once you
tab or click the record list, the highlight color changes and the
Universal Notes/Attachment button becomes functional, based
on the highlighted record. If the highlighted record has notes or
attachments, the Universal Notes/Attachment button is
available. If, however, the highlighted record does not have
notes, the Universal Notes/Attachment button is greyed out.
The Universal Notes/Attachment button is only available when

you are in the record list. For more information, refer to the
System Basics User’s Guide.

PO Negative Non- Negative non-inventory line items can now be added directly
Inventory Items to the purchase order, providing the flexibility to record the
line item to any available chart of account number. For
example, add a discount line to your Purchase Order, and select
the GL account number to post the transaction to.
New Look for User The User Guides now link to external PDF files when
Guides displaying sample reports. Because of this new feature, a
multitude of new PDF files are installed on the server in the
\\Platinum\PFWRes\Master directory. These new PDF files
reflect the reports found in PFW.
Version 5.11
Description Version 5.11 was a maintenance release. The primary focus of
this maintenance release was to resolve reported PTRs.
Additionally, the following enhancements were added.

Accounts Payable Negative non-inventory line items

You can enter a negative amount for non-inventory items on
Accrued or Re-accrued vouchers, prior to posting. The only
stipulation is that the voucher must have an overall value
greater than zero.
Purge History Transactions

This purge utility now purges the Transaction History
(APTRANH), Line Item History (APLINH), and Voucher
Header History (APHDRH) files.
Accounts Line Item History Listing

Receivable This listing is now a Crystal Report that can be customized.

PFW Financial Report Parameters

Modules You can save a report parameter with an assigned printer on the
Routing tab. However, when the parameter is saved, it is the
printer number from the printer list that is saved, not the printer
name. When the pre-saved parameter is run, the printer number
is used for output. If the person running the pre-saved
parameter doesn’t have the printer number in their list of
printers, the report is printed to that user’s default printer.
CWB Un-install This version provides an uninstall program for the

Customization Workbench product. This is available for both
the client and the server.
Version 5.1
Description of 5.1 This section discusses changes made in the 5.1 release of PFW.

New Expanded This release of PFW increases the field sizes of many key
Field Sizes fields found in several modules. For several of these expanded
fields, you can apply a mask to determine how many
characters you wish to use. Expanded field sizes and masking
provides greater flexibility in defining key values and for
reporting capabilities.
If you choose to take advantage of the new expanded field

sizes, keep in mind that any field that is all numeric will
automatically be zero filled. You may want to include an alpha
character to stop the zero fill process.
Conversion issue
During the auto conversion process, all expanded key fields
that contain only numbers (numeric) are filled with zeros.
However, all pre-saved parameters, that contain numeric
customer keys, are not zero filled. After the conversion, the
affected pre-saved parameters must be refreshed and saved.

Therefore, if you use any of the following keys in pre-saved

parameters, you will need to refresh and save these parameters.
The fields affected by this are:
Accounts Receivable Customer key
Ship to key
FOB key
Ship Via key
Terms key
Accounts Payable Vendor key
FOB key
Ship Via key
Terms key
Inventory Item key
Using Alpha Characters

If you have fields that are comprised of primarily upper case
characters, you may see characters trucated on reports. This is
due to proportional fonts and a limited amount of space on
some of the reports. There is a work around for this. By using
Crystal Reports Designer, that is shipped with PFW, you can
isolate the field that is truncated and decrease or change the
font of that field.
The following section discusses the expanded fields in each

module:
Accounts Receivable
Customer key - This field is now 12 characters long. The data
conversion to PFW 5.1 fills these fields with zeros if the
current customer key is numeric.
Ship to key - This field is now 8 characters long. The data

current ship to key is numeric.
Document numbers - These fields can now be up to 16

characters long and can be masked. This includes transaction
numbers, invoice numbers, credit memo numbers, apply to
numbers, check numbers, deposit numbers, finance and late
charge numbers. The data conversion to PFW 5.1 does not zero
fill or apply a mask to any of these numbers being converted.

FOB key - This field is now 4 characters long. The data

current FOB key is numeric.
Ship Via key - This field is now 4 characters long. The data
current Ship Via key is numeric.
Terms key - This field is now 4 characters long. The data

current Terms key is numeric.
Sales Order
Sales Order number - This field is now 16 characters long. The
data conversion to PFW 5.1 does not zero fill or apply a mask
to any of these numbers being converted.
Accounts Payable
Vendor key - This field is now 12 characters long. The data
current vendor key is numeric.
Document numbers - These fields can now be up to 16

characters long and can be masked. This includes voucher and
debit memo numbers, apply to numbers, and check numbers.
The data conversion to PFW 5.1 does not zero fill or apply a
mask to any of these numbers being converted.
FOB key - This field is now 4 characters long. The data

current FOB key is numeric.
Ship Via key - This field is now 4 characters long. The data
current Ship Via key is numeric.
Terms key - This field is now 4 characters long. The data

current Terms key is numeric.

Purchase Order
Purchase Order number - This field is now 16 characters long.
The data conversion to PFW 5.1 does not zero fill or apply a
mask to any of these numbers being converted.
Inventory
Item key -This field is now 30 characters long. The data
current Item key is numeric.
Bank Book
Document number - This field can now be up to 16 character
long and can be masked. The data conversion to PFW 5.1 does
not zero fill or apply a mask to any document number being
converted.
General Ledger - Standard and Premier

Account key - We will no longer be using sub-system lookup
account keys. As part of the PFW 5.1 data conversion process,
these sub-system account keys will be converted to the 32
character account number. The account number will come
from NLCHART. If NLCHART does not exist, LOCHART
will be used. If a corresponding 32 character account number
cannot be found, the 8 digit account key value will be placed in
the 32 character field.
Description - The Description field in all Journal Batch files is

now 60 characters long.
New Form Layouts The increased field lengths discussed above have made it
necessary to change the layouts of most the pre-printed forms
with the exception of Accounts Payable checks. The AP
checks did not change from version 5.01.
Note: Be sure to contact your forms vendor and order your

forms prior to upgrading to 5.1.
In order to take advantage of the larger field sizes, you will

need to either obtain new forms, or customize the report files
(.RPT) that produce the forms.

For those that will not be using the new longer field sizes, we
have created base .RPT files that can be used as a starting point
to create custom layouts for old forms. They can be found in
the \OLDFORMS sub-directory on the distribution CD.
Please be sure and save these old form layouts and your
customized report files to the appropriate \CUSTOM
subdirectory.
Auto Numbering Many types of document numbers can now have a

and Document corresponding, user defined mask. A mask consists of two
Number Masking parts;
• Static - An optional alphanumeric description
• Variable - A system generated number that must be a
contiguous number with no special characters.
This mask defines the static portion of the document number

plus the number of digits (up to nine) for the system generated
portion of the document number. In addition to defining a
mask, you can also enter the next available number.
For example, you might define a mask where the static portion
signifies the current year and the system generated number is
six characters long. Also, the auto numbering is set to begin
numbering with 000009. The mask will look like this:
2002-######
When a transaction is entered, using this mask, the new

document number will be 2002-000009.
The total size of a document number, including static and

system assigned number, can be no larger then 16 characters.
Additionally, the static portion of mask can be before and/or
after system generated number (e.g., 2002-########-12).
Installing PFW 5.1 provides a default mask for all document

number fields that is nine digits long (#########). Make sure
to review your masks before you begin processing with version
5.1.

When a transaction is saved, the entire masked number is

saved in the document number fields, including the static
portion.
Note: The PFW 5.1 conversion utility does not refresh pre-5.1
data using the new masking feature or expanded field sizes.
This provides historical reference to all original transaction
numbers.
Document Masking
Unique masks can be assigned to the following document
numbers:
Accounts Payable
Voucher Number
Check Number
Accounts Receivable
Invoice Number
Transaction Number
Deposit Number
Late Charge Number
Finance Charge Number
Credit Memo Number
Bank Book
Document Number
Purchase Order
Purchase Order Number
Sales Order
Sales Order Number
Credit Memos In Accounts Receivable, you can now setup a separate Credit
Memo number and Mask. This allows you to track credit
memos and invoices separately.
In addition, Print and Post Invoices and Credit Memos now

processes invoices and credit memos separately.

New Country File A new Country file maintenance and Country file listing are
and File Listing added to the System Manager tab. This new file maintenance
allows you to add, change, and delete country abbreviations
and names. The listing lets you print the countries that are in
this file.
The Country file maintenance is used by Accounts Receivable,

Sales Order, Accounts Payable, Purchase Order, and Project
Costing for country lookups in file maintenances and entry
screens.
Warning! This table is not maintained by PFW.

So, as countries need to be added, deleted, or
changed, it is up to the user to make these changes.
Note: Do not delete or change country key US or USA. These

are the default values and if they are changed or deleted this
will directly affect the applications that use this field.
Redesign of The sub-system lookup chart functionality has changed. The

Subsystem Lookup lookup chart files (GLCHART.*) are no longer created,
Chart Functionality updated, or used. This functionality is now completely
contained in the Chart of Accounts file (NLCHART).
When you setup a new account number or look at an existing

account number, you have access to the following new tab.

This tab lets you select the sub-systems that will have access to
each account number. This replaces the lookup charts.
Note: The PFW 5.1 conversion selects the sub-systems

previously setup in the prior versions of PFW.
Creating Custom You can customize existing Crystal reports and restrict these
Reports by new custom reports to a specific company or companies. To do
Company this, you must add the new report file (*.RPT) to a \CUSTOM
directory in a company’s directory. When that report is run
from the Business Desktop in PFW, the system looks first in
the \\Platinum\Company name\CUSTOM directory for the
correct *.RPT file. If it is found, that is the report format used
to generate the report.
If the*.RPT file is not found in the company’s custom

directory, PFW then checks the
\\PLATINUM\PFWRES\MASTER\CUSTOM directory. If it
is found, that is the report format used to generate the report.
Finally, if the *.RPT file is not found in the

\PFWRES\MASTER\CUSTOM directory, the report in the
\PFWRES\MASTER directory is used to run the report.
Data Conversion The upgrade to PFW 5.1 requires a data conversion in each of
your companies and within each company, of every data file.
The new expanded fields touch almost every data file in PFW
and requires the conversion process to rebuild every affected
file. Because of this, the data conversion will be time intensive,
based on the amount of data in your files.
You may want to archive and purge as much historical data as

possible prior to upgrading to 5.1. Many PFW applications
provide purge utilities that not only purge data but also provide
a list of the purged information. These lists can be archived by
saving the list to a disk or printing a hard copy of the
information.

New Demo Data PFW 5.1 provides you with updated demo data for the
following companies:
• GLSDEM
• PREMGL
• PRMTRN
• PRMCON
The upgrade to PFW 5.1 replaces the demo data in all of these
companies. If you want to save your current demo data, you
can backup the company data prior to installing.
Changes to Data PFW 5.1 converts all company data files to Pervasive.SQL
Files version 7 file format. Additionally, all floating point fields are
converted from BFloat (MBF) to IEEE Floating Point format.
Version 5.1 also added the new field sizes, some additional
spares, several new fields, and some changes to existing fields
to the DDF files. A new set of DDFs is included on the
installation CD, located in the \UIK directory on the CD.
For a complete list of PFW’s data files, that include the above
changes, refer to the Database Reference Guide
(CORETR.PDF). This file is located in the following
directory:
\\PLATINUM\PFWRES\MASTER
All changes made to the DDFs are displayed in a bold font.
BatchMasterPFW 5.02
Global Registration
Enhancements The registration process for all modules has been streamlined.
The relevant chapter in this guide describes the new process in
detail, which includes illustrations of the new windows.
Double byte support

BatchMasterPFW 5.02 enhances double byte character set
support. This improves performance and reliability where this
feature is used, most commonly in Chinese versions of
Windows.

Lot sorting
This release also enhances the search and sorting for lots
numbers by extending current sorts and searches for controlled
lots. This includes vendor key, location key, bin number, or
SSCC number. The sorting also includes new fields for
quantity on order, quantity committed to sales, quantity
committed to production, purchase order number, purchase
date, expiration date, and quarantine date.
Customer notes
This useful feature allows users to attach notes to customer
records, item records, or a specific combination of customers
and items from within sales order entry.
Citrix printing
This release streamlines report printing over Citrix-based
configurations to speed generation of large multi-page reports.
Module Specific Labeling

Enhancements The Labeling module has been added to this release. This
module automates the process of producing customized labels
for your in-stock inventory items and for items as they are
being received into your facility. It includes the use of various
fonts, templates, and barcodes. Refer to the Labeling User’s
Guide for a complete discussion of this module.

Chapter 2
PFW Installation
Procedures
Pre-Installation Procedures Chapter 2
Overview
Description This chapter discusses complete installation procedures that
you should be aware of when upgrading your current
installation of Platinum for Windows to PFW 5.3
Note: PFW is a complex and sophisticated software

product. The PFW 5.3 installation is a job for certified
personnel. For a successful installation, you should
seek the assistance of your Business Partner.
If you, as an end-user, choose to install PFW 5.3
without the assistance of a Business Partner, please be
aware that Best Software's technical support is limited
to specific questions about specific aspects of the
upgrade process and does not include guidance through
the upgrade process itself.
In this chapter This chapter contains the following sections:
Topic Page
Pre-Installation Procedures 32
Installation Procedures 43

C HAPTER 2 Pre-Installation Procedures
Pre-Installation Procedures
Overview
In this section This section discusses the pre-installation procedures for the
PFW 5.3 release.
Important! Use only the section that reflects your

current version.
Topic Page
Version 4.6 through 5.0x 32
Version 5.1x to PFW 5.3 39
Version 4.6 through 5.0x

Description If you want to successfully upgrade your system, you must read
the information in this chapter and follow the instructions that
apply to your system before you perform the installation.
Warning!You must have upgraded to PFW 4.6 or

later before performing these installation
procedures. If you are upgrading from any version
of PFD or a pre-4.6 version of PFW, refer to the
Preface of this guide for instruction.
Multi-Currency It is recommended that you not install this application if you

Manager will not be using it. This application contains features that
change the processing flow of the other applications. Even
though you will not be using these features, installation of
Multi-Currency Manager may slow your system and introduce
unexpected results.

Upgrade Process The following flowchart shows the procedures you will need to
Flowchart perform to complete the upgrade process from PFW 4.6, 4.7,
4.8, 4.8a, 5.0, 5.01 to PFW 5.3. To upgrade to 5.3 you must be
running version 4.6 or later. To upgrade to version 4.6, refer to
the Update Addendum located on the PFW 4.8a or 5.3 CD.
Perform Pre-Installation
Procedures
Chapter 2
Install PFW on the Network

File Server
Install PFW Install Pervasive.SQL
Appendix B
Install PFW on each Client

Workstation Remove prior versions of
Install Pervasive.SQL
PFW Client
Appendix B
Install MDAC
Install PFW Client
(if necessary)
Install Acrobat Reader (if latest

version is not already installed)
Appendix B
Run Automatic Menu Upgrade

Wizard (only runs if
Login to PFW 5.3 customizations are detected)
Chapter 4
Run Auto Data Conversion
Chapter 4
Perform Post-Installation
Procedures
Chapter 5

Order new forms - Prior to upgrading to 5.3, you will need to order new forms. All
new layouts forms have changed to accommodate the new field sizes
introduced in version 5.1, with the exception of Accounts
Payable Checks.
Cash basis If you are using Cash Basis accounting in Accounts Payable,
Accounts Payable you must void all checks that need to be voided, prior to
upgrading to version 5.3. A new void check program was
introduced with version 5.01 that only voids checks posted in
version 5.01 or later.
Purge historical The upgrade to PFW 5.3 requires a data conversion of every
data data file within each of your companies. Because of this, the
data conversion will be time intensive, based on the amount of
data in your files.

information.
Transaction Posting Because of the enlarged document numbering capabilities, it is

recommended that you post all unposted transactions prior to
upgrading. This includes:
• Vouchers (Accounts Payable)

• Invoices and credit memos (Accounts Receivable)
• Purchase order receipts (Purchase Order)
• Sales order shipments (Sales Order)
• Inventory transactions (Inventory)
• Journal batches (General Ledger)
• Journal entries (Bank Book)
If you upgrade to PFW 5.3 without posting these transactions,

you may have significant differences in transaction numbering.

Note: All document numbers are not converted. They will

remain in their original format and will not be masked. You
will notice a difference between pre-5.3 data and data entered
in 5.3 on reports, especially if you use the masking feature.
Backing up before Before installing this PFW 5.3 upgrade, you should back up
you install your entire PFW system including all companies. Another
option is to rename the \Platinum directory if you have
sufficient disk space available.
Demonstration During installation you are given the choice to install the
company data - demonstration companies for the Standard and/or Premier
saving existing data Editions of the General Ledger. For BatchMasterPFW the
Chem and Food companies are available for installation.
If you are installing only Platinum for Windows, and you

choose to install GL Premier Edition demo data, the program
will overwrite the existing data for demonstration company
PREMGL. If you choose to install GL Standard Edition demo
data, it will overwrite the existing data for GLSDEM. If you
choose to install Premier Consolidations or Premier
Translations, it overwrites the existing data for demonstration
companies PRMCON and PRMTRN, respectively.
If you are installing BatchMasterPFW, and you choose to

install the Chem and/or Food demo data, the installation will
overwrite the existing data found in their sub-directories.
If you want to save the existing data, you should:

1. Rename those company directories on your network file
server prior to installing PFW 5.3.
2. After installation, create a new company using the new
name given in Step 1.
3. Run the automatic data conversion utility on those
demonstration companies after installing PFW 5.3.

Converting pre- If you have created entry screen templates and would like to
saved templates use them in 5.3, you must do the following:
Step Action
1 Prior to installing 5.3, copy all ??TMPLAT.SRF files
found in the \\PLATINUM\PFWRES\MASTER direc-
tory to a new location. This can be a disk, CD, client
machine, or new location on the server.
2 Install version 5.3.
3 Once the installation is complete, copy the
??TMPLAT.SRF files back into the
\\PLATINUM\PFWRES\MASTER directory.
Turn Off Virus Because Platinum for Windows requires read/write access to
Checkers certain files during processing, it is recommended that
continual virus checkers be turned off or configured to only
check executable files during Platinum for Windows
processing. These programs may change the access rights of
files or cause errors during processing.
Language If you have defined more than one language, you must make
translation - sure the current language is set to English (United States) in the
resetting the PFW Language Selector before you perform the installation
language to English procedures.
Remove Lookup In each company directory, remove all GLCHART.* files.

Charts These are no longer used by PFW.
Remove Prior All prior versions of Btrieve or Pervasive will be removed from
Btrieve Versions the server and client workstations during the installation of
Pervasive.SQL V8.1.
The Pervasive.SQL V8.1 server installation includes a System

Analyzer process that checks for older versions of Pervasive. If
a prior version is found, that version is cleaned up and
optionally archived automatically by this process.

Note: Removing prior versions of Btrieve may affect

other installed products. If you have other products that
require Btrieve 6.15 or earlier, you may want to
upgrade them to a Pervasive.SQL V8.1 version.
Remove Prior PFW On each workstation that will be running PFW 5.3, remove all
Client Installations prior versions of the PFW directory using Control Panel - Add/
Remove Programs.
If this step is missed, you may receive the following error

when the queue manager attempts to open:
Error 382 qmReport set not supported at runtime
Remove Prior For any workstation running PFW 5.3, all prior versions of
Crystal Versions Crystal must be uninstalled. PFW 5.3 reports run using Crystal
8.5.

To remove prior versions of Crystal Reports from each

workstation, use the Crystal Clear utility. This is found on the
Platinum for Windows installation CD. In the
\PLATINUM\CLEANUP directory, select the
PFWCrystalClear.exe file. This removes most Crystal files.
You may need to use the following steps to remove additional
Crystal files.

Step Action
1 Using the Windows Explorer, search the System or
System32 directory in Windows or WINNT directo-
ries finding all local files using the following mask:
CR*.DLL
2 Once the Explorer returns the list of files, right click on

each file accessing Properties. Determine if it is a file
created by Seagate by viewing the Version tab.
3 If the file owner is Seagate Software, delete the file.

4 Re-install the PFW client software.

Version 5.1x to PFW 5.3

Introduction This section includes a process overview and identifies tasks
you may or may not need to perform prior to installing
Platinum for Windows when you are upgrading from PFW
5.1x or later to 5.3.
Topic Page
Upgrade Process Flowchart 40
Backing up - before you install 41
Demonstration company data - saving existing data 41
Language translation - resetting the language to English 42
Turn Off Virus Checkers 42

Flowchart perform to complete the upgrade process from PFW 5.1x or
later to PFW 5.3. Also included are the chapters in which the
procedures are located.
Procedures
Chapter 2

File Server
Appendix B

Workstation
Appendix B

Chapter 4
Chapter 4
Procedures
Chapter 5

Step Action
Backing up - before Before installing this PFW 5.3 upgrade, you should back up
you install your entire PFW system including all companies. Another
saving existing data Editions of the General Ledger. For BatchMasterPFW the
Chem and Food companies are available for installation.
If you are installing only Platinum for Windows, and you

choose to install GL Premier Edition demo data, the program
will overwrite the existing data for demonstration company
PREMGL. If you choose to install GL Standard Edition demo
data, it will overwrite the existing data for GLSDEM. If you
choose to install Premier Consolidations or Premier
Translations, it overwrites the existing data for demonstration
companies PRMCON and PRMTRN, respectively.
If you are installing BatchMasterPFW, and you choose to

install the Chem and/or Food demo data, the installation will
overwrite the existing data found in their sub-directories.


translation - sure the current language is set to English (United States) in the
resetting the PFW Language Selector before you perform the installation
language to English procedures.
Remove Programs.
If this step is missed, you may receive the following error when
the queue manager attempts to open:

Installation Procedures
Overview
Description This chapter contains installation procedures for upgrading
Platinum for Windows. Once the pre-installation requirements
are complete, you can continue the upgrade process.
Complete installation procedures are available for the

following:
• PFW 4.x, 5.0, or 5.01 to PFW 5.3
• PFW 5.1x or later to PFW 5.3.

current version.
If you want to successfully upgrade your system, you must

read the information in this chapter and follow the instructions
that apply to your system before you perform the installation.
In this section This section contains the following:
Topic Page
Upgrading from PFW 4.x or 5.0x to PFW 5.3 44
Upgrading from PFW 5.1x to PFW 5.3 45
Installation You install Platinum for Windows from a single CD-ROM that
CD-ROM includes all of the application files available for purchase. The
installation prompts you to select the applications that you
want to install. You may install the applications you purchased,
as well as unpurchased applications that you would like to
evaluate for a 30-day trial period. Within 30 days, you must
register the applications you have already purchased and any
additional applications you would like to purchase, or uninstall
any unpurchased applications.
Online documentation files are automatically included with

each selected application.

You must also have a Pervasive.SQL V8.1 CD-ROM designed

for your network operating system. The Pervasive CD carries
the name “Server Version for NT”. The Pervasive.SQL V8.1,
Server Version for NT is compatible with all operating systems
certified by Platinum for Windows, including 2003, 2000 and
NT.
Installation Complete step-by-step instructions for installation are

Instructions available, refer to Appendix B: “Installation Procedures” on
page 125.
Upgrading from PFW 4.x or 5.0x to PFW 5.3

Upgrade procedure Use the following steps to perform the upgrade process from
PFW 4.6, 4.7, 4.8, 4.8a, 5.0, 5.01, 5.1, 5.11, or 5.2 to PFW 5.3.
To upgrade to 5.3 you must be running version 4.6 or later. To
upgrade to version 4.6, refer to the Update Addendum located
on the PFW 4.8a or 5.3 CD.
Step Action
1 Perform the pre-installation procedures discussed ear-
lier in this chapter.
Note: Make sure to remove all prior versions of

Btrieve/Pervasive and Crystal before installing.
2 Install PFW 5.3 on the network file server. Complete
step-by-step instructions are available in Appendix B,
refer to “Server Installation of PFW and Perva-
sive.SQL” on page 127.
Note: It is recommended that you install PFW 5.3 to a

new location on your server.
3 Install Pervasive V8.1 on the network file server.
Complete step-by-step instructions are available in

Appendix B, refer to “Server Installation of PFW and
Pervasive.SQL” on page 127.

Step Action
4 Install Pervasive.SQL V8.1 client on each workstation.

Appendix B:, refer to “Installing Pervasive.SQL V8.1
Client and the PFW Client” on page 136.
5 Install PFW 5.3 on all client workstations, making sure
to remove all prior versions of the PFW from each
workstation. If you installed PFW 5.3 client on a new
location on the server, make sure to redirect the client
workstation to the new drive.

Appendix B, refer to “Installing PFW on the Client
Workstation” on page 135.
You may need to install MDAC and Adobe Acrobat on

each workstation.

Appendix B, refer to “Installing MDAC” on page 145
or “Installing Acrobat Reader” on page 147.
6 Once the installation process is complete, please
proceed to “Before Processing in PFW Version 5.3”
on page 97 for additional information.
Upgrading from PFW 5.1x to PFW 5.3

PFW 5.1x or later to PFW 5.3.
Step Action

Step Action
2 Install PFW 5.3 on the network file server.

workstation.


Chapter 3
BMPFW Installation
Procedures
BMPFW Installation Procedures Chapter 3
Overview
Description This chapter discusses complete installation procedures that
you should be aware of when upgrading your current
installation of BatchMasterPFW to PFW 5.3.
If you are integrated to Platinum for Windows, you’ll also need

to upgrade the financial modules to PFW 5.3. Instructions for
upgrading PFW are included in this chapter. If you are not
integrated with the Platinum for Windows financial modules,
you can skip the sections dedicated to upgrading PFW.
Note: BatchMasterPFW is a complex and sophisticated

software product. The 5.3 upgrade is a job for certified
personnel. For a successful installation, you should
seek the assistance of your Value Added Reseller
(VAR).
If you, as an end-user, choose to install PFW 5.3
without the assistance of a VAR, please be aware that
Best Software's technical support is limited to specific
questions about specific aspects of the upgrade process
and does not include guidance through the upgrade
process itself.
Topic Page
Pre-Installation Procedures 48
Installation Procedures 63

C HAPTER 3 BMPFW Installation Procedures
Overview
In this section This section discusses the pre-installation procedures for the
PFW 5.3 release. If you are integrated with Platinum for
Windows, you’ll need to upgrade both products.

current version.
This section includes:
Topic Page
Platinum for Windows Preparation 48
BatchMasterPFW Preparation 56
Platinum for Windows Preparation

Description If you want to successfully upgrade your system, you must read
the information in this chapter and follow the instructions that
apply to your system before you perform the installation.
Warning!You must have upgraded to PFW 4.6 or

later before performing these installation
procedures. If you are upgrading from any version
of PFD or a pre-4.6 version of PFW, refer to the
Preface of this guide for instruction.
Multi-Currency It is recommended that you not install this application if you

Manager will not be using it. This application contains features that
change the processing flow of the other applications. Even
though you will not be using these features, installation of
Multi-Currency Manager may slow your system and introduce
unexpected results.

Topic Page
Upgrade Process Flowchart 50
Order new forms - new layouts 50
Cash basis Accounts Payable 51
Purge historical data 51
Transaction Posting 51
Backing up before you install 51
Demonstration company data - saving existing data 52
Converting pre-saved templates 52
Remove Prior Btrieve Versions 53
Remove Prior Crystal Versions 54

Flowchart perform to complete the upgrade process from PFW 4.6 or
higher or 5.0x to PFW 5.3. Also included are the chapters in
which the procedures are located.
Procedures
Chapter 2

File Server
Install PFW Install Pervasive.SQL
Appendix B

Workstation Remove prior versions of
Install Pervasive.SQL
PFW Client
Appendix B
Install MDAC Install PFW Client
Install Acrobat Reader (if latest

version is not already installed)
Appendix B

Chapter 4
Chapter 4
Procedures
Chapter 5
Order new forms - Prior to upgrading to 5.3, you may need to order new forms.
new layouts All forms have changed to accommodate the new field sizes,
with the exception of Accounts Payable Checks.

Cash basis If you are using Cash Basis accounting in Accounts Payable,
Accounts Payable you must void all checks that need to be voided, prior to
upgrading to version 5.3. A new void check program was
introduced with version 5.01 that only voids checks posted in
version 5.01 or later.
Purge historical The upgrade to PFW 5.3 requires a data conversion of every
data data file within each company. Because of this, the data
conversion will be time intensive, based on the amount of data
in your files.

information.
Transaction Posting Because of the enlarged document numbering capabilities, it is

recommended that you post all unposted transactions prior to
upgrading. This includes:
• Vouchers (Accounts Payable)

• Invoices and credit memos (Accounts Receivable)
• Purchase order receipts (Purchase Order)
• Sales order shipments (Sales Order)
• Inventory transactions (Inventory)
• Journal batches (General Ledger)
• Journal entries (Bank Book)
If you upgrade to PFW 5.3 without posting these transactions,

you may have significant differences in transaction numbering.
Backing up before Before installing this PFW 5.3 upgrade, you should back up
you install your entire PFW (\Platinum directory) and BatchMasterPFW
(\BM3 directory) system including all companies. Another

saving existing data Editions of the General Ledger. DO NOT install either of these!
You can install the Chem and Food demo data sets for
BatchMasterPFW.
If you choose to install the Chem demo data, the program will
overwrite the existing data for demonstration company CHEM.
If you choose to install Food demo data, it will overwrite the
existing data for FOOD.

Step Action

translation - sure the current language is set to English (United States) in
resetting the the PFW Language Selector before you perform the
language to English installation procedures.
Remove Lookup In each company directory, remove all GLCHART.* files.

Charts These are no longer used by PFW.
Remove Prior All prior versions of Btrieve or Pervasive will be removed

Btrieve Versions from the server and client workstations during the installation
of Pervasive.SQL V8.1.
The Pervasive.SQL V8.1 server installation includes a System

Analyzer process that checks for older versions of Pervasive. If
a prior version is found, that version is cleaned up and
optionally archived automatically by this process.
Note: Removing prior versions of Btrieve may affect

other installed products. If you have other products that
require Btrieve 6.15 or earlier, you may want to
upgrade them to a Pervasive.SQL V8.1 version.
Remove Programs.


Remove Prior For any workstation running PFW 5.3, all prior versions of
Crystal Versions Crystal must be uninstalled. PFW 5.3 reports run using Crystal
8.5.
If this step is missed, you may receive the following error when
the queue manager attempts to open:
To remove prior versions of Crystal Reports from each

workstation, use the Crystal Clear utility. This is found on the
Platinum for Windows installation CD. In the
\PLATINUM\CLEANUP directory, select the
PFWCrystalClear.exe file. This removes most Crystal files.
You may need to use the following steps to remove additional
Crystal files.
Step Action
1 Using the Windows Explorer, search the System or
System32 directory in Windows or WINNT directo-
ries finding all local files using the following mask:
CR*.DLL

2 Once the Explorer return the list of files, right click on

each file accessing Properties. Determine if it is a file
created by Seagate by viewing the Version tab.
3 If the file owner is Seagate Software, delete the file.

4 Re-install the PFW client software.

BatchMasterPFW Preparation
In this section This section discussed the pre-installation procedures for the
BatchMasterPFW product. The following topics apply to any
version of BatchMaster or BatchMasterPFW.
If you are upgrading from version 3.x or earlier, refer to the

Upgrade Addendum for complete instructions.
Topic Page
Upgrade Process Flowcharts 57
Warning for BatchMaster for DOS Users 58
Preliminary Tasks 59
Versions 4.8a and Earlier 60
Integrating with Platinum for Windows 62

Upgrade Process Flowcharts

BatchMaster 4.x to The following flowchart shows the procedures you will need to
PFW 5.3 perform to complete the upgrade process from BMPFW 4.x to
PFW 5.3.
If interfaced to PFW, backup
ARSERIAL and APSERIAL
files
Install BMPFW 5.02 on the

Network file server and one Initialize BMPFW 5.02 If interfaced with PFW,
client workstation data fies copy company data files
Convert pre-save report

and posting parameters
Install PFW 5.3 on the network

Install Pervasive.SQL V8.1
file server
and hot fixes
Install PFW 5.3 on each client

workstation, removing all prior Install MDAC on
Install Pervasive.SQL V8.1
versions of BMPFW from each applicable workstations
client
Install Adobe Reader as

needed
Procedures
Chapter 5

BatchMasterPFW The following flowchart shows the procedures you will need to
5.x to PFW 5.3 perform to complete the upgrade process from BMPFW 5.x to
PFW 5.3.
Procedures
Chapter 3

File Server
Appendix B

Workstation
Appendix B

Chapter 4
Chapter 4
Procedures
Chapter 5
Warning for BatchMaster for DOS Users

Description This warning applies to you if you meet all of the following
criteria:
• You are using BatchMaster 4.x
• You are NOT integrated with PFW financial software
• You are using all numeric item/formula keys
All other BMPFW customers can disregard this notice.

BatchMaster for 4.x, supports an option that allows you to

disable the right-justify, zero-fill feature, which is enabled by
default. This affects numeric-only item keys for raw materials,
containers, finished goods, and formulas. It does not affect
non-numeric or alphanumeric item keys.
For example, by default a formula key of 1001 would be saved

as 000000000000001001. With the feature disabled, a formula
key of 1001 would be saved as 1001 (without leading zeros
being inserted).
If you have configured your version of BatchMaster for DOS

to disable the right-justify, zero-fill feature, your data will not
be usable in BatchMasterPFW until a special conversion is
performed. This is because BMPFW requires all numeric keys
to be right justified and zero-filled (the option to disable the
feature is not available). You need to obtain the updated
conversion utility.
Please contact your BMPFW reseller or BMPFW Support

Services if you have questions or for additional information.
If you have not disabled the feature (your numeric item keys
are already right justified and zero-filled) then you should
disregard this notice.
Preliminary Tasks
Introduction This section discusses tasks you should perform and
requirements you should be aware of before you begin the
upgrade process.
Windows 98 PFW 5.3 no longer supports Windows 98. Prior to upgrading,

platforms you must upgrade Windows to an accepted version. Refer to
the “System Requirements” on page 12 for a list of certified
products.
Backing up files Before starting the upgrade process, you must backup your
company data files. This allows you to compare pre- and post-
upgrade reports and provides for easier recovery in case errors
occur during the upgrade process.
You should make two (2) reliable backups of your BMPFW

and Platinum for Windows (PFW) company data files. The two
directories for each company that you are processing are:
• x:\BM3\[company] directory
• x:\Platinum\[company] directory
where x represents the drive letter where these directories

reside.
Note: In order to properly run the conversion program,

the system needs at least 2 - 3 times the amount of free
space of the largest company file. Company files are
usually maintained on the Server.
Using Lot Numbers Any PFW upgrade truncates your existing In-Stock Lot
Number (APSERIAL) and Sold Lot Number (ARSERIAL)
files. This means that the last several numbers identifying the
records will be arbitrarily cut off or shortened.
Backup and restore Prior to installing any PFW upgrade you must first backup both
the APSERIAL and ARSERIAL files from each processing
company. Once the PFW upgrade and data file conversion
processes are complete and just before you run the BMPFW
data file conversion, restore the APSERIAL and ARSERIAL
files to their respective processing companies.
Upgrading After you have reviewed the information in this chapter,

procedures proceed to Appendix B, Installation Procedures, then to the
section that outlines the upgrade procedure specific to your
current version of BatchMasterPFW.
Versions 4.8a and Earlier

Introduction This section contains information about modifications and
enhancements that were added to BMPFW after version 4.8a of
which you should be aware before you begin upgrade
processing.

Decimal places You must define decimal place settings for each BMPFW
module you have installed. The system will not operate
properly until you define decimal places in all modules,
because reports are formatted to fit a fixed amount of character
spaces per field regardless of where the decimal point is
positioned. You may wish to use BMPFW's System Manager
(SC) Company Defaults, Number of Decimal Places, as a
guide.
Duplicate files BMPFW tests to see if there are duplicate files in either the
\BM3\[company key] or the \PLATINUM\[company key]
directories. If one or more duplicate files exist, BMPFW
displays a message describing the situation and writes a
DUPLIST.LOG file to the \BM3\[user] directory. You need to
determine which of the two sets of data files are actually
required and move them to the \PLATINUM\[company key]
directory.
The only files that need to remain in the \BM3\[company key]

directory are ??CVTREV and ??PARAMS files, where ?? is
the two-letter BatchMasterPFW module prefix.
Disk space test The DOS command-line switch '/ST' has been added to the
BMPFW, DOS component, system startup program to skip
checking for amount of free disk space. A low disk space
warning occurs on disks with capacity greater than 2 gb
(2,147,483,647 bytes), regardless of the actual amount of free
space due to disk-check code, which cannot handle numbers
larger than 2 gb. When '/ST' is entered on the command line (or
in the startup DOS batch file) the disk checking routine is
skipped, and a message is not displayed.
User licensing Software License Control has been added to BatchMasterPFW,

starting with 4.8a SP1. From that release through BMPFW
5.01, the User License establishes the number of users
authorized to concurrently access BMPFW. User License also
tracks the number of users to ensure that the number of users
on the system does not exceed the authorized number.
BMPFW cannot be used without installing this option.

However, 5.3 ships with a default of one user license. You may
purchase additional licenses and activate them using the
Registration wizard. Refer to “Registering Platinum for
Windows” on page 86, for complete information about the
registration process.
Data dictionary files BMPFW data files have changed significantly. BMPFW date
(DDFs) fields no longer use a string-type date, but instead use a Btrieve
date.
If you access BMPFW data files from an external data file

editor, such as Access, Xtrieve, or Pervasive.SQL, you need to
use the new PFW version 5.3 set of DDFs from BMPFW in
order to access the new data files.
Integrating with Platinum for Windows

Introduction BatchMasterPFW can be run as a stand-alone application (not
integrated with the PFW financial modules) or it can be
integrated with Platinum for Windows.
Integrated with If you have already integrated BatchMaster and PFW and are
PFW upgrading from a version earlier than 4.6x, you must perform
any data conversions that PFW requires after installing 4.6x.
Important! For versions earlier than 4.6x, refer to

the section on “Upgrade Paths” on page 10 for
installation path information.
When data conversion is completed, you can then install PFW

5.3 and perform any data conversion, which it requires. The
installation of PFW 5.3 does not affect existing integration with
the exception of serialized lot tracking (APSERIAL/
ARSERIAL).

Overview
Description This section contains installation procedures for upgrading
BatchMasterPFW to version 5.3. Once the pre-installation
requirements are complete, you can continue the upgrade
process.
Complete installation procedures are available for the

following:
• Platinum for Window 5.x to PFW 5.3
• BatchMaster 4.x to PFW 5.3
• BatchMasterPFW 5.0x to PFW 5.3
Important! Use the section that reflects your

current version.
If you are upgrading from BatchMaster version 3.x or earlier,

refer to the Upgrade Addendum document found on the
Platinum for Windows 5.3 CD.
If you want to successfully upgrade your system, you must

read the information in this chapter and follow the instructions
that apply to your system before you perform the installation.
If you are upgrading from a prior version of BatchMasterPFW,

refer to the correct section for complete upgrade instructions.
All 5.3 upgrades must begin on BatchMasterPFW, version 5.01

or 5.02. Therefore, you must upgrade to 5.02 before attempting
to upgrade to version 5.3.

In this section This section contains the following:
Topic Page
Upgrading Platinum for Windows to PFW 5.3 65
Upgrading from BatchMaster 4.x to PFW 5.3 67
Upgrading from BMPFW 5.0x to PFW 5.3 73
Installation You install BatchMasterPFW 5.3 from a single CD-ROM that

CD-ROM includes all of the application files available for purchase. The
installation prompts you to select the applications that you
want to install. You may install the applications you purchased,
as well as unpurchased applications that you would like to
evaluate for a 30-day trial period. Within 30 days, you must
register the applications you have already purchased and any
additional applications you would like to purchase, or uninstall
any unpurchased applications.


certified by Platinum for Windows, including 2003, 2000 and
NT.
Migration Path It is important that you are familiar with the migration path for
your version of BatchMasterPFW (refer to “Upgrade Path” on
page vi). It is essential that all versions migrate to version 5.02
before upgrading to PFW 5.3.
Installation Complete step-by-step instructions for installation are

Instructions available, refer to Appendix B: “Installation Procedures” on
page 125.

Upgrading Platinum for Windows to PFW 5.3
Upgrading Platinum for Windows to PFW 5.3
Overview
PFW 4.6, 4.7, 4.8, 4.8a, 5.0, 5.01 to PFW 5.3. To upgrade to
5.3 you must be running version 4.6 or later. To upgrade to
version 4.6, refer to the Update Addendum located on the PFW
4.8a or 5.3 CD.
Step Action
Note: Make sure to remove all prior versions of

Btrieve/Pervasive and Crystal before installing.
Note: It is recommended that you install PFW 5.3 to a


4 Install Pervasive V8.1 client on each workstation.

Appendix B, refer to “Installing Pervasive.SQL V8.1
Client and the PFW Client” on page 136

Step Action
workstation. If you installed PFW 5.3 client on a new
location on the server, make sure to redirect the client



Upgrading from BatchMaster 4.x to PFW 5.3
Upgrade Procedure
Description Following are the procedures for upgrading BatchMaster4.x to
BMPFW 5.3.
Step Procedure
1 If BatchMaster is integrated with Platinum for Win-
dows, be sure to back up the ARSERIAL and APSE-
RIAL files before beginning the upgrade. (See “Using
Lot Numbers” on page 7.)
2 Install BMPFW 5.02 from the CD
3 Initialize BMPFW 5.02 data files. (See “Initializing
Data Files” on page 68.)
4 If BMPFW is integrated with PFW, copy required
BatchMaster data files from the \PLATINUM\[com-
pany key] directory. (See “Copying Data Files” on
page 69.)
5 If you are upgrading from BatchMaster 4.x and have
previously saved report and posting parameters, you
will need to run the Parameter Conversion utility to
restore these parameters to use in BMPFW 5.02. (See
“Running the Parameter Conversion Utility” on
page 71.)
Note: It is recommended that you install PFW 5.3 on a



Step Procedure
workstation. If you installed PFW 5.3 on a new loca-
tion on the server, make sure to redirect the client

You may need to install MDAC and Adobe Acrobat on

each workstation.

9 Install Pervasive V8.1 on each workstation.

Appendix B, refer to “Installing Pervasive.SQL V8.1
Client and the PFW Client” on page 136
Initializing Data Files

Introduction Because BatchMasterPFW 5.3 requires some data files that
were not available in previous versions, you must run the
Initialize Data Files utility to create them. Files must be
initialized for each of your companies individually.
Warning! As a precaution, you should save all data

files then load them back into BatchMaster when the
upgrade is completed.

Changing Before you begin initializing files, you MUST be in the

companies company for which the files are being initialized. Use the
Change Company option from the System Manager Main
Menu to enter the applicable company, available through the
DOS component.
Procedure detail Run the Initialize Data Files utility from the BMPFW DOS
component. Follow these steps to initialize each company’s
files.
Step Procedure
1 Select Company Setup from the System Manager
Main Menu.
2 Select Initialize Data Files. The following warning
appears:
Initializing files that already
contain data will erase that
data.
3 Select the module for which files are to be initiated.
You must initialize data files for each BMPFW module
you have licensed.
4 Press the <End> key or use the down arrow key to
highlight the last option, -ALL FILES-, then press
<Enter>.
5 Type ALL and press <Enter>. Files are now initialized
for the selected company and module.
6 Press <Esc> to skip any data files that BMPFW reports
as already existing. These files may already contain
data, which you do not want to overwrite.
Copying Data Files

Introduction BatchMasterPFW 5.3 looks for all data files in the
\PLATINUM\[company key] directory so you must copy all
BatchMasterPFW data files into this the correct directory.

Procedure detail Use the following procedure to copy data files:
Step Procedure
1 Copy all BMPFW data files from the \BM3\[com-
pany key] directory to the \PLATINUM\[company
key] directory, except for these two files:
• ??CVTREV
• ??PARAMS
where ?? is the two-letter BatchMasterPFW module
prefix.
2 Once you have copied these files, BMPFW displays
a Duplicate Files status message when you first start
BMPFW. The duplicate files are listed in the
DUPLLIST.LOG file in your \BM3\[user] directory,
and can be viewed with any ASCII text editor.
3 You can now safely delete the listed data files, except
for the ??CVTREV and ??PARAMS files, from the
\BM3\[company key] directory.

Running the Parameter Conversion Utility

Introduction If you have saved report and posting parameters that you want
to retain in BMPFW 5.3, you need to run the Parameter
Conversion utility to restore these parameters.
Procedure detail In version 5.02, the Parameter Conversion is available from

the System Manager (SC) menu and employs a wizard to
guide you through the process, as follows
Step Procedure
1 Select Parameter Conversion from the SC menu. The
Introduction window appears.
Click Next.

Step Procedure
2 The Upgrade Parameters window allows you to select
the companies to convert. Select the companies for
which you want the report and posting parameters con-
verted (or you can select the All Companies check
box).
Click Next.
3 The Finish window lets you know that all conversion
information has been entered.
Click Finish to complete the conversion process.

Upgrading from BMPFW 5.0x to PFW 5.3
Upgrading from BMPFW 5.0x to PFW 5.3
Overview
Upgrade Procedure
Description Following are the procedures for upgrading BatchMasterPFW
5.0x to BMPFW 5.3.
Step Action
1 Perform the pre-installation procedures discussed earlier
in this chapter.
2 Install PFW 5.3 on the network file server.Complete step-
by-step instructions are available in Appendix B, refer to
“Server Installation of PFW and Pervasive.SQL” on page
127.
workstation.Complete step-by-step instructions are
available in Appendix B, refer to “Installing PFW on
the Client Workstation” on page 135.
4 Once the installation process is complete, please pro-
ceed to “Before Processing in PFW Version 5.3” on
page 97 for additional information.


Chapter 4
Automatic Data Conversion
Automatic Data Conversion Chapter 4
Overview
Introduction An automatic data conversion must be performed after you
have completed the installation of PFW 5.3, regardless of the
version that you are upgrading from.
There are two auto data conversion utilities.

• PFW Menu Upgrade wizard
When you login to PFW 5.3 for the first time, the system
detects any menu item customizations from PFW 4.6
forward, and displays the PFW Menu Upgrade wizard
automatically.
• Auto Data Conversion wizard
This wizard is run by the System Administrator in PFW
5.3. Users upgrading must run this utility once for each
company. This wizard converts data from prior versions to
PFW 5.3.
• Security Data Conversion wizard
This wizard must be run if you have copied USERS.ADM
or UTGXR.ADM from a prior version to PFW 5.3. A
message automatically displays requiring you to run this
wizard.
Notification to If you attempt to access any menu item in a company that

perform data requires conversion before running the automatic data
conversion conversion, you are prompted to convert the data.

CHAPTER 4 Automatic Data Conversion
Topic Page
Automatic Data Conversion Wizards 77
Post Conversion 86

Automatic Data Conversion Wizards
Overview
Introduction The Auto Data Conversion wizard must be run for each
company requiring data conversion before processing in PFW
5.3.
Topic Page
PFW Menu Upgrade Wizard 77
Understanding the Automatic Data Conversion Wizard 79
Security Data Conversion Wizard 84
Post Conversion 86
PFW Menu Upgrade Wizard

Description When you login to PFW 5.3 for the first time, the system
detects any menu item customizations from previous versions
and displays the PFW Menu Upgrade wizard.
This wizard updates your PFW menu items as a result of:
• Menu item changes included in the new release

• Caption changes you made to system-delivered menu items
• The presence of user-defined custom menu items.

Procedure To run the PFW Menu Upgrade wizard, do the following:
Step Action
1 When the PFW Menu Upgrade wizard appears, read the
information provided by the wizard then click Ok.

Step Action
2 When the system has completed its preservation proce-
dures:
• Click View Log to view the changes that were made, if

desired
• Click Close to exit the wizard.
When you exit the wizard, you will need to login to Plat-
inum for Windows.
Log The log provided by the wizard records changes made by the
conversion.
Understanding the Automatic Data Conversion Wizard

Description The PFW Auto Data Conversion wizard rebuilds the entire
database in order to accommodate the increased field sizes and
the changes made to the data files.

The upgrade to PFW 5.3 requires data conversions in every

data file, within each company. The new expanded fields touch
almost every data file in PFW and BMPFW and requires the
conversion process to rebuild every affected file. Because of
this, the data conversion will be time intensive, based on the
amount of data in your files.

information.
The amount of time required to convert data depends upon the

version of PFW that you are upgrading from and the size of the
data files.
Hardware Since the data conversion rebuilds every data file, this process
requirements requires that the workstation used for the conversion have the
following minimum requirements, prior to converting your
data.
• 256 MB RAM
Additionally, the server drive must have two times a

company’s data size free to complete a conversion. For
example, the PREMGL demo company is 10 mgs in size.
Before this company can be converted, 20 mgs of disk space
must be free to successfully convert the data. This free space
must be on the same drive as the company’s data. You may
receive an Out of Memory error if you do not have enough disk
space available.
Conversion The complete conversion process for a company must be run

Requirement from one machine. Do not separate a company’s data onto
different machines to convert simultaneously.

2000 Server If you use Windows 2000 on the server, you may want to run
Suggestion the conversion from the server workstation. This can speed up
the conversion process.
Chart of Accounts The conversion process makes a backup copy of the chart of
backup file accounts file, prior to the conversion. For each company that is
converted, an NLCHART.P51 file is created in the company
directory. Do not delete this file after the conversion.
The NLCHART.P51 is the only link to the old 8 digit account

numbers and is not updated after the conversion is complete.
Note: While PFW 5.3 doesn’t use this file, 3rd party products
may use it to convert their products, so do not delete it after the
conversion is complete.
Numeric Keys Many numeric key fields are zero filled during the auto
conversion process. However, all pre-saved parameters, that
contain numeric customer keys, are not zero filled. After the
conversion, the affected pre-saved parameters must be
refreshed and saved.

Ship To key
FOB key
Ship Via key
Terms key
FOB key
Ship Via key
Terms key
Inventory (PFW and Item key
BMPFW)
Formula Formula key

How to Run Auto Data Conversion

Procedure To run the Auto Data Conversion wizard, do the following in
every company:
Step Action
1 Make sure you are logged into PFW as Admin.
2 Select Auto Data Conversion from the Admin menu.
3 Follow the instructions provided by the wizard.
4 Upon completion of the automatic data conversion, exit
the wizard.
Conversion Log As the conversion processes, a conversion log displays on the

screen. As each file is converted, it is added to the log,
including a status. The status of each file determines if that file
converted successfully or not. The log also displays the
number of records successfully converted.
Historically, this conversion log file is updated with any

conversion run on PFW, including the 5.3 conversion. Each
time a conversion begins, the conversion log is appended. The
appended information is always added to the end of the file.
Therefore, if you run several conversions, the log stores
information for each attempt or completed conversion. To find
the most resent conversion, you may want to look at the end of
the file first.
When the conversion is complete, the conversion log displays

a message, “Check company directory for *.DUP files”. If a
duplicate record is found in a file during the conversion
process, the first occurrence of that record is saved in that file.
The duplicate record is then removed from the file and added
to a *.DUP file in the company directory.
Note: Duplicate records are only saved in the *.DUP file for
duplicate key values to an index that does not allow duplicate
values. Most files allow duplicate values.

By viewing the *.DUP file(s), you can determine which

records are duplicates and if they need to be added back into
the file. A separate *.DUP file is created for each file where
duplicates are found.
Note: The *.DUP file is in text format and can be read using
Notepad.
Analyzing Duplicate Records

If you find *.DUP files in a company directory, you need to
determine if the duplicate records need to be added into the
PFW file or if those records are in fact duplicates that can be
discarded. You can use the following steps to analyze duplicate
records.
Step Action
1 Locate and view (using Notepad) the *.DUP files found
in the company directory.
2 In PFW, view the file that originated the duplicate (refer
to the file name).
For example, if you have a file APVENDH.DUP you

need to look at the AP-Vendor Activity file in PFW to
find the original records.
3 In PFW, find the record that matches the duplicate record.
4 Determine if the duplicate is a valid record or if it can be
discarded.
5 If the duplicate record is valid, you must enter the dupli-
cate record manually, making sure that it is unique.
6 Once all the records in the *.DUP files have been ana-
lyzed, you can delete the *.DUP files.
Incomplete If the user's system shuts down, or receives a run time error,
Conversion during the auto data conversion process, it should be able to be
restarted and pick up the conversion process where it left off. If
the application terminated during the middle of reading from
or writing to a data file it will resume at the beginning of the

read process for that data file when the application is

subsequently started. The user may also exit in the middle of
the conversion process and then restart where they left off (not
recommended!).
If termination occurs either during the read or write process,

the ".SAV" file (the prior version format data file) will be left
intact in the company data directory. The initialized, or
partially written to, 5.3 format data file will also be left intact
but will immediately be over-written the next time the data
conversion is run.
Additionally, an error log is created that documents the errors.

This log can be viewed by either:
• Clicking the view log button after the conversion process
• Or by viewing the PFWCV.LOG file found in the
\\PLATINUM\<company directory>.
Conversion Errors During the conversion process, you may receive errors. These
errors are documented in the conversion log. Below is an error
that you may receive and a suggested solution.
Run-Time Error 75
You may receive a Run-Time Error 75 - Path/File access error
during the conversion process if the conversion finds a data file
that has a read only status. When this occurs, the Auto Data
Conversion window stops on the read only file. If this occurs,
change the file properties to read/write and start the conversion
process again. The conversion resumes, begins with that file,
and continues until it completes the process.
Security Data Conversion Wizard

Overview The Security Data Conversion Wizard converts the Users.adm
and UTGXR.adm data files to the PFW 5.3 format. This
wizard is required if you have copied either of these files
during the upgrade process. These files store the user settings

that are defined by the Admin user. Often, after upgrading,

these files are copied from the prior version of PFW or
BMPFW to the new version. This moves all PFW user
information from one version to the other.
Because PFW 5.3 has added so much security functionality, it

is necessary to convert these files if they have been copied to
PFW 5.3.
To run the conversion wizard, do the following:
Step Action
1 Make sure you are logged into PFW as Admin.
2 Select Security Data Conversion from the Admin
menu.
3 Follow the instructions provided by the wizard.
4 Upon completion of the automatic data conversion,
exit the wizard.
If you forget to run this wizard before you begin processing,

the following message displays as soon as anyone tries to login
to PFW.
It is impossible to use PFW 5.3 until this wizard processes

successfully.

Post Conversion
Overview
Introduction Once you have installed PFW 5.3 (PFW or BatchMasterPFW)
and performed the automatic data conversion procedures, there
are several issues you need to be aware of and procedures you
must complete before you begin processing in PFW 5.3.
Topic Page
Registering Platinum for Windows 86
Special Considerations for Registering General Ledger 95
Configuring the System 95
Reading the README Files 96
Registering Platinum for Windows

Introduction When you register your software, you provide the Registration
department with information about your company, computer
system, and the serial numbers for the applications you
purchased. The registration process verifies your purchase and
adds your company information to the Registration
department’s database. At the same time, you can register to
receive software maintenance updates.
Grace period After installing Platinum for Windows, you have 30 days in
which to register the installed applications with the Order
Fulfillment and Registration Department. Additionally, you
are limited to a single user until PFW is registered.
30 Day Trial You can install unpurchased applications and use them for a
30-day free trial, however, you cannot register these
applications unless you purchase them.

Post Conversion
Following the 30-day grace period, the presence of any

unregistered applications causes the entire system to become
locked from access, including any applications that are
registered. To prevent this from occurring, you must uninstall
the unpurchased applications.
List of installed After installation, if you want to see a list of the applications
applications you have installed, open Platinum for Windows and select
About Platinum for Windows from the Help menu. Click
Application Info and the list of applications is displayed. The
applications listed are not necessarily those you want to
register; they are those you have installed. Alternatively, you
can log in as Admin and run the Registration wizard from the
Admin menu. This will show which applications are installed
and their registration status.
Purchasing You may purchase additional user or PAS licenses and activate
additional user them using the Registration wizard.
licenses and
applications You may also purchase and install additional applications.
Registration Instructions
Before you register Before you access BOSS, call or FAX the Registration
department to register Platinum for Windows, review the list
of installed applications. If you have not already or do not
intend to purchase one or more of the applications you
installed, you must uninstall those applications since they
cannot be registered.
Refer to the System Management user’s guide for instructions

on uninstalling applications that you have not purchased.

Registration on If you are registering your software via Best Online Support
BOSS Services (BOSS), use the following instructions:
Step Action
1 Install the software according to the instructions pro-
vided in the Platinum for Windows System Manage-
ment User’s Guide or Upgrade Guide, as applicable.
2 Choose Platinum for Windows from the Windows
desktop. A version window is displayed while the
system initiates the login process. Once the process is
complete, the Registration wizard is displayed.
The Registration wizard displays the number of days

remaining for you to register each time you log in to
Platinum for Windows. The day-count decreases by
one day for each subsequent calendar day, whether or
not you use Platinum for Windows on a given day.
To exit the Registration wizard and access Platinum for

Windows prior to receiving and entering your unlock
code, click Register Later.
The Registration wizard is displayed each time you

access Platinum for Windows until you register the
software.
3 Review the list of installed applications and uninstall
any that you do not intend to register. Refer to System
Management User’s Guide - Uninstalling Applications
Not Purchased for instructions.
Obtaining the Unlock Code:

Post Conversion
Step Action
4 Log onto BOSS. Access Profile Mgmt and then Products.
The following screen displays providing a list of all pur-
chased applications.
Click the PFW Product Registration button.

5 You are prompted for the Initialization Code. This can be
found on the Platinum for Windows registration screen,
as seen below:

Step Action
6 Your unlock key then displays.
Unlocking PFW:
7 When you receive your unlock code, start Platinum for
Windows and on the first window of the Registration
wizard, click Next.
8 Enter the site ID (if None is indicated) and unlock code in
the applicable fields.
Click Next.

Post Conversion
Step Action
9 If no errors occurred, a window showing the installed and
registered applications is displayed. Click Finish.
Logging in to Platinum for Windows:
10 When you exit the Registration wizard, you can log in
as the System Administrator by completing the Plati-
num for Windows Login window.
Registering via Fax If you are registering via a fax or phone, you must complete
or Phone and return the registration form to provide the Registration
department with information required for registration.
This form is found at the end of System Managers User Guide.

You use this form to provide the Registration department with
your initialization code, which is required for unlocking your
software. The initialization code is displayed on the
Registration wizard when you log in to Platinum for Windows.

Procedure Follow these steps to register Platinum for Windows via fax or
phone
Step Action
1 Install the software according to the instructions pro-
vided in the Platinum for Windows System Manage-
ment User’s Guide or Upgrade Guide, as applicable.
2 Choose Platinum for Windows from the Windows
desktop. A version window is displayed while the
system initiates the login process. Once the process is
complete, the Registration wizard is displayed.
The Registration wizard displays the number of days

remaining for you to register each time you log in to
Platinum for Windows. The day-count decreases by
one day for each subsequent calendar day, whether or
not you use Platinum for Windows on a given day.
To exit the Registration wizard and access Platinum for

Windows prior to receiving and entering your unlock
code, click Register Later.
The Registration wizard is displayed each time you

access Platinum for Windows until you register the
software.
3 Review the list of installed applications and uninstall
any that you do not intend to register. Refer to System
Management User’s Guide - Uninstalling Applications
Not Purchased for instructions.
Completing the Registration form:

Post Conversion
Step Action
4 Complete the Registration form. Refer to the last page of
this guide for the form. Be sure to include the initializa-
tion code shown on the Platinum for Windows Registra-
tion wizard screen.
Obtaining the Unlock Code:

5 Transmit the information on the Registration form and the
Serial Number form to the Registration department in any
of the following ways. Your unlock code will be assigned.
Fax: (949) 753-1593
Phone: US (888) 773-8989, option 2
International +1-949- 753-1222 ext: 4922
6 When you receive your unlock code, start Platinum for
Windows and on the first window of the Registration
wizard, click Next.

Step Action
7 Enter the site ID (if None is indicated) and unlock code in
the applicable fields.
Click Next.
8 If no errors occurred, a window showing the installed and
registered applications is displayed. Click Finish.
Logging into Platinum for Windows:
9 When you exit the Registration wizard, you can log in
as Admin by completing the Platinum for Windows
Login window.
Unlock code You are assigned an unlock code by the Registration

department or by BOSS. It unlocks your software, providing
continued access to your system.
The unlock code assigned is valid only for the initialization

code that appears on your system for your current installation.
If any of the following has occurred, the unlock code becomes
invalid, preventing you from continued access to the system
following the 30-day grace period.
• You install another application between the time you

receive and enter your unlock code.
• You register only some of your installed applications.
Post Conversion
Contact the Registration department by phone or fax to have

another unlock code assigned.
Warning! Do not attempt to reuse an unlock code

as it may cause undesirable results.
Special Considerations for Registering General Ledger

Running Premier If you installed both the Standard and Premier Editions of
Ledger on a trial General Ledger, the system runs Premier Edition. If, after
basis running Premier Edition during the 30-day grace period, you
want to register Standard Edition, you must uninstall Premier
Edition.
To see which editions of General Ledger you have installed,

login as the System Administrator and run the Registration
wizard from the Admin menu. If the list shows Premier Ledger
as installed, you still have both editions installed. If the list
shows Standard Ledger as installed, you have properly
uninstalled Premier Edition. If you do not uninstall Premier
Edition, you will not be able to register Platinum for Windows
with Standard Edition.
Configuring the System

Set up Once you have successfully installed Platinum for Windows,
configuration files login to the system as the System Administrator to set up
system-level configuration files. These files provide the
information that enables your users to access the system and
process data.
The configuration files set up one or more of each of the

following:
• Processing companies
• User security groups
• Users
• PASs (if applicable)
Instructions for setting up each of the above files are provided

in the System Management User’s Guide.
Reading the README Files

Description The README files contain information that is not currently
included in the user documentation. Some of the README
information is critical to successful processing of the Platinum
for Windows or BatchMasterPFW system. You should be sure
to read this information prior to processing in PFW 5.3.
You access the README files from the HELP menu on the
Platinum for Windows Business Desktop.

Chapter 5
Before Processing in PFW
Version 5.3
Before Processing in Version 5.3 Chapter 5
Overview
Introduction Depending on your installed applications and version that you
upgraded from, there are steps you must take to complete the
upgrade.

current version.
There are two sections in this chapter. You only need to refer to
the chapter that reflects the version of PFW or
BatchMasterPFW from where you are upgrading. You do not
need to read both sections.
In this chapter This chapter contains the following topics:
Topic Page
BatchMasterPFW 5.0x and PFW 4.x /5.0x 98
PFW 5.1x and 5.2 113

CHAPTER 5 Before Processing in Version 5.3
BatchMasterPFW 5.0x and PFW 4.x /5.0x
Reviewing Your Current Settings

Company Setup PFW 5.3 does not automatically update your company or user
and User Group group setup. After upgrading from a previous version you must
Setup wizards always review your current company and user group setups
and make any necessary changes. This is especially important
if you have installed any new applications or if a company’s
data has been split across drives.
Note: The feature allowing company data to reside on special

drives no longer exists in PFW 5.3. Therefore, after reviewing
companies where data is split, you must physically move the
data to the designated drive.
User Security PFW 5.3 offers new user based security options. It is important
that you update each user’s security and the Admin’s setup as
well. When updating the Admin user’s setup, you’ll need to
establish some system wide password options. These include:
• Minimum length of user passwords

• The number of allowable login attempts
• The number of days that a password is valid
• Any required characters in the password.
Reviewing existing When upgrading from a previous PFW version, the Group
access rights Definition and Group Access (UTGD.SRF and UTGXR.SRF)
files are not overwritten to include the new menu items. Before
users can be given access to those menu items in the Business
Desktop, the system administrator must access the User Group
Setup wizard and assign rights to all new menu items.
Reviewing system Verify the settings in your system configuration and file
configuration and maintenance menu items for each processing company in your
file maintenance installed applications, especially the Application Setup and
menu items Automatic Numbering menu items.

Generating Reports and Forms

Error 484 in If you receive this error when running a report, add a printer to
QMReport when the client workstation where the error occurred. Before you
printer is not can run reports, listings, or posting programs from a client
defined on Client workstation, a printer must be defined in Microsoft Windows.
This can be the default printer, a local printer, or a network
printer.
Verify reports To further verify successful conversion, use the following

steps:
Step Action
1 Generate the specified reports using equivalent parameter
settings to those you used before automatic data conver-
sion:
• Accounts Receivable: Aged Receivables report

• Accounts Payable: Aged Payables report
• Bank Book: Reconciliation report and Cash Balance
report
• Purchase Order: Open Order report
• Sales Order: Sales Order report
• Inventory: Planning report & Valuation report.
2 Compare totals in the pre-and post-conversion reports to
verify successful conversion.
3 Access and complete or revise all new data fields and
files.
4 Run your normal month-end procedure to ensure you are
still in balance.
5 When you have generated and verified all reports, make a
backup of the entire company’s new data files. You then
have a set of backup data for both pre-and post-conver-
sion versions. Be sure to use a separate location for each
backup you perform. Do not write over your pre-conver-
sion backups.

Preview All Forms With the variations in operating systems and printers, spacing
on individual combinations of pre-printed forms, operating
systems, and printer drivers may vary. It is important that you
have the current printer drivers for your printers, including dot
matrix printers -- the generic dot matrix printer driver will not
work properly with Crystal. Therefore, it is vital for you to
test all pre-printed forms prior to conversions. If you have
alignment problems, open the forms in Crystal Reports 8.5,
drag the fields to the appropriate locations for your
environment, then save the report in the appropriate
subdirectory. You can refer to “Creating Custom
Reports by Company” on page 28 for additional information.
The following .RPT files are used:
Form Crystal RPT file

AR Invoices & Credit Memos ARPINVCM.RPT
AR Statements ARRSTMNT.RPT
AP 1099 AP1099.RPT
AP Checks APPCKPRT.RPT
OR Bill of Lading OR7_BOL.RPT
OR Inventory Bill of Lading OR8_IBOL.RPT
OR Invoices and Returns OR4_IVL.RPT
OR4_IVS.RPT
OR4_IVZ.RPT
OR Packing Slip OR5_PACK.RPT
OR Sales Orders and Returns OR4_WOL.RPT
OR4_WOS.RPT
OR4_WOZ.RPT
PO Purchase Orders (PFW) POPFORMS.RPT
PU Purchase Orders PU3_PLZ.RPT
(BMPFW) PU3_POB.RPT
PU3_POC.RPT
PU3_POZ.RPT
SO Invoices OEPINV.RPT
SO Sales Orders OEPSORD.RPT

Special Considerations for Inventory Reports

Changes in Report Some reports in Inventory, version 5.3, display information
Data differently than prior versions. For example, if an inventory
item exists in the Item Location file but not in the Item Master,
prior versions of PFW would print “Item Not Found” or “Not
Found” in the Item Description. The old reports would then
include the Item Location detail on the report, even though the
item key and description were not available.
In PFW 5.3, items that do not exist in the Item Master file are
not included on the report. Only items that are present in both
the Item Master and the Item Location files are included on
reports.
Note: If you find that you have inventory items in the Item
Location file but not in the Item Master, you need to add these
items into the Item Master file manually.
General Ledger
Running the In some situations the GL Edit List creates provisional files
General Ledger that the automatic data conversion does not convert. To ensure
Edit List that this data is converted to the new format, you must run the
period or year end Edit List again after you upgrade to PFW
5.3. You must do this before you run a period or year end post
in PFW 5.3.
Important! If you do not perform this task as

described, you may corrupt your database.
Lookup Charts The lookup chart feature was replaced with the ability to
individually select which applications can use an account. In
the Chart of Accounts file maintenance you can determine the
sub system where an account can by used by clicking a
checkbox for each application. A new tab lets you select the
sub-systems that will have access to each account number.
The PFW 5.3 conversion selects the sub-systems equivalent to

sub-systems assigned prior to the conversion. You can change
this accordingly in the Chart of Accounts file maintenance.
Enabling Serial/Lot Tracking in PFW

Description If you are upgrading from any PFD version and were tracking
serial/lot numbers, or if you are upgrading from PFW 4.6 or
prior and want to begin tracking serial/lot numbers, you must
place a check mark in the Track Serial/Lot Number checkbox
in the Application Setup window in Inventory.
Accounts Payable
On account If you upgraded from PFD, you need to be aware that PFW
payments with does not allow on account payments with discounts. Any
discounts existing on account payments with discounts must be voided
and re-entered without the discount as follows:
Step Action
1 Activate the automatic data conversion for existing com-
panies. This clears any existing payments or application
of on account amounts that have not been posted.
2 Run the AP Current Transaction Listing:
• by Vendor Key / Apply To Document Number

• specifying that the listing include Transaction Type =
T (Discount Taken)
• with all ranges set First to Last
3 Void the documents on the listing using the Void Posted
Check utility.
4 Re-enter the documents by entering a handwritten check
in Cash Disbursement, being sure to:
• use the current processing date

• enter the original voided check number as the hand-
written check number
This procedure voids the on account payments with discounts,

removes the transactions from the Current Transaction file
(APTRAN), and replaces them with on account payments with
no discount. All General Ledger transactions generated by this

sequence are dated with the current processing date and any
discounts are generated at the time the on account payments
are applied to a voucher. Entering the same handwritten check
numbers as the voided checks provides an audit trail in Bank
Book reconciliation.
Defining Masks and Auto Numbering

Description Many types of document numbers can now a have
corresponding, user defined mask. A mask consists of two
parts;
• Static - An optional alphanumeric description
• Variable - A system generated number that must be a
contiguous number with no special characters.
This mask defines the static portion of the document number

plus the number of digits (up to nine) for the variable portion
of the document number. In addition to defining a mask, you
can also enter the next available number.
For example, you might define a mask where the static portion
signifies the current year and the variable number is six
characters long. Also, the auto numbering is set to begin
numbering with 000009. The mask will look like this:
2004-######
When a transaction is entered, using this mask, the new

document number will be 2004-000009.
The total size of a document number, including static and

system assigned number, can be no larger then 16 characters.
Additionally, the static portion of mask can be before and/or
after system generated number (e.g., 2004-########-12).
Installing PFW 5.3 provides a default mask for all document

number fields that is #########. Make sure to review the
masks before you begin processing with version 5.3.
When a transaction is saved, the entire masked number is

saved in the document number field.

Mask Size Although version 5.3 allows larger numbers, it is

recommended to be conservative when defining your mask. If
you choose to design a mask that fills the entire field size, keep
in mind that the variable number zero fills and may make it
more difficult to find specific transactions.
Converted Data The PFW 5.3 conversion utility does not refresh pre-5.3 data
using the new masking feature or expanded field sizes. This
provides historical reference to all original transaction
numbers.
When running reports, data will be separated by pre-5.3 data

and post 5.3 data, due to the difference in field sizes.
The following report displays data prior to the conversion and

data entered in 5.3 using the new masks. The invoice number
mask is IN-########-2004, notice the difference in the
document number column.
Sample Report
To view a sample report, click the following button.

Setting up Masks After installing PFW, you may want to setup masks for the
following numbers:
Application Menu Item Field Mask

Accounts Receivable Process Options Setup Transaction number
and BMPFW Order Invoice number
Entry Credit memo number
Check number
Deposit number
Finance charge number
Late charge number
Order number (for Sales Order)
Accounts Payable Auto Number Setup Voucher number
and BMPFW Purchase Order number
Purchase Order
Bank Book Auto Number Setup Document number
System Manager Cash Account File Check number and mask for each
Maintenance cash account
Once the masks have been setup, all data from that point
forward will reflect the masks.
Establishing Cash Accounts

Overview The cash accounts, used by both Bank Book and Accounts
Payable, are now stored in the System Management group on
the Business Desktop in the Cash Account file maintenance.
Before processing, you need to setup each cash account that
you use, in addition to the associated check number and mask
for each cash account. Once these accounts are setup, they are
used by both Bank Book and Accounts Payable for processing.
If, prior to upgrading, you have Bank Book installed and have
only one cash account setup, this step is optional. The
conversion process maintains the cash account previously
established. However, you may want to update the cash
account information, especially the next check number and
mask.

If you don’t have Bank Book installed, this step is required.

Refer to the Bank Book or Accounts Payable User’s Guide for
additional information.
Posting by User ID
Overview The User ID field has been added to the parameter tab for
several print and post menu items and report menu items. This
field allows you to print and post batches of transactions based
on the User ID. Plus, a new menu item on the SM -
Configuration tab, has been added that lets you determine the
default for this field.
Set this default option on the SM tab to determine if the User

ID is blank or if it defaults the currently logged in User’s ID.
Reconfiguring Your Data

Overview If you want to use the expanded field sizes for Customer Key,
Formula Key, Item Key and/or Vendor Key, you may want to
use the change utilities to update your existing data.
How to Change The Change Vendor Key or Change Customer Key menu items
Vendor and allow you to:
Customer keys
• Change an existing vendor/customer key to a new key
• Replace an existing vendor/customer key with an existing
key
• Merge an existing vendor/customer key with another
existing key
Vendor/customer keys with different class keys that have:
• Different account distribution mappings, or

• Different currencies
cannot be merged and should not be replaced.

If vendor/customer keys have different class key settings, the

existing account distributions and currencies for transactions
are not updated. New transactions will be posted according to
the account specifications in the new class.
Procedure Follow these steps to change, replace, or merge vendor/

customer keys:
Step Action
1 Select Change Vendor/Customer Key from the Busi-
ness Desktop.
2 Select an existing parameter and then Edit or Process;
or select New to create new parameters from the View
List window. The Change Vendor/Customer Key win-
dow appears.
3 Select the vendor/customer key you want to change,
replace, or merge from the lookup in the Old Vendor/
Customer Key field.

Step Action
4 In the New Vendor/Customer Key field, do the follow-
ing:
To.. a
vendor/
Then...
customer
key:
Change or Type in a new vendor/customer key.
rename
Replace Select the vendor/customer key which
you want to replace the old vendor/cus-
tomer key.
Warning: The data from the ven-

dor/customer key you enter in the
New Vendor/Customer Key field
replaces the data from the old
vendor/customer key.
Merge Select the vendor/customer key which
you want to merge with the vendor/
customer key you selected in the Old
Vendor/Customer Key field.
Warning: Various types of data

from both vendor/customer keys
will be combined in the new ven-
dor/customer key.
5 Click Process.
6 If you are merging or replacing a vendor/customer key,
a message is displayed to confirm that you want to
replace or merge the vendor/customer keys. Select
Replace or Merge and click OK.
Need more information? Press F1.

How to Change The Change Item Key Entry and Change Item Key menu items
Item Keys in PFW allow you to change:
Only
• Old item key references in the Item Master and Item
Location files to a new key
• References to the old item key as an Alternate Item Key in

the Item Master file to a new key (optional)
• Item key references in the current and historical GL

transaction files to a new key (optional)
Before you begin Before you run this process:
• Suspend data entry and file maintenance to ensure that all

records get changed.
• Print a Change Item Key Listing of all change records you

have entered, but not processed. This is your audit trail of
the changes that will be made.
Procedure Take the following steps to enter item key changes:
Step Action
1 Select Change Item Key Entry from the Business Desk-
top.
2 Complete the Old Item Key and New Item Key fields.
3 Save the record.
4 Repeat steps 2 and 3 for other item keys you want to
change.
5 Generate a list of the changes you have entered with the
Change Item Key Listing window.
6 Select Change Item Key from the Business Desktop.
7 Select an existing parameter to edit or process, or select
New to create new parameters from the View List win-
dow.
8 Complete the Selection document tab.

Step Action
9 Complete the Routing and Distribution tabs.
10 Click Process.
11 Save the parameters, if desired.
Need more information? Press F1.
Refreshing Parameters
Description All expanded keys that are numeric zero fill during the auto
conversion process. However, all pre-saved parameters, that
contain numeric keys, are not zero filled. After the conversion,
the affected pre-saved parameters must be refreshed and saved.

Ship To key
FOB key
Ship Via key
Terms key
FOB key
Ship Via key
Terms key
Formula Formula key
Inventory Item key
Additionally, for all report parameters created prior to 5.x, you

must also visit the routing tab. Version 5.x added additional
functionality to the routing tab that needs to be setup. These
features included:
• Remote and local processing (PFW only)

• Scheduling
• Output information.

Procedure Any pre-saved parameters must be refreshed and re-saved as

follows:
Step Action
1 Select the report, listing, utility, or posting menu item.
From the View List select the pre-saved parameter that
contains the invalid key.
Click the Edit button.

2 Use the lookup or enter the new expanded key.
3 Select the Routing tab and select the desired processing
method (local vs. remote), scheduling, and output.
4 Click the Save button. You can either save the changes to
the old name, or assign a new name for the pre-saved
parameter.
Click OK.
5 Repeat these steps for each pre-saved parameter.
Customizing Business Desktop

Overview The Menu Browser has evolved into the Business Desktop.
Once PFW 5.3 is installed, you can customized each user’s My
Tasks tab to include processes that they use. Additionally, you
may want to add any shortcuts or URLs that are used by each
user.
Crystal Report Template Files

Overview You may want to copy two template files from the PFW
Installation CD that allow you to create new reports with the
standard look and feel found on the existing PFW reports.
These files are found on the Installation CD at the following
location:
\\CWB\PFWRES\MASTER

In this directory, you’ll find SMULand.RPT (Landscape

layout) and SMUPort.RPT (Portrait layout). These files are not
installed but reside on the installation CD.

PFW 5.1x and 5.2
PFW 5.1x and 5.2
Establishing Cash Accounts

Overview The cash accounts used by both Bank Book and Accounts
Payable are now stored on the SM tab in the Cash Account file
maintenance. Before processing, you need to setup each cash
account that you use, in addition to the associated check
number and mask for each cash account. Once these accounts
are setup, they are used by both Bank Book and Accounts
Payable for processing.
If, prior to upgrading, you have Bank Book installed and have
only one cash account setup, this step is optional. The
conversion process maintains the cash account previously
established. However, you may want to update the cash
account information, especially the next check number and
mask.
If you don’t have Bank Book installed, this step is required.

Refer to the Bank Book or Accounts Payable User’s Guide for
Refine User Security

Overview PFW 5.3 offers new user based security options. It is important
that you update each user’s security and the Administrator’s
setup as well. When updating the Admin user’s setup, you’ll
need to establish some system wide password options. These
include:
• Minimum length of user passwords

• The number of allowable login attempts
• The number of days that a password is valid
• Any required characters in the password.

Posting by User ID
Overview The User ID field has been added to the parameter tab for
several print and post menu items and report menu items. This
field allows you to print and post batches of transactions based
on the User ID. Plus, a new menu item in the System
Management group - Configuration group, has been added that
lets you determine the default for this field.
Set this default option on the SM tab to determine if the User

ID is blank or if it defaults the currently logged in User’s ID.
Customizing Business Desktop

Overview The Menu Browser has evolved into the Business Desktop.
Once PFW 5.3 is installed, you can customized each user’s My
Tasks tab to include processes that they use. Additionally, you
may want to add any shortcuts or URLs that are used by each
user.

Appendix A
Upgrade Checklist
Upgrade Checklist Chapter 6
Overview
Description This appendix contains a suggested set of steps for upgrading
to version 5.3. This check list covers basic issues that should
be considered prior to and during a conversion.

A PPENDIX A
Upgrade Checklist
Procedure Use the following check list for upgrading Platinum for
Windows to PFW 5.3
Task Action
1 Verify Computers have supported Hardware and Software.
Server Client
500 MHz Pentium Processor 500 MHz Pentium Processor (1GHz preferred)
(1GHz preferred)
1 GB or greater Hard Disk space 1 Gb or greater Hard Disk space
(2 GB preferred)
Monitor: VGA Monitor: VGA
512 MB RAM Minimum 256 MB RAM Minimum (256 MB RAM
preferred)
32-Bit NC 32-Bit NC
Supported Operating Systems: Supported Operating Systems:
Windows 2000 Server Windows 2000 Professional

Windows 2003 Server Windows XP Professional
Citrix Metaframe XP, using Note: We will not be supporting WindowsXP
Terminal Services Home Edition.
Computer Operating
CPU Speed RAM Free HD Space
Server System

Upgrade Checklist
Task Action
2 Ensure that all workstations have the proper print drivers for all printers being
printed to. A "generic dot matrix" print driver will not work properly with Crys-
tal.
3 Ensure that all pre-printed forms are 8 ½ x 11 or A4 size. PFW 5.3 no longer
supports "short" forms due to Crystal limitations.
Order new forms!

4 List any third-party software or customizations that are being used with Plati-
num, and verify that they are compatible with PFW 5.3 from that vendor.
Currently Using? Software Vendor

IndustriOS IndustriOS Ltd.
Manufacturing 2000 Maynard Software Assoc.
Abra (Payroll and HR) Best Software, Inc.
Payware Service Technologies
FAS 2000 Best Software, Inc.
Laser Form Energizer or TransMicro
CheckFactory
Messenger Liason Software
FRx Desktop FRx Software
Premier Budgeting/Alloca- Best Software, Inc.
tions
5 Be sure to ask about any special processing they may do that PFW may impact.
Make sure this processing will still work, (for example: commission reporting,
interface packages).
6 Make backup of current PFD/PFW software and data.

A PPENDIX A
Task Action
7 Run balancing reports on old PFW version:
a) GL Report
b) AP Aged Payable Report (no cut off)
c) AP Distribution to GL (trial mode)
d) AR Aged Receivables Report (no cut off)
e) AR Distribution to GL (trial mode)
f) Cash Balance Report (all accounts)
g) BB Distribution to GL (trial mode)
h) Any others that may be required.
8 Log all people off of PFD/PFW. If not converting from PFD 4.6, go to step 10.
9 Upgrade from PFD to PFW 4.8a. Refer to the Upgrade Addendum for complete
instructions.
10 Install PFW 5.3 on Server.
a) Verify all users are logged off of the server where you will be installing PFW
5.3 and Pervasive.SQL. (You will be prompted for Pervasive and asked to reboot
the server after the installation.)
b) Log on as the Network Administrator.
c) Create a folder on the server called APPS off of the root of the server hard
drive that you will be installing on.
d) Assign Share rights to the new \PFW53 folder.
e) Map a drive to the \PFW53 folder. This will be the new permanent home for
PFW 5.3.
f) Install the PFW Server on the new drive letter, letting it create the \PLATI-
NUM subdirectory as is normal. If Pervasive.SQL V8.1 is already installed, you
do not need to install it again. If you have not loaded the hot fixes, do so now.
g) If you checked the Pervasive.SQL box, you will be prompted to insert the Per-
vasive.SQL CD. Make sure you have gone into the Server “services” and
stopped prior versions of Pervasive.SQL or Btrieve. Install Pervasive to the
default C:\PVSW directory on the server. Reboot the server if you are prompted
to.
You need to load the Pervasive hot fixes for V8.1. These can be downloaded
from the Pervasive website.

Upgrade Checklist
Task Action
h) Assign Share rights to the new \PVSW subdirectory and MAP a drive letter to
the new share.
i) We strongly recommend that you set up companies, groups, users and all other
security from scratch. If, however, you absolutely need to replicate the prior ver-
sion settings rather than starting from scratch, copy the security files from the
old \PLATINUM\ADMIN subdirectory to the new \PLATINUM\ADMIN sub-
directory.
Also, copy each user folder and contents from the old \PLATINUM\username
folders, creating new ones. Reset the UTQMSG file in each new user folder, and
get rid of any .MDB, .LDB, .RPT, .SAV, or .PRM files that are in the users' sub-
directories in the new area. Log in to PFW as Admin and make sure every com-
pany is pointed to the correct (new) drive letter.
11 Verify Network Communication and Pervasive settings.
a) Apply most recent Service Pack or hot fixes (if applicable). The hot fixes can
be downloaded from the Pervasive website.
b) On Windows 2000 servers, check the following:
• Right click on the computer’s icon and select Properties:

1) On the Performance tab, Performance Boost for Foreground Application
should be set to None.
2) Also, the Total Paging File Size is at least twice the physical memory of
the system.
• Right click on the Network Neighborhood icon and select Properties:
1) On the Services tab, select Server and press the Properties button. Select
Maximize Throughput for Network Applications.
c) Launch the Pervasive Control Center one of 2 ways:
• Run \PVSW\Bin\PCC.EXE from the drive you installed pervasive on

• From the Start Menu, choose Programs-Pervasive-Pervasive Control Center
Choose the server that you are running Pervasive on, then expand the Server
options. The following major categories and their settings should be verified/
changed. See following table:

A PPENDIX A
Task Action
Pervasive Control Center

Category Name Setting Name Value to be Set
Access Number of Sessions 50
Communication Buffer Communication Buffer 16384
Size Size
Communication Proto- Supported Protocols Make sure only TCP/IP is
cols selected
Communication Proto- TCP/IP Multihomed If you are running multiple
cols NICs in the server, this
must be set to On
Compatibility Create File Version 7.x
Data Integrity Archival Logging Off
Selected Files
Data Integrity Initiation Time Limit 3000
Data Integrity Operation Bundle Limit 200
Data Integrity Transaction Durability Off
Memory Usage Allocate Resources at On
Startup
Memory Usage Back to Minimal State if Off
Inactive
Performance Tuning Cache Allocation Size As large as possible, but
not more than one half of
available physical cache.
Performance Tuning Communications Threads Peak of files open (dis-
played in Pervasive Moni-
tor) divided by 8.
Performance Tuning Input/Output Threads 12
d) If you changed any settings, reboot the server.

e) You may now let users back into the network, and into the old PFW system.

Upgrade Checklist
Task Action
12 Prepare Workstation for install.
a) Verify Hardware and Operating Systems (see step 1).

b) Remove existing versions of Crystal. Refer to “Remove Prior Crystal Ver-
sions” on page 37.
c) Remove prior versions of PFW. Run the uninstall program, and be sure to
answer yes when prompted to remove .dll files that start with CR. These are pre-
vious versions of Crystal.
d) Using Regedit, look for and remove references to Btrieve Technologies.
13 Install Pervasive Client on workstation.
• X:\PVSW\CLIENT\WIN\setup.exe where "x" is the mapped drive on the file

server.
Note: The new client install for Pervasive.SQL V8.1 now scans for older ver-
sions of Pervasive.SQL and Btrieve that may have been missed in prior steps.
• Launch the Pervasive Control Center. From the Start Menu choose Programs
- Pervasive Control Center. Select Workstation, Configuration, Client. The
following changes should be made:
Pervasive Control Center
Category Name Setting Name Value to be Set

Access Target Engine Server Only
Access Use IDS Off
Communication Enable Auto Reconnect On
Protocols
Communication Supported Protocols Select TCP/IP only
Protocols
Security Runtime Server Support Off
14 Install PFW 5.3 client on the workstation. You do not need to install the PAS cli-
ent unless this machine will function as a PAS. However, if you will be using the
machine as a PAS, you must install the PFW client too.

A PPENDIX A
Task Action
15 Install MDAC (if necessary) on client workstations. This is loaded on the client
after the PFW client installation.
\PFWClien\MDAC_TYP.EXE
Reboot the client workstation.

16 Check the date settings in Control Panel - Regional Settings to make sure you
have a supported date format.
Make sure a printer is setup for each workstation in Control Panel - Printers.
17 Set up basic PFW parameters:
a) Log into PFW as Admin

b) Set up new companies, initializing data files for modules installed as needed.
You may find that there are already company definitions here (that were copied
in step 10l). If they are there, make sure they are pointing to the drive letter for
PFW 5.3 and not to the drive letter of the old PFW setup.
c) Log out of PFW
d) If upgrading from a prior version of PFW, copy the data files from the old
company subdirectories into the new ones. You will be overriding many if not
all files initialized in prior steps. We initialize them just in case they are upgrad-
ing from a version that didn't have as many files as PFW 5.3 (for example, the
Serial/Lot tracking files were added in PFW 4.7).
e) Log into PFW as Admin
f) Run Security Data Conversion if prompted.
g) Set up/verify logins for users and PASs (if they will be using PASs)
h) Setup new password security settings.
i) Run PFW Client Setup on machine(s) to be used as PASs.

Upgrade Checklist
Task Action
18 Run balancing reports (either locally or via PAS as appropriate).
a) GL Report
19 Confirm that other critical applications and/or customizations and report identi-
fied in steps 4 and 5 work properly with PFW 5.3.
20 If the client has continued processing in the prior version of PFW area while the
above testing has taken place, delete the company data files from new PFW area
21 If the client has continued processing in the old PFW area while the above test-
ing has taken place, run balancing reports on old PFW version:
a) GL Report
22 Log all people off of PFW.
23 Upgrade from PFD to PFW 4.8a.
a) Delete files from the company subdirectories created in the temporary PFW
4.8a area.
b) Copy the data files from the old PFD companies into the temporary PFW 4.8a
company subdirectories you just emptied.
c) Go to one of the PFD workstations (running true DOS 6 or Windows NT).
Start a DOS based PAS by executing the NETSTART.BAT batch file.
d) Switch to each new company and the auto conversion will launch.
e) After all conversions are done, end the DOS PAS session.

A PPENDIX A
Task Action
24 Convert companies to PFW 5.3
a) Log into PFW 5.3 as Admin

b) Re-initializing company data files for modules installed as needed (through
Company Setup - Modify Existing Company).
c) Log out of PFW
d) If upgrading from a prior version of PFW, copy the data files from the old
company subdirectories into the new ones. If upgrading from PFD, copy the
converted data files. In either case, you will be overriding many if not all files
copied over in prior steps. We initialize them just in case they are upgrading
from a version that didn't have as many files as PFW 5.3 (for example, the
Serial/Lot tracking files were added in PFW 4.7).
e) Log into PFW as Admin
f) If converting from PFD 8-character GL, perform GL Import
g) Run Parameter Conversion from Admin menu
25 Run balancing reports (either locally or via PAS as appropriate).
26 Install PFW Client on remaining workstations and repeat steps 12 - 16.
27 If converting from PFD, remove the temporary PFW 4.8a subdirectory and data
that was created.

Appendix B
Installation Procedures Chapter 7
Overview
Description This appendix contains the step-by-step instructions for
installing PFW version 5.3. Before installing version 5.3, read
Chapter 2: “Pre-Installation Procedures” for pre-installation
tips and Chapter 3: “Installation Procedures”for installation
procedures.
In this chapter This section has the following topics:
Topic Page
Server Installation of PFW and Pervasive.SQL 127
Installing PFW on the Client Workstation 135
Installing MDAC 145
Installing Acrobat Reader 147
Post Installation for All Versions 149
Installation Install Platinum for Windows or BatchMasterPFW from a

CD-ROM single CD-ROM that includes all of the application files
available for purchase. The installation prompts you to select
the applications that you want to install. You may install the
applications you purchased, as well as unpurchased
applications that you would like to evaluate for a 30-day trial
period. Within 30 days, you must register the applications you
have already purchased and any additional applications you
would like to purchase, or uninstall any unpurchased
applications.

APPENDIX B Installation Procedures


certified by Platinum for Windows, including XP, 2000 and
NT.
Server Installation Installation of the network file server includes:
• Installing the Platinum for Windows server files

• Installing Pervasive.SQL V8.1. plus hot fixes
Client Installation The installation of each client includes:

• Installing the Pervasive.SQL client files
• Installing the Platinum for Windows client setup programs
• Installing MDAC, if necessary
• Installing Adobe Acrobat

Server Installation of PFW and Pervasive.SQL
Server Installation of PFW and

Pervasive.SQL
Overview
Description The installation process is the same for both PFW and
BatchMasterPFW. This appendix discusses the installation
process, step-by-step.
Before you begin Before you install the Platinum for Windows 5.3 server files,
identify a drive on the network file server with sufficient space
for the installation and your data. Refer to the System
Management User’s Guide or “System Requirements” on
page 12, for minimum and recommended requirements.
When upgrading your system, you have a choice, you can:

1) Install PFW 5.3 to the drive where the current version is
installed. If you choose this method, follow the instructions
in this chapter, no additional steps are required.
2) Install PFW 5.3 to a new drive (recommended). If you
select this method, there are several additional steps that
are required, after installing PFW. Refer to “Additional
Steps When Installing to a New Drive” on page 149 for
complete post installation instructions.
Product Installation
Pervasive.SQL You may have received a Pervasive.SQL V8.1 CD-ROM
designed for installation on a Microsoft Windows Server, or it
may already be installed. It may also have been purchased
elsewhere.
The installation of PFW 5.3 server precedes the installation of

Pervasive.SQL V8.1.
For additional information on Pervasive.SQL V8.1, refer to the

Pervasive.SQL V8.1 documentation included on the
Pervasive.SQL V8.1 CD-ROM.

You can refer to the following location for installation

instructions (where D denotes your CD drive):
D:\Books\Getting_Started_Workgroup.pdf
D:\Books\Getting_Started_Server.pdf
Before you begin You must install PFW 5.3 and Pervasive.SQL V8.1 at the
server and be a system administrator or have administrative
rights to the system. You need administrative rights to make
the client folders available to the client workstations.
System Pervasive.SQL V8.1 has several system requirements for the

Requirements for server. Refer to the Pervasive documentation for complete
the Server details, specifically the Installation Checklist.
Installation Do not run the installation program from Windows Explorer or

Suggestions Network Neighborhood, use My Computer or the Control
Panel-Add/Remove Program.
Note: Do not install Pervasive.SQL V8.1 to a mapped drive on

the server.
If you run with Advanced Power Management, disable it while

installing Pervasive.SQL V8.1. The power management can
cause a Pervasive.SQL V8.1 installation to fail if the server is
suspended during the install. On a Windows Server, you
control the Advanced Power Management via the Power icon
on the Control Panel.
Procedure Use the following procedure to install the network files:
Step Action
Installing Platinum for Windows 5.3:
1 Reboot your Windows server, login as the Administrator, and close any Windows
applications that may start during startup, including TSR’s, screen savers, and
virus scanners. The reboot ensures that all DLLs have been properly unloaded.

Step Action
2 Run the server installation program at the server.
When you insert the CD, the Autorun program begins. If it doesn’t begin, locate
and run Setup.exe found on the CD.
3 Read the instructions in the Platinum for Windows Server Setup window.
Click Next.

Step Action
4 Read the licensing agreement.
Click Yes.
5 Read the registration and upgrading information.
Click Next.

Step Action
6 Select the product you are installing. You can choose Platinum for Windows or
BatchMasterPFW. If you select BatchMasterPFW, you can install both Batch-
MasterPFW and PFW at the same time. There is no additional step necessary to
install PFW with BatchMasterPFW
Click Next to continue.

Step Action
7 Select System Manager, the applications, and the demonstration data you want to
install. If you are installing BatchMasterPFW, all modules for both BatchMaster-
PFW and PFW are available for installation. Only select the modules you want to
install.
Note: If you are installing BatchMasterPFW, do not install the PREMGL and
GLSDEM demo data sets. The Chem and Food data sets can be installed as
demo data for BatchMasterPFW.
You will also be prompted to install a Process Application Server (PAS). A PAS
is now an optional module that can be installed, but is not required.
Enter the letter of the drive where the program files should be installed. Due to a
limitation on the number of files that can be installed to the root directory, you
must install to a directory below the root as follows (where M represents the drive
on the Microsoft Windows server):
M:\PLATINUM
Note: Do not use a period (.) in the path of the Destination Folder.
Review the displayed status of available disk space. The available disk space
should meet or exceed the displayed required disk space. If sufficient space is
available, click Next.

Step Action
8 Review the current settings. Click Next.
9 The system displays a progress indicator as each application is installed. When

the installation is complete, the following window is displayed:
It is recommended that you view the ReadMe file. Click Finish.

Step Action
10 Once the Readme has been viewed, the following option displays if you selected
to install Pervasive.SQL V8.1.
11 Insert the Pervasive.SQL V8.1 CD into your CD-ROM drive, Click OK. For com-
plete installation instructions, refer to the Pervasive.SQL V8.1 documentation.
You can refer to the following location for installation instructions (where D
denotes your CD drive):
D:\Books\Getting_Started_Workgroup.pdf
D:\Books\Getting_Started_Server.pdf
Modifying Pervasive.SQL V8.1 Settings
You must install the Pervasive Hot Fixes.
Pervasive Hot Fix After installing Pervasive.SQL V8.1, you will need to
download and install the latest hot fix from the Pervasive
website. The hot fix contains patches for both the server and
the client workstations. These can be found at the following
path:
http://www.pervasive.com/support/updates/
Next step With the setup programs for the Platinum for Windows client
interface files installed on the network file server, you can
begin to set up each client workstation. Refer to “Installing
PFW on the Client Workstation” on page 135.

Installing PFW on the Client Workstation
Overview
Description This task installs the Platinum for Windows interface files at
each client workstation from the setup programs previously
installed on the network file server. Typically, the first client
you set up is the System Administrator’s workstation.
Topic Page
Before you begin 135
Installing Pervasive.SQL V8.1 Client and the PFW Client 136
Installing MDAC 145
Installing Acrobat Reader 147
Before you begin

Drive designations Before you install the software to the client workstations, you
must ensure that all clients are using the same drive
designation and share name. For example, if all clients
designate L:\ as the Platinum base during installation, the drive
designation should also be mapped to L:\ when making
network connections.
If you are running or are planning to run a Process Application

Server (PAS) on the Windows file server, the above
designation should also be the same. In addition, the server
will have its local drive designation. For example, if the
\PLATINUM directory resides on the local drive C:\, it should
also be mapped to L:\ as its network connection. The
\PLATINUM directory must be a shared directory.

Logging off If other workstations are accessing Windows from the

network, they should be logged off the network. There are files
in the Windows System directory that are updated by the
Platinum for Windows 5.3 client installation process, such as
OLE automation servers. If these files are in use, they cannot
be updated and the Platinum for Windows client will not install
successfully.
Windows 2000, XP, If a workstation is running Windows 2000, XP, or NT, you
and NT must be logged in as the local Administrator before installing
PFW.
Installing Pervasive.SQL V8.1 Client and the PFW Client

Before you begin Remove all prior versions of the PFW directory on each client
workstation.
Note: Do not install the Pervasive.SQL V8.1 client on the

server. Pervasive.SQL V8.1 client should only be installed on
a client workstation.
Procedure Once you have installed the network server files, use the
following procedure to install the client workstation.
Note: The Pervasive.SQL V8.1 Client should be installed

prior to installing the PFW Client. The MDAC installation (if
needed) must follow the PFW Client.
Step Action
Installing Pervasive.SQL V8.1 Client:
1 Reboot your workstation and close any Windows applications that may start dur-
ing startup, including TSR’s, screen savers, and virus scanners. The reboot
ensures that all DLLs have been properly unloaded.
2 From the \PVSW directory on the server, install each client workstation. For com-
plete installation instructions, refer to the Pervasive.SQL V8.1 documentation.

Step Action
Installing Platinum for Windows 5.3 Client:
1 If you didn’t install the client version of Pervasive.SQL V8.1 and are only install-
ing the PFW client, reboot your workstation and close any Windows applications
that may start during startup, including TSR’s, screen savers, and virus scanners.
The reboot ensures that all DLLs have been properly unloaded.
2 Run the client installation program from each client workstation as follows
Locate the \\PLATINUM\PFWCLIEN directory on the server and run Setup.exe.

For example (where M represents your server drive):
M:\PLATINUM\PFWCLIEN\SETUP.EXE
Note: The client installation can also be run from the PFW 5.3 installation
CD. For example (where E represents your CD drive):
E:\PLATINUM\PFWCLIEN\SETUP.EXE
3 Read the instructions in the Platinum for Windows Client Setup window.
Click Next.

Step Action
4 Read the Licensing agreement.
Click Yes to accept the terms.

5 To personalize this copy of Platinum for Windows, enter your user name and
company name:
Click Next.

Step Action
6 Select the product you want to install (if you are installing BatchMasterPFW,
select ONLY the BatchMasterPFW Client, it is not necessary to install both
clients), the location for the installation, and review the required disk space. In
order to run a PAS on any workstation, the client must be installed.
You must install to a directory below the root as follows:
C:\PFW
The Platinum for Windows client program files and the Pervasive.SQL V8.1
client files should be located on the same drive.
Click Next.

Step Action
7 Specify the program folder where you want the Platinum for Windows applica-
tion icons to appear.
Click Next.
8 Review the current settings and click Next.
9 The system displays a progress indicator as the necessary PFW files are installed.

Step Action
10 In the Platinum for Windows Client Options window, specify the following:
Option Description
Server Path Specify the drive and directory on the network file
server where the Platinum for Windows network files
were installed.
Display Reserved Optional. Makes reserved fields available on certain
Fields processing windows.
Display Login Name If you select this option, the login name of the last user
of Last User is automatically displayed in the PFW Login window
the next time you run PFW.
Create Shortcut for Select this to create a shortcut on this client machine
PAS which starts a PAS.
Click OK to continue.

Step Action
11 The Setup Complete window appears.
If prompted, Select to reboot your System. Click Finish.
Repeat these steps for each Platinum for Windows client

workstation.
Pervasive.SQL V8.1 Client Settings

After client installations are complete, you will need to change
the Pervasive.SQL V8.1 local client settings. Settings must be
modified while seated at the client workstation. Never make
the following changes on the server. The client settings are
also set by using the Configuration Utility located within the
Pervasive Control Center.

Verify the machine name shown in the namespace is the local

client machine.
Category Name Setting Name Value to be set

Communication Enable Auto On
Protocols Reconnect
Application Splash Screen off (You may
Characteristics want to set this to
On for trouble
shooting.)
To apply new settings, click the ! button, or do the following:
1 Click Action
2 Choose Exit
3 Choose Yes
The Pervasive.SQL V8.1 services must be stopped then

restarted before the new settings will take effect.
Files Updated by Platinum for Windows Installation

Description Installation of Platinum for Windows 5.3 may update some
files in your local \WINNT \SYSTEM32 (Microsoft Windows
NT, XP, or 2000) directory. It may also add or update some
OLE DLL files to versions required by Platinum for Windows
5.3.

Platinum for Windows on the Desktop

Description During client installation, the following shortcut may be added
to your desktop if the option is selected:
Additionally, during the client setup, you can optionally add a

shortcut for a Process Application Server (PAS). If you select
this option, the following shortcut displays on your desktop:
The System Administrator can safely delete the shortcut if it is

not desired on a client workstation. It can be re-added at any
time following the usual Windows procedures for adding a
shortcut.
Start menu When you install Platinum for Windows, the following items
are placed in the Programs folder on the Start menu:

Installing MDAC
Installing MDAC
Background Microsoft Data Access Component (MDAC), version 2.5,

must be installed to facilitate repository access. Many
centralized configurations are accessed via MDAC.
Note: FRx Desktop requires MDAC version 2.8 and can be

installed from the FRx installation CD. However, prior to
installing version 2.8, make sure that MDAC version 2.5
already exists.
Where to install You must install MDAC 2.5 at each client workstation where
MDAC you want to run PFW 5.3.
MDAC must be installed on the workstation’s local drive
Note: Windows 2000 or XP operating systems include MDAC

in their configuration. It is not necessary to run the MDAC
installation on machines running these operating systems.
Procedure Follow these steps to install MDAC.
Step Action
1 Close all Windows applications, including all TSRs,
screen savers, and virus scanners.
2 Run the installation setup program as follows (where C
represents the drive on the client where the \PFW
directory resides):
C:\PFW\MDAC_TYP.EXE
3 Read the license information in the Software License
Agreement window, click Yes to Accept, and click
Next to continue the installation.
4 As the installation proceeds, the system displays a
progress indicator. Once complete, click Next to
continue the installation.

5 When the setup is complete, click Finish.

6 Repeat steps 1 through 5 above at each Platinum for
Windows client workstation.

Installing Acrobat Reader
Installing Acrobat Reader
Overview
Background To enable a user to view the online user’s guides, Acrobat
Reader must be installed at the client workstation. Acrobat
Reader version 5.0 is provided as part of the Platinum for
Windows installation. Unless you already have the most
current version installed, you should install this upgrade.
You can distribute Reader, register the program, or purchase

additional Adobe software as desired. Instructions on using
Reader to view online documents is provided in the System
Basics User’s Guide.
Where to install the You must install Acrobat Reader at each client workstation
Reader where you want to access online user’s guides.
Acrobat Reader should be installed on the workstation’s local

drive.
How to Install Acrobat Reader

Before you begin If you have installed a prior version of Acrobat Reader it is
recommended that you uninstall it prior to installing Acrobat
Reader version 5.0.
Description This procedure:
• Updates/adds the required Adobe Type Manager files to

the client workstation
• Creates Acrobat Reader program group on the client

desktop

Procedure Follow these steps to install Acrobat Reader files:
Step Action
1 Close all Windows applications, including all TSRs,
screen savers, and virus scanners.
2 Run the Reader installation setup program by typing
the following: (where M represents the network server
drive where your PFW Server is installed)
M:\PLATINUM\ACRCLIEN\AR500ENU.EXE
3 Read the information in the Acrobat Reader 5.0 Setup

window then click Next.
4 Read the license information in the Software License
Agreement window, click Accept to continue the
installation.
5 In the Choose Destination Location window, if you
want to install Reader to a path other than the default,
type in the drive and directory path where you want to
install Reader, and click Next.
6 As the installation proceeds, the system displays a
progress indicator.
Note: If a version of Adobe Type Manager (ATM)

prior to version 3.x was previously installed on your
computer, a message may appear requesting permis-
sion to update portions of your ATM to the latest ver-
sion. Choose to continue the installation; the partial
ATM installation ensures the online documents will
appear as designed, and will not affect how your ATM
works.
7 When the setup is complete, click Ok.
8 Repeat steps 1 through 7 above at each Platinum for
Windows client workstation.

Post Installation for All Versions
Overview
Description After the installation is complete, please review the following.
These issues are important, regardless of the version that you
have upgraded from.
In this section The following topics are discussed in this section:
Topic Page
Additional Steps When Installing to a New Drive 149
Defining the Process Application Server (PAS) 151
Additional Steps When Installing to a New Drive

Description If you installed PFW 5.3 on a new drive on the network file
server, use the following steps to complete the installation.
Note: For ease of discussion, the prior PFW version drive will
be referred to as drive O: while the new PFW 5.3 drive will be
referred to as M:.

Converting Custom You may have custom menus and/or tabs in Platinum for
Menu and Tabs Windows (this excludes BatchMasterPFW customizations)
that you have designed using Customization Workbench and
want to move these menus forward into PFW 5.3.
Step Action
1 To preserve customized menus and tabs, do the
following:
Step Action
1 On the PFW 5.3 drive (M:), add a new directory
in the N:\Platinum\PFWRes directory named
Upgrade (new directory
M:\Platinum\PFWRes\Upgrade).
2 On the PFW 5.3 drive (M:), copy the
M:\Platinum\PFWRes\MASTER\UTMID.SRF
and UTML.SRF files to the new
M:\Platinum\PFWRes\Upgrade directory.
3 From the Prior PFW version drive (O:), copy the
O:\Platinum\PFWRes\MASTER\UTMID.SRF
and UTML.SRF files into the
M:\Platinum\PFWRes\MASTER directory.
4 Login to PFW 5.3 and the menu upgrade wizard
is automatically triggered.
2 Login as Admin and add your companies, making sure to

initialize the appropriate applications for each company.
Remember to enter the new server drive (in our example,
M:) in the Drive Specification.
Note: Make sure to use the same company key.

3 Copy each company’s data from the old drive into the
new one.
4 The company data is now ready to convert.

Bringing forward You can bring forward all user groups and users previously
User Groups and defined in prior versions of PFW. To accomplish this, do the
User following:
Step Action
1 Copy only the files (not the sub-directories) from the
old O:\Platinum\PFWAdmin directory into the new
N:\Platinum\PFWAdmin directory.
2 Login as Admin, go to User Setup and modify each
user, adding new security features. You may be
prompted to run the Security Data Conversion Wizard
prior to making the changes.
Note: Running the Security Data Conversion
wizard is only necessary when bringing for-
ward User Groups and Users. To run the wiz-
ard, login as Admin, go to Security Data
Conversion, and select Finish to convert the
PFWAdmin files.
When you click Finish, a user directory is created on

the new drive.
3 Also, in the User Setup, each PAS that you will be
using needs to be refreshed. Make sure that you
change the drive letter for each PAS to reflect your
new drive mapping.
Defining the Process Application Server (PAS)

Introduction The Process Application Server (PAS) is a Windows process.
A specific procedure is required to establish a PAS or multiple
PAS’s to run on the Windows Server or workstation computer
before a PAS session can be launched. Depending on the
volume of network traffic, number of users, and type of
computer, several PAS sessions could be running
simultaneously on the server computer.

Note: Be sure to uninstall a PAS(s) if it is not registered. The

existence of an unregistered PAS causes the system to leave all
remote submission features on the Report Routing tab. If a
report is submitted remotely to a queue with an unregistered
PAS, the report is never created and remains with a In Progress
status.
Windows Server A Windows server configurations could include the following:

configurations
• Windows Server as the file server running an application
server.
• Single or multiple workstations connected to a Windows

2003/2000 Server as the file server.
Note: Running a PAS(s) on the Windows Server will impact

network performance.
Prerequisites To run a PAS on any machine (client or server), the PFW

Client must be installed. During the client installation, a
shortcut for launching the PAS can be added to the client
machine’s desktop. If this step was missed, use the following
steps to add the shortcut to the desktop.
Creating a Shortcut to Launch the PAS

The Program Filename, Window Title, and Startup Directory
will change based on your preferences.
1. Right mouse click on the desktop.
2. Select NEW then select Shortcut.
3. Enter the Program Filename. For example, the entry would
be (where x is the drive where Platinum is installed):
x:\PLATINUM\SMUDSPCH.EXE
4. Then name the Shortcut. For example:
Posting Server
You can then create as many Shortcuts as you need and place
them on the Desktop or use the Taskbar options to place them
in Program groups within the Start menu.

Additionally, you should have set up all Companies, Queues,

Users, and PAS users using the appropriate wizards within
PFW. If you have not done this, please do so before continuing.
The procedure for this setup is provided in the System
Management User’s Guide.
PAS Automation To load, login, and minimize a PAS from an icon, enter the
following target when creating the shortcut (where x: is the
network drive where PFW is installed):
x:\PLATINUM\SMUDSPCH /name <PAS name> /password <PAS
password>
For example:
x:\PLATINUM\SMUDSPCH.EXE /name PAS1 /password MASTER
The PAS name and password are case sensitive. The password
may be optional, based on how Admin created the PAS user. If
so, the target command would be:
x:\PLATINUM\SMUDSPCH.EXE /name PAS1
If the command is incorrect, the following error message

displays directing you to the problem area.

Other Security
considerations Using the NTFS file system will allow greater resolution in
assigning security than using the FAT system. This will allow
assigning security to the file level. But using file-level security
will cause Platinum for Windows errors. The preferred method
is to use the Platinum built-in security features, and to only use
the NTFS security to completely restrict users from accessing
the \PLATINUM directory.
Sharing Drives
When the client connects to the server volume where Platinum
for Windows is installed, the volume must be shared from the
root of the drive. This is necessary because PFW will build a
drive path for creating files assuming Platinum is located the
first level off the root.
Error 484 in If you receive this error when running a report, add a printer to
QMReport when the client workstation where the error occurred. Before you
printer is not can run reports, listings, or posting programs from a client
defined on Client workstation, a printer must be defined in Microsoft. This can
be the default printer, a local printer, or a network printer.
Next Step
Description Once the installation process is complete, please proceed to
“Before Processing in PFW Version 5.3” on page 97 for

Appendix C
Crystal Reports and PFW 5.3
Crystal Reports and PFW 5.3 Chapter 8
Overview
Description This appendix contains several known issues between the Crystal
Reports product and Platinum for Windows or BatchMasterPFW.
The first issue has changed in version 5.3. The remaining issues
will be addressed in future releases of PFW or Crystal reports.

APPENDIX C
Issues
Overview
Description The following section discusses known issues of the Crystal
Reports product used in conjunction with Platinum for Windows
or BatchMasterPFW.
• Default Platinum report files that include posting routines
cannot be recreated because these routines will fail with the
new report file. There may, however, be a third-party product
which can accomplish the desire result.
• In default Platinum report files, fields may not be moved into
different report sections (i.e., from detail to group, or from
one group number to another) because the table linking
becomes corrupted.
• Fields from the ARdeflts, ARprctbl, APdeflts, APaltadd, and
JClvlunt tables that have null values will not pull data into
custom Crystal Reports because of Crystal and Btrieve driver
limitations.
• Default Platinum report files that are customized should
retain their default report name and be saved in a Custom
folder, a sub-folder to Master or the appropriate company
directory. The Custom folders need to be created manually.
• New Crystal Report files created for Platinum should be
saved in the Master folder, a sub-folder to PFWRes
(\Platinum\PFWRes\Master)
• The Preview option is not available when editing any PFW
report in Crystal. This is because the associated MDB/TTX
file has not been created. To Preview your changes you must
save the report and run the associated PFW menu option.
Formatting Issues Some reports need to be exported to Excel using Excel

(Extended). If you export a report that is unsuccessful or corrupt
when opened in Excel, try using the Excel (Extended) format.
The extended version of Excel allows for the complicated report
layout and sub-reports that are often found in PFW.

Issues
Creating Custom You can customize existing Crystal reports and restrict these
Reports by new custom reports to a specific company or companies. To do
Company this, you must add the new report file (*.RPT) to a \CUSTOM
directory in a company’s directory. When that report is run
from the Business Desktop in PFW, the system looks first in
the \\Platinum\Company name\CUSTOM directory for the
correct *.RPT file. If it is found, that is the report format used
to generate the report.
If the*.RPT file is not found in the company’s custom

directory, PFW then checks the
\\PLATINUM\PFWRES\MASTER\CUSTOM directory. If it
is found, that is the report format used to generate the report.
Finally, if the *.RPT file is not found in the

\PFWRES\MASTER\CUSTOM directory, the report in the
\PFWRES\MASTER directory is used to run the report.
This feature is available throughout the PFW Financial suite,

however, in the BatchMasterPFW suite, this functionality is
limited to the following menu items:
Application Type Menu Item

Formula Listing Boilerplate Listing
Formula Class Listing
Formula Line Item Listing
Formula Master Listing
Formula Status Listing
Labor/Additional Cost
Listing
Overhead Cost Listing
Q/C Test Description List-
ing
Q/C Test Target Values
Listing
Revision History Listing

APPENDIX C

Formula Report Formula Class Report
Formula History Report
Formula Key / Descrip-
tion Report
Formula Status Report
Intermediates Report
Obsolete Formulas Report
Inventory Listing Container Specification
Listing
Customer Listing
Finished Good Specifica-
tion Listing
Hazard, Material Safety
Information
Hazard, Occupational
Exposure Limits
Hazard, Print Range Spec-
ifications
Hazard, SARA Tier I / II
Tracking
Hazard, Type Description
Hazard, Type Print Crite-
ria
Item Location Listing
Item Master Listing
Lot History Listing
Period Summary Listing
Physical Count Listing
Q/C Result Listing

Issues

Inventory Listing Q/C Target Value Listing
Q/C Test Listing
Status Listing
Transaction Cost Listing
Unposted Transaction
Listing
Print & Post Print and Post Distribution
to GL
Report Analysis Report
Gross Profit Report
In Stock Lot Number
Report
Item Information Report
Lot Expiration Report
Price List Report
Sold Lot Number Report
Labeling Listing Template Item Listing
Template Master Listing
Report Master Template Report
MSDS Listing BP Master Description
Listing
BP Paragraph Master List-
ing
BP Paragraph Override
Listing
Customer History Listing
Master Format Descrip-
tion Listing
MSDS Master Listing

APPENDIX C

MSDS Listing Schedule Listing
Supply BP Formula Class
Listing
Supply BP Formula List-
ing
Supply BP Material Class
Listing
Supply BP Material Haz-
ard Type Listing
Supply BP Material List-
ing
Supply BP Template List-
ing
Report BP Where Used In Over-
ride
Order Entry Listing Bill of Lading Inv. Info
Listing
Bill of Lading Ship To
Info Listing
Contract Price Listing
Customer Item Key List-
ing
Customer Listing
Customer Salesperson
Listing
Lot Number Listing
Price Table 1 Listing

Issues

Order Entry Listing Price Table 5 Listing
Sales Order History List-
ing
Salesperson Class Desc.
Listing
Salesperson Class/
Address Listing
Report Inventory Commitment
Report
Laboratory Report Physical Properties Search
Report
MRP Report MRP Detail Report
MRP Report
Production Listing Bill Of Materials Listing
Byproduct Listing
Finished Goods Listing
Formula Line Items List-
ing
History, Bill Of Material
History, Byproduct
History, Finished Goods
History, Formula Line
Items
History, Lot Numbers
History, Production Mas-
ters
History, Q/C Results
History, Transactions
Lot Numbers Listing

APPENDIX C

Production Listing Production Master Listing
Q/C Results Listing
Responsibility Listing
Scheduling Listing
Report Batch In Process Report
Committed Batch Report
Container Where Used In
Process Report
Finished Goods In Process
Report
Material Variance Report
Material Where Used In
Process Report
Production Cost Summary
Report
Production History Report
(Summary)
Production Master Report
Schedule Report
Purchasing Listing Carrying Cost Listing
Contract Listing
Line Item History Listing
Lot Number Listing
Purchase Order History
Listing
Q/C Lot Number Result
Listing
Recurring Cycle Listing
Responsibility Listing

Issues

Purchasing Listing Schedule Listing
Vendor Lead Time/Quote
Listing
Vendor Listing
Report Accrued Receipt Report
Approved Vendor Report
Contract Report
Expected Delivery Report
Inventory Commitment
Report
Item/Vendor Lead Time
Analysis Report
Item/Vendor Performance
Analysis Report
Open Order Report
Overdue Order Report
Purchase History Report
Requisition Report
Vendor/Item Lead Time
Analysis Report
Vendor/Item Performance
Analysis Report

APPENDIX C

Index
A E
Acrobat Reader viii, 147 Edit list 101
Automatic data conversion enhancements
notification to perform 75 Citrix printing 30
PFW 77 customer notes 30
running PFW Auto Data Conversion double byte support 29
wizard 82 lot sorting 30
running PFW Upgrade wizard 78
F
B Formatting Issues 156
Backing up 35, 41, 51
backing up files 59
I
C initializing data files 68
Installation
Citrix printing 30 Acrobat Reader 147
Configuration files 95 CD-ROM 43, 64, 125
copying data files 69 client workstation 135
Creating Custom Reports by Company 157
customer notes 30
L
D Language translation 1, 36, 42, 53
licensing
data 4.8a and earlier 61
copying files 69 lot numbers
initializing data 68 sorting by 30
Data conversion using 60
performing 75
data dictionary files (DDF)
4.8a and earlier 62 M
decimals
4.8a and earlier 61 Microsoft Windows NT server
Demonstration companies installation with Pervasive.SQL 127
General Ledger 35, 41, 52 Multi-Currency Manager 32, 48
Documentation
online x, 147
DOS users O
warning 58
double byte support 29 On account payments 102
Drive designations 135
duplicate files
4.8a and earlier 61
P
Parameter Conversion utility 71
path table

for upgrades vi Registration 86
Pervasive.SQL v7.0
CD-ROM 43, 64, 125
installation 127 S
PFW Upgrade wizard
overview 77 Serial/lot tracking
procedure 78 enabling 102
platforms Start menu 144
Windows 98 59
Platinum for Windows (PFW)
integration with BatchMaster 62 U
Platinum for Windows CD-ROM 43, 64, 125
Post installation procedures Uninstalling
company setup 98 applications not registered 86
enabling serial/lot tracking 102 upgrading procedures
reentering on account payments 102 copying data files 69
registration 95 initializing data files 68
reviewing Readme file 95 Parameter Conversion utility 71
running Edit list 101 versions 4.x and 5.x 67
setting up configuration files 95 Upgrading to PFW 4.8
user group setup 98 process overview 33, 40, 44, 45, 50, 57, 65
Pre-installation procedures
backing up 35, 41, 51
resetting language 36, 42, 53
V
saving existing demo data 35, 41, 52 Virtual Warehouse 32, 48
printing Virus checkers 36, 42, 53
Citrix 30
procedures. See upgrading procedures
W
R Windows 98 59
Readme files xi, 96

Chapter 1
Platinum for Windows Product Registration Form

Company Information
Company Name:________________________________________________________________________
Address Line 1: _________________________________________________________________________
Address Line 2:__________________________________________________________________________
City: _____________________________________ State/Province: _____________________________
Country: ____________________________________ Postal Code/Zip: _____________________________
Contact Name: __________________________________ Phone: __________________________________
Contact email: ____________________________________ Contact fax: ____________________________
Best Reseller
Name: _________________________________________________________________________________
City: _______________________________________________ State/Province: _______________________
Phone: _________________________________________________________________________________
Important: Registration, support, updates, and access to the application will not be granted unless your
software is registered within 30 days after installation.
Initialization Code: _________________________ Site Identification Number: _______________________
UNLOCK CODE: ________________________________________________________________________
FAX Transmittal # of pages:

To: Best Software Registration Department At: (949)753-1593

PFW 5.3 Upgrade Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

PFW 5.3 Upgrade Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Upgrade Guide 5.

This document is also protected by copyright, and may not be reproduced or

© 1984-2004 Best Software, Inc. All rights reserved.

Platinum is a trademark licensed to and a product produced by Best. Best is a

This guide provides the following:

• Features included in PFW 5.3

In this section This section provides information on the following topics:

Upgrade Guide Version 5.3 v

DOS 2.x 3.2 to 4.6x to 5.02 to 5.3 N/A

vi Upgrade Guide Version 5.3

*Version number subject to change.

Upgrade Guide Version 5.3 vii

Platinum for Windows

Upgrade to: Perform:

• Pre-PFW 4.6 Upgrade Tasks

Note: If you do not have Acrobat Reader installed, you may

viii Upgrade Guide Version 5.3

Upgrade to: Ver. 3.2 to 4.6x to Upgrade to:

Upgrade to: Upgrade to:

Upgrade Guide Version 5.3 ix

PFW 5.3 Documentation Set

Hardcopy Your Platinum for Windows kit contains the following

The System Management User’s Guide contains registration

This guide contains the steps required to upgrade to the new

System Basics Production

x Upgrade Guide Version 5.3

You may also open the README files by opening the

Miscellaneous The following documents are also provided online as

• Database Reference Guides for version 5.3

Upgrade Guide Version 5.3 xi

xii Upgrade Guide Version 5.3

In addition to the enhancements that follow, many Problem

Language Preservation of language translation is not covered in this

In this section This section contains the following topics:

Upgrade Guide Version 5.3 1

What’s New in 5.3

Business Desktop The NEW Business Desktop is a powerful alternative to your

The Business Desktop is designed to improve workflow. You

The main page of your Business Desktop also provides

2 Upgrade Guide Version 5.3

Improved Security Due to growing concerns about compliance with regulations

Many of you will be excited about the User Group Security

Business Insights Business Insights consolidates critical information and enables

Information is easily accessible and can be displayed in a

Business Insights was introduced in December, 2003, and is

Upgrade Guide Version 5.3 3

Enhanced Usability The following enhancements have been added to improve

Numeric Search Capability

4 Upgrade Guide Version 5.3

The customer account that is active in Customer File

Drop Down List Boxes

Platinum for Windows

Upgrade Guide Version 5.3 5

Purge Inventory Transaction History

Purge Chart of Accounts

Purge GL Transaction History

Enhanced Inter- With an abundant amount of Inter-Company transactions,

In response to several requests, the Vendor Invoice Number is

6 Upgrade Guide Version 5.3

• Increased Processing Speed

Simplified No longer do you need to install PFW and BatchMasterPFW

Furthermore, the Chem and Food demonstration companies

The following utilities can be easily accessed from the Admin

• Auto Data Conversion