home *** CD-ROM | disk | FTP | other *** search
- DATA REPORT GENERATOR
- Document Name: Readme.XT
- Document Date: February 8,1989
- ================================
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Version: PLT-5
-
-
- XTRIEVE (Version 3.0)
-
- 1) KNOWN PROBLEMS AND WORK AROUNDS:
-
- Two problems have been defined in the Xtrieve System. We offer
- work-arounds for both of these problems.
-
- Problem : Transferring data files out to SDF files produces asterisks in
- the BFLOAT fields.
- Solution: When fielding the BFLOAT fields, define a "user-defined" numeric
- field. Specify its value to be equal to the BFLOAT data field you
- wish to transfer.
-
- Problem : Some users wish to add new index fields to data files for
- special Xtrieve reporting.
- 1) Make a backup of your data!
- 2) Translate the data from the data file out to an SDF, DIF or
- Unformatted file.
- 3) Access Dictionary/Reorganize, add the new index to the
- dictionary, and Finish - Create the data file.
- 4) From DOS, copy the newly created data file from the
- \PLATINUM\XTRIEVE directory to the company data directory.
- 5) From DOS, erase the newly created data file from the
- \PLATINUM\XTRIEVE directory.
- 6) Translate the data from the temporary SDF, DIF or Unformatted
- file into the data file.
- Some users have completed this process successfully. However,
- upon accessing the Platinum System, the error message
- "Buffer too Short" occurs during the opening of the data file
- which has been enhanced.
- Solution: Perform the above process again, but add one step. When
- accessing the Dictionary, change all the existing indexes and
- the newly defined index to CASE Sensitive (YES).
-
-
-
- 2) WHAT TO DO WHEN THE VIEW DISPLAYS GARBAGE CHARACTERS IN NUMERIC FIELDS
- ----------------------------------------------------------------------
- Garbage appears while viewing numeric fields when a print mask for the
- data field is not set. Perform the following commands to set the print
- mask.
-
- From the Xtrieve Main Menu:
- VIEW
- MANAGE
- RELEASE
- DICTIONARY
- DEFAULTS
- Select the File
- Select the field displaying garbage
- MASK <Enter>
- Enter a mask of (ZZZ,ZZZ.99)
- <Enter>
-
- You may now re-define the view.
-
-
- 3) HOW TO PRINT THE DATA DICTIONARY (applies to Xtrieve version 3.0 ONLY)
- ---------------------------------
- *****
- This applies to those users with Xtrieve version 3.0 ONLY!!!
- For those users with Xtrieve verson 4.0 or greater, access the
- Xtrieve Dictionary/Print option to print the layout of a data file.
- *****
-
- The release of PLT-5b of the Data Report Generator, includes the views
- and reports necessary to print the Data Dictionary. To print the
- Dictionary, follow these steps.
-
- a) From the System Manager, select the following:
- SETUP & UTILITIES MENU
- INITIALIZE FILES
- DATA/REPORT GENERATION
-
- Initialize the following files:
- FILE MAP VIEW
- FILE MAP REPORT
- FILE INDEX VIEW
- FILE INDEX REPORT
-
- b) From the Data Report Generator option:
- VIEW
- MANAGE
- RECALL
- FILEMAP
-
- You may now browse the file mapping.
- To report a range of data files, you may invoke a RESTRICT
- on the XF$NAME field to BEGIN WITH the data file name you
- wish to view.
-
- To access the pre-saved report, <ESC> back to the XTRIEVE Main Menu.
- Select the following:
- REPORT
- MANAGE
- RECALL
- FILEMAP
- PRINT
- The report will print on eight and a half by eleven inch paper.
-
-
- 4) HOW TO CHANGE A PRE-SAVED COMMAND FILE TO AN ASCII FILE
- --------------------------------------------------------
- The Xtrieve system has the capability to edit and/or view a COMMAND file.
- To do this, you must convert the COMMAND file to an ASCII file. You
- may edit and view the ASCII file with any word processor or with the
- EDLIN command.
-
- If you execute Xtrieve from Platinum, the COMMAND files are stored in the
- company data directory. The MAKE_XTA file is located in the
- \PLATINUM\XTRIEVE directory.
-
- This example shows you how to change the FILEIX.XTC command file
- to a FILEIX.XTA ASCII file. Execute from DOS the following command,
- from the \PLATINUM\XTRIEVE directory.
-
- XCFP \PLATINUM\COMPANY\FILEIX.XTC \PLATINUM\COMPANY\FILEIX.XTA
-
- The XCFP file is the Xtrieve command file processor. It pays attention
- to the file extensions, XTC indicates a COMMAND file and XTA indicates an
- ASCII file. The order of the parameters determines whether you will be
- converting from a COMMAND file to an ASCII file or converting an ASCII
- file to a COMMAND file.
-
- If you have edited the XTA file and wish to convert it back to a COMMAND
- file, execute the following command.
-
- XCFP \PLATINUM\COMPANY\FILEIX.XTA \PLATINUM\COMPANY\FILEIX.XTC
-
-
- 5) HOW TO CHANGE A PRE-SAVED VIEW
- ------------------------------
- The Xtrieve system has the capability to view and edit a VIEW. To do this,
- you must convert the VIEW file to an ASCII file. You may edit and view
- the ASCII file with any word processor or with the EDLIN command.
-
- If you execute Xtrieve from Platinum, the VIEW files are stored in the
- company data directory. The XCFP file is located in the
- \PLATINUM\XTRIEVE directory.
-
- This example shows you how to change the FILEMAP.VTB command file
- to a FILEMAP.XTA ASCII file. Execute from DOS the following command,
- from the \PLATINUM\XTRIEVE directory.
-
- MAKE_XTA /V:\PLATINUM\COMPANY\FILEMAP.VTB /O:\PLATINUM\COMPANY\FILEMAP.XTA
-
- Refer to your Xtrieve manual for the syntax of the ASCII file. If you
- edit the ASCII file, you can convert the ASCII file back to the view file
- by performing the following.
-
- 1) Convert the ASCII file to a COMMAND file by executing the following
- command from DOS, in the \PLATINUM\XTRIEVE directory.
-
- XCFP \PLATINUM\COMPANY\FILEMAP.XTA \PLATINUM\COMPANY\FILEMAP.XTC
-
- 2) From the Xtrieve Main Menu execute the following commands:
- COMMANDS
- PLAY
- FILEMAP
- VIEW
- MANAGE
- STORE
- FILEMAP
-
-
- 6) HOW TO INITIALIZE ARINVHST OR IVBOM FILES FOR USE IN ADVANCED FEATURES:
- -----------------------------------------------------------------------
- The following is an example of how to initialize the IVBOM file. It may
- be used as an example to initialize other data files for use in adding
- indexes to data files or for use in the advanced features.
-
- From the Data Report Generator, select the following:
- DICTIONARY
- REORGANIZE
- IVBOM -BILL OF MTL
- REPLACE? <yes>
- LOCATION <Enter>
- FILE <Enter>
- Field Type Size <Esc>
- COMPLETE
- INDEXES <Esc>
- COMPLETE
- FINISHED - CREATE
-
- This will create the file in the \PLATINUM\XTRIEVE directory.
- From DOS, copy the file into the \PLATINUM\CompanyKey directory
- From DOS, erase the file from the \PLATINUM\XTRIEVE directory.
-
-
-
- 7) HOW TO ACCESS THE GENERAL LEDGER YEAR BALANCES FILE:
- ----------------------------------------------------
- The following example shows you how to read the Year Balances for the
- year 1988.
-
- From the Xtrieve Main Menu:
- DICTIONARY
- REORGANIZE
- GLYRXX -YR BALANCES
- REPLACE? <Yes>
- LOCATION change GLYRXX to read GLYR88 <Enter>
- FILE <Enter>
- Field Type Size <Esc>
- COMPLETE
- INDEXES <Esc>
- COMPLETE
- FINISHED - DON'T CREATE
- Now you may define the VIEW to access the fields you wish.
-
-
-
- 8) HOW TO PLACE THE BALANCES IN PERIOD 6 INTO PERIOD ZERO IN THE GENERAL
- LEDGER YEAR BALANCES FILE.
- ---------------------------------------------------------------------
- In the event a user enters the opening balances for the Balance Sheet in
- period six instead of period zero, Xtrieve can be used to quickly
- resolve this problem by executing the following commands.
-
- From the Xtrieve Main Menu:
- VIEW
- FILE
- GLYRXX -YR BALANCES
- FIELD
- ADD
- DEFAULTS? <yes>
-
- Add the following fields to the view by
- using the arrow keys to place the cursor
- on the appropriate field and pressing <Enter>.
-
- ACT O/BAL PD0,GLYRxx
- ACT BAL PD6, GLYRxx
-
- Add a user-defined field which will be used
- to transfer the balances from period 6 to
- period 0. A second user-defined field will
- be set to zero. This field will be used to
- set the balances in period number six to zeros.
-
- <End> to access the USER-DEFINED field
- <Enter> to select
- BFLOAT
- Size: 8
- MASK enter ZZZ,ZZZ,ZZZ.99
- OPERAND <down arrow> to ACT BAL PD6, GLYRxx
- <Enter>
- COMPLETE
- HEADING: PERIOD 6 BALANCES
- OFFSET: 75 <Enter>
-
- <End> to access the USER-DEFINED field
- <Enter> to select
- <arrow> to BFLOAT <Enter>
- Size: type 8 and <Enter>
- MASK enter ZZZ,ZZZ,ZZZ.99
- OPERAND <End> to CONSTANT
- <Enter>
- <Enter> to set the field column to zero
-
- <Esc> to the View Menu
- RESTRICT
- NEW
- ACCT NO., GLYRxx
- LESS THAN 4070 which is the INS account
- in the DEMO data
-
- <Esc> to the View Menu
- BROWSE to verify the account to be updated
-
- <Esc> to View Menu
- EDIT
- MODIFY ALL
- ACT O/BAL PD0,GLYRxx
- to PERIOD 6 BALANCES
- ARE YOU SURE? <yes>
-
- MODIFY ALL
- ACT BAL PD6, GLYRxx
- to CLEAR BALANCES
- ARE YOU SURE? <yes>
-
-
- 9) HOW TO SET UP PRINT FORMATS FOR DATE FIELDS:
- -------------------------------------------
- To assign a print format to date fields, you must combine the
- two data fields, the month and day fields and the year fields. You must
- also change the data type from string to numeric. The following example
- tells you how to change the string field type to a numeric field
- type for the A/P Bank Book Interface file (APBB) and assign a mask on the
- date field.
-
- To change the data type and combine the fields:
- DICTIONARY
- REORGANIZE
- APBB -BB_INTERFAC
- REPLACE? <Yes>
- LOCATION <Enter>
- FILE <Enter>
- Field Type Size
- <Down arrow> to the CHK DATE mmdd, APPBB
- change the data field to CHK DATE mmddyy,APBB
- <Enter> leaves cursor on STRING then
- <Down arrow> to NUMERIC <Enter>
- SIZE type 6 and <Enter>
- DECIMAL PLACES? type 0 and <Enter>
- <Esc>
- REMOVE
- CHK DATE yy, APBB <Enter>
- <Esc>
- COMPLETE
- INDEXES <Esc>
- COMPLETE
- FINISHED - DON'T CREATE
-
- The data type for the date fields have been changed from
- string to numeric. The dictionary is now prepared to
- define a print mask. <Esc> to the Xtrieve Main Menu and
- perform the following:
-
- DICTIONARY
- DEFAULTS
- APBB -BB_INTERFAC
- <Down arrow> to CHK DATE mmddyy, APBB
- <Enter>
- MASK
- ZZ/ZZ/ZZ <Enter>
-
-
- 10) HOW TO INCREASE THE BASE PRICE IN THE ITEM LOCATION FILE BY 10%
- ---------------------------------------------------------------
- Following is an example of how to increase the base prices of all
- the Item Location records by 10%. This example uses a "virtual field"
- to update fields in the data base.
-
- From the Xtrieve Main Menu:
- VIEW
- FILE
- IVLOC -ITEM LOCATION
- FIELD
- ADD
- DEFAULTS? <yes>
-
- Add the following fields to the view by
- using the arrow keys to place the cursor
- on the appropriate field and pressing <Enter>.
-
- ITEM KEY, IVLOC
- LOCN KEY, IVLOC
- BASE PRICE, IVLOC
-
- Add a user-defined field which will be used
- to calculate the base price+10%. This
- "virtual" field will be used to update the
- base price.
-
- <End> to access the USER-DEFINED field
- <Enter> to select
- BFLOAT
- Size: type 8 and <Enter>
- MASK enter ZZZ,ZZZ.99
- (you may add decimal places to the right
- of the decimal point typing nines)
- OPERAND select BASE PRICE, IVLOC
- TIMES
- <End> to access CONSTANT
- <Enter> to select
- CONSTANT type 1.1 and <Enter>
- COMPLETE
- HEADING: Increased price <Enter>
- OFFSET: 54 <Enter>
-
- You may BROWSE to view the columns. The
- increased price column will display the new
- price.
- You may apply a RESTRICT if you wish
- to increase the BASE PRICE on a range of items.
- After you have verified the increase, you
- can update the data base by performing the
- following commands from the VIEW menu.
-
- EDIT
- MODIFY ALL
- BASE PRICE, IVLOC
- TO Increased Price
- ARE YOU SURE? <yes>
-
- The above commands will replace the BASE PRICE
- with the value in the INCREASED PRICE field.
-
-
-
- 9) COMMON XTRIEVE MISTAKES
- -----------------------
- Creating Btrieve data files from Xtrieve:
- When accessing Dictionary/Reorganize, the final options are
- Finished Don't Create, Finished Create, Review, or Abort. If you
- select Finish Create, Xtrieve will create the data file in the
- \PLATINUM\XTRIEVE directory. Platinum accesses Btrieve data files
- only from the \PLATINUM\CompanyKey directory. However, Xtrieve
- will look for the Btrieve data file first in the \PLATINUM\XTRIEVE
- directory. If it is not found, then it will access the
- \PLATINUM\CompanyKey directory. Many users have changed indexes
- or data fields and performed the Finished Create option. Then,
- they enter Platinum and add data into the newly created data file.
- When they go back into Xtrieve to view the data entered, no records
- are found. This is because Xtrieve is accessing the
- \PLATINUM\XTRIEVE directory and Platinum is adding to the data
- file located in the \PLATINUM\CompanyKey directory.
-
- Solution:
- After creating the Btrieve data file from Xtrieve, access DOS
- and copy the newly created data file into the \PLATINUM\CompanyKey
- directory. Then, erase the newly created data file out of the
- \PLATINUM\XTRIEVE directory.
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Version: PLT 5b
- Date : December 15, 1987
-
- 1) CHANGES AND ADDITIONS TO THE DICTIONARY:
- ----------------------------------------
- The Xtrieve Dictionary has been altered to reflect changes in the
- following data files.
-
- OEHDR - Order Header File, New Record Length = 530
- The following data fields were added to the end of the
- record.
-
- Ship Date = pos 500, len 6, String
- Spare = pos 501, len 1, String
- Invoice # = pos 507, len 5, String
- Invoice Date = pos 512, len 6, String
- Aging Date = pos 518, len 6, String
-
- ARHDR - Invoic_Alt1, Record length = 515
- The invoice number and invoice date under which the
- invoice was printed have been added to the dictionary.
-
- ARLIN - Invoic_Alt2, New Record Length =110
- The cost field, used to accommodate the Cost Entry advanced
- feature, has been added to the dictionary.
-
- ARLINH- ARCOST, New Record Length =120
- The cost field, used to accommodate the Cost Entry
- advanced feature, has been added to the dictionary.
- This should only be used if you have invoked the Cost
- Entry advanced feature.
-
- BBDIST- Distribution to G/L File, New Record Length= 65
- The distribution description field has been added to the Dictionary.
-
- ARSERIAL- Serial Number File, New Record Length= 80
- The vendor and purchase information fields have been added to the
- Dictionary.
-
- PRTIMCRD - Time Card File, New Record Length= 80
- The Job Cost interface fields have been added to the Dictionary.
-
- PRDEPART - Department File, New Record Length= 255
- The Job Cost interface fields have been added to the Dictionary.
-
- PREMPMST - SCRN 5 OF 6, Employee Master File, record length= 1200
- A padding field to accommodate screen 3 of 6 was added to the
- Dictionary.
-
- PREMPMST - SCRN 6 of 6, Employee Master File, record length = 1200
- The weeks worked field has been redefined as a Bfloat field type.
-
- POHDR - Purchase Header File, Record Length= 550
- A spare field of 75 characters has been added to make the record
- length equal to 550.
-
- APBRANCH - Branch File, Record Length= 185
- The Company Name index path has been added to the Dictionary.
-
- ARPRICE - Price Table , Record Length= 200
- One of the quantity fields was defined as a string field. It has
- been redefined as a Bfloat data type.
-
-
- The Following data files have been made accessible.
- POSER - Purchase Order Serial No. File
- POJC - Purchase Order Job Cost Interface File
- APJC - Accounts Payable Job Cost Interface File
- APJCHOLD - Accounts Payable Retention Holding File
- IVJC - Inventory to Job Cost Transaction File
- IVJCDIST - Inventory to Job Cost Distribution to G/L File
- JC* - Job Cost System
- ARSER - Invoice Entry Serial/Lot No. File
- APALTADD - Alternate Vendor Address File
- ARINVHST - Invoice additional information offered by the
- advanced feature.
- APSER - Voucher Entry Serial/Lot No. File
- APRECUR - AP Recurring File
- GLYRXX - General Ledger Year Balances File
-
- The following data fields were changed to comply with the requirements of
- PlatForm. Those fields which are String type but contain numeric values
- are designated by the tilde (~) character in the data name field.
-
- APHDR - Voucher Entry Header File
- APJC - Voucher Entry Job Cost Interface File
- APLIN - Voucher Entry Line Item File
- ARHDR - Invoice Entry Header File
- ARLIN - Invoice Entry Line Item File
- OEHDR - Order Entry Header File
- OELIN - Order Entry Line Item File
- OETRAN - Line Item Changes File
- POHDR - Purchase Order Entry Header File
- POLIN - Purchase Order Entry Line Item File
- PRCMPDRA - Computed Payroll Ded., Red., Allowance File
- PRMNTDRA - Computed Entry Payroll Ded., Red., Allowance File
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Version: PLT-5c
- Date : September 9, 1988
-
- This version of Data/Report Generator supports Xtrieve version 4.01.
- If you have Xtrieve version 4.0 installed, please contact Novell
- Development Products Division for an upgrade to version 4.01. You must
- be running Xtrieve 4.01 to execute properly.
-
- The Data Dictionaries have been changed to support restrictions
- implied by Xtrieve 4.0.
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Version: PLT-5c
- Date : October 17, 1988
-
-
- CORRECTIONS:
- -----------
-
- 1) Corrections to Xtrieve version 4.0 and 4.01 are included on your
- Data Report Generator diskette(s). The install utility has installed
- the necessary files in the \PLATINUM\XTRIEVE directory.
-
- -----------------------
- !!!!! IMPORTANT !!!!!!
- -----------------------
- Patches for Xtrieve versions 4.01 MUST be executed.
- The patches are executed by running one of two batch files. Run
- FIX401N.bat for the Network version of Xtrieve or run FIX401S.bat for
- the Single-user version of Xtrieve. To execute these patches,
- DEBUG.COM must be available via the PATH command or it must exist
- in the \PLATINUM\XTRIEVE directory.
-
- Please verify the correct DOS version of DEBUG is installed by
- typing DEBUG and <enter> from the DOS prompt while in the
- \PLATINUM\XTRIEVE directory. If the machine responds with a dash,
- you have the correct version of DEBUG loaded. You may type "Q" and
- <enter> to quit from DEBUG. If the machine responds with,
- "Incompatible DOS version", you must install the correct version of
- DEBUG prior to executing the patches. If the batch files to execute
- the patches processed very quickly, the wrong version of DEBUG is
- loaded and the patches have not been executed. The patches take
- approximately 30-60 seconds to process.
-
- PLEASE read the ASCII files named README.BUG and README.FIX located
- in the \PLATINUM\XTRIEVE directory. These files have been supplied
- directly by the Novell Development Products Division.
-
-
- ERRORS (Xtrieve Version 4.01)
- -----------------------------
-
- "OUT OF BUFFER SPACE"
-
- This error may occur if the /F option is not set or set too high in the
- "Xtrieve Options/Switches" field of the "Data/Report Generator Start-up
- Options File Maintemance" located on the Set-up & Utilities Menu. The
- /F option defines the maximum number of fields in ALL ACTIVE views.
- Note, this also includes those views which are retained but may not
- be the current view. The /F option defaults to 255. We recommend
- setting /F:100 to relieve buffer space.
-
- REPORTS HANG
-
- The report hangs the machine. THe may be caused by the /I option not
- defined or defined too low int the "Xtrieve Options/Switches" field
- of the "Data\Report Generator Start-up Options File Maintenance" located
- on the Set-up & Utilities menu. This option specifies the maximum number
- of report elements that you can have in a single report. The default
- value for the /I option is 100. You may have to increase this value
- for a specific report.
-
-
- "XQL PRIMITIVE NOT FOUND"
-
- This error may occur if you are not running a System Manager version
- PLT-5c. You MUST be running System Manager PLT-5c when accessing
- Xtrieve 4.01 from the PLATINUM menu.
-
- This error may also occur if you are running Xtrieve version 4.0. You
- MUST be running Xtrieve version 4.01. If you have found this to be the
- case, please contact Novell Development Products Division in Austin, TX.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Version: PLT-6
- Date : February 3, 1989
-
-
- GENERAL INFORMATION
-
- Version PLT-6 is not compatible with PLT-5c or prior versions
- of the software.
-
-
- NO CONVERSION NECESSARY
-
- WHAT YOU TO NEED CHANGE TO RUN PLT-6 AFTER THE CONVERSION
-
- A) SET COMMANDS
- The SET commands are no longer used to invoke Xtrieve.
- You may remove these commands from your START.BAT and
- NETSTART.BAT files.
- B) PRE-DEFINED COMMANDS, VIEWS OR REPORTS.
- Any COMMAND, VIEWS or REPORTS defined using the following
- files will need to be changed to reflect the new file
- structures.
-
- 1. ARHDR (increased in length)
- 3. ARSERIAL (new field)
- 4. ARLINH (new field)
- 5. ARCUST (new key)
- 6. ARLIN (new field)
- 7. ARSER (new field)
- 8. ARSELECT (new fields)
- 9. ARDIST (new key)
- 10. IVTRANH (new fields)
- 11. IVTRAN (new fields)
- 12. IVDIST (new fields)
- 13. APLIN (new fields)
- 14. APLINH (new fields)
- 15. APSER (new field)
- 16. APSERIAL (new field)
- 17. POSER (new field)
- 18. OEHDR (new fields)
- 19. OELIN (new field)
- 20. OESER (new fields)
-
-