|
|
|
Technical Support Bulletin
INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY ACCOMPANY THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. The user assumes the entire risk as to the accuracy and the use of the information supplied. This information may be copied and distributed subject to the following conditions: 1)All text must be copied without modification and all pages must be included; 2)If software is included, all files on the disk(s) must be copied without modification; 3)All software included and documentation must be distributed together; and 4)This information may not be distributed for profit. All other trademarks contained herein are acknowledged. Threading Files The files included in the 4.0 release which hold the last threading number have give rise to a number of questions by third party developers as to their contents and usage. The files in question are: Accounts Receivable Last Sys Doc ID ARNEXTSY Accounts Payable Last Sys Doc ID APNEXTSY Order Entry Last Sys Doc ID OENEXTSY Purchase Order Last Sys Doc ID PONEXTSY Inventory Last Event ID INNEXTEV Last Orig Doc ID INNEXTOR Each of these Btrieve files shares a basic similarity in that it contains a single record. The record is a single 4 byte field defined as autoincrement field type. Each time a record is added to the file Btrieve will increment the value of the key. This is the next number to be used by the system. The original record in the file must then be deleted. Below are the standard steps used within Platinum to obtain the next number and update the file. Read the record This is the number assigned to the transaction being processed. Write over the record Add a new record Delete the prior record If multiple records are contained in the file they should be removed as the impact on processing are indeterminate.
|
| |||||||