This program uses a number of files to hold your information.  They consist of files listed below.

Note that for advanced users, file structure information is available for Sales.dbf, Orders.dbf, Cust_Num.dbf, Cat_no.dbf, Contact.dbf, and UserDef.dbf.

Sales.dbf. This is the main file which holds your invoices.  It includes invoice numbers, names and addresses, purchase order numbers, dates, and all the information displayed on the invoice form except for notes and products listed in the Item Area. File structure information.

Sales.dbt.  This file contains all your notes included with the invoices.

Sales.mdx is an index file which keeps the invoices ordered properly for quick access.  This file can be re-created if it is destroyed.  The first two files (Sales.dbf and Sales.dbt) can not.

Orders.dbf. This is the file that holds the information that appears in the Item Area on the Invoice screen.  It consists of quantities, catalog numbers, item descriptions and prices. File structure information.

Orders.mdx is an index file which provides rapid access to orders.dbf.  This file can be re-created if destroyed.  Orders.dbf can not.

BsetUp.dbf. This file holds all of your basic set up values.  It can be re-created if destroyed, but any information saved in the file will be lost.

Cust_Num.dbf.  This is the customer information database file.  It holds all of the information that appears on the Customer Information Screen including customer and group numbers, billing and shipping address and customer notes. File structure information.

Cust_Num.dbt.  This file contains the notes associated with each customer.

Cust_Num.mdx is an index file which provides rapid access to the customer information database.  It can be re-created if destroyed.  Cust_Num.dbf and Cust_Num.dbt, however, can not.

Cat_no.dbf is the product information database.  It holds all the information that appears on the Product Information Screen including catalog numbers, item names, cost, etc. File structure information.

Cat_no.mdx is an index file which provides rapid access to the product information database.  It can be re-created if destroyed.  Cat_no.dbf, however, can not.

Contact.dbf This is the database file that is used by the Contact Manager to hold contact information. File structure information.

Contact.mdx is an index file which provides rapid access to information in the Contact database file.  It can be re-created if destroyed.  Contact.dbf, however, can not.

Contact.dbt Contains any notes included in the Contact Manager.

ShipVia.dbf Contains the list of shipping methods.

Category.dbf Contains a list of category and prefixes.

ExchRate.dbf Contains AnyOrder's Currency Table for invoice conversions.

Profile.dbf Holds import profile values.

ImpList.dbf Holds all data from Import Replacement Tables.

Profile2.dbf Holds export profile values.

RepList.dbf Holds all data from Export Replacement Tables.

UserDef.dbf Holds User Defined Fields data. Also includes data from the Shipment Form. File structure information.

UserDef.mdx is an index file which provides rapid access to information in the User Defined Fields database file.  It can be re-created if destroyed.  UserDef.dbf, however, can not.

CodeList.dbf Holds all codes: general invoice, ad campaign, sales representatives, and terms.

CodeList.mdx is an index file which provide rapid access to CodeList.dbf

WebLinks.dbf Holds all of the information associated with on-line shipment processing.

PackSum.dbf Holds summary data for multi-package invoices

PackSum.mdx is an index file which provides access to PackSum.dbf

PackItem.dbf Hold individual records for each package of the multi-package invoice

PackItem.dbf is an index file which provides access to PackItem.dbf

Inventory.dbf Contains the inventory transaction log

Inventory.mdx is an index file which provides access to Inventory.dbf

Schedule.dbf Holds scheduling dates and reminder notes

Schedule.mdx is an index file which provides access to Schedule.dbf

Translate.dbf use to hold language translations

Inventory Files: An example is InvEnd05.dbf which holds the ending inventory levels of all of the products at the end of 2005 and any inventory which has been added during 2006.

Balance Files: An example is Bal05End.dbf which holds the balances of each of your customers at the end of 2005.  Another example is Bal05Mid.dbf which hold the balances of each of your customers at mid year 2005.

All of the files listed above (except the *.mdx files) are copied to the back-up disk whenever you do a back-up.  They are vitally important and they should not be deleted.  Some of the files listed next are temporary (created and deleted by the program as they are needed), but others are permanent and should not be deleted:

Billing.dbf.  This file is created during the billing process and holds billing names, addresses and account balances. This file can be deleted.  The program will re-create it when needed.

Billing.mdx This is the index file associated with Billing.dbf.  It can be re-created if destroyed.

SalesBil.dbf is another file created during the billing process which stores needed information for billing.dbf. If needed, this file can be deleted.  The program will re-create it when needed.

SalesBil.mdx This is the index file associated with SalesBil.dbf.  It can be re-created if destroyed.

Invent.dbf. This file is created during the inventory process and holds product names and inventory levels. It is a required file and should not be deleted.

OrderInv.dbf is another file created during the inventory process which stores needed information for invent.dbf.  It is a required file and should not be deleted.

Cat_no_2.dbf is another file created during the inventory process and is used to hold catalog numbers and products for use by Invent.dbf. It can be deleted.  The program will re-create it when needed.

BackOrd.dbf is created during the backorder processing routine.  The program will re-create it when needed.

NetLog.dbf is used to keep track of network activity. It is a required file and can not be deleted.

Labeling.dbf is used to store label, envelope and mailing list properties.  It is a required file and should not be delete.

Sales & Product Report Files. Files used for sales and product report purposes include:  InvCode.dbf, RepCode.dbf, ProdSale.dbf, ProdSale.mdx, Ad Camp, TaxRate.  These are required and can not be deleted.

MailList.dbf and MailList.txt.  These two files are created for use by other programs for producing mailing lists or mail merge letters.  They can be deleted or moved to other locations.

*.ndx files.  Several files with a .ndx extension are created.  They are temporary index files and can be deleted with no effect on the program.

The following files are created when invoice files are moved to storage.  The second set of files (Tmp files) can be deleted.  However, the first set, the main storage files, can not:

Storage Files.  When files are moved to storage, the program uses a file name that you assign to it.  Let's say that the following file name has been assigned to a group of invoices in storage: Yr01to02.  Several files are created with the Yr01to02 name.  The first file created is Yr01to02.dbf.  This file is used as an internal reference file and contains the names of all the files moved to storage and the extensions assigned to each. Additionally, the following files, each with a different extension, are created.  (Note that if any of these files are deleted, storage information will be lost).

Yr01to02.S01 The storage file equivalent to Sales.dbf

Yr01to02.S02 The storage file equivalent to Sales.dbt

Yr01to02.O01 The storage file equivalent to Orders.dbf

Yr01to02.P01 The storage file equivalent to Cat_no.dbf

Yr01to02.P02 The storage file equivalent to Cat_no.dbt

Yr01to02.C01 The storage file equivalent to Cust_Num.dbf

Yr01to02.C02 The storage file equivalent to Cust_Num.dbt

Yr01to02.U01 The storage file equivalent to UserDef.dbf

Yr01to02.B01 (…02, 03, etc.) Storage file equivalent to a Balance File, i.e. Bal02End.dbf

Yr01to02.I01 (…02, 03, etc.) Storage file equivalent to an Inventory File, i.e. InvEnd02.dbf

TmpSales, TmpOrder, TmpCat, TmpCust.  These are temporary storage files which are used when "View Storage File" is selected from the Menu Bar.  They are temporary, re-created when needed, and may be deleted.

The following are files used in the Payment Analysis function. They should not be deleted:

Payment.dbf and PayTemp.dbf.  Both of these files are used in the Payment Analysis feature, and should not be deleted.

Payment.txt. Payment.txt is a small file that holds help information for the Payment Analysis function.  It should not be deleted.

The following are files used by the Royalty Functions program. They are copied to the back-up disk when you exit Royalty Functions.  They should not be deleted:

RoyInfo.dbf This file contains all of the set-up information for an author or royalty holder.   It is required and should not be deleted.

RoyInfo.mdx An index file which provides rapid access to RoyInfo.dbf. It can be re-created if destroyed.  RoyInfo.dbf, however, can not.

RoyReprt.dbf Contains all royalty reports which have been generated. It is required and should not be deleted.

RoyReprt.mdx An index file which provides rapid access to RoyReprt.dbf. It can be re-created if destroyed.  RoyReprt.dbf, however, can not.

RoyState.dbf Contains name and address information from the Royalty Statement portion of the program. It is required and should not be deleted.

RoyState.mdx An index file which provides rapid access to RoyState.dbf. It can be re-created if destroyed.  RoyState.dbf, however, can not.

RoyItems.dbf Contains the individual transactions listed on the Account Spreadsheet on the Royalty Statement Screen. It is required and should not be deleted.

RoyItems.mdx An index file which provides rapid access to RoyItems. It can be re-created if destroyed.  RoyItems.dbf, however, can not.

RoyTrans.dbf Holds the Transaction List used in Royalty Statements. It is required and should not be deleted.

RoyTotal.dbf Holds the data used in the "Cash Reserves" feature. It is required and should not be deleted.

The following are files used by the AnyPO: The Purchase Order System.  They are copied to the back-up disk when you exit AnyPO.  All the below files have .mdx files.  They should not be deleted:

POCat.dbf Holds the categories used by the stock ordering database. It is required and should not be deleted.

POData.dbf The main database that contains all of the purchase orders.  It is required and should not be deleted.

POData.dbt This file contains all the notes used on purchase orders. It is required and should not be deleted.

POData.mdx The index file for POData.dbf.  It can be deleted.  The program will re-create it.

POrders.dbf A database closely associated with POData.dbf that all of the products on purchase orders.  It is required and should not be deleted.

POrders.mdx The index file for POrders.dbf.   It can be deleted.  The program will re-create it.

POSetup.dbf This file contains all the set-up values for AnyPO.  Required file.

Stock.dbf The stock ordering database. Required file.

Stock.dbt Notes in the stock ordering database. Required filed.

Stock.mdx The index file for Stock.dbf.  The program will re-create if deleted.

VContact.dbf Contact manager for AnyPO. Required file.

VContact.dbt Notes for the contact manager.  Required file.

Vendors.dbf Vendor database.   Required file.

Vendors.dbt Vendor database notes.   Required file.

Vendors.mdx Index file for Vendor.dbf

POFinder.dbf is used for finding past ordered items.  Required file.

POCode.dbf Holds Codes, PO, Tax, etc.   Required file.

POCode.MDX Index file for codes

POExport.dbf Holds Export Profiles.   Required file.

POImplist.dbf Holds Import Replacement Tables.   Required file.

POImport.dbf Holds Import Profiles.   Required file.

The following files are used by the Proforma invoicing system. They are copied to the back-up AnyOrder main back-up disk when you exit AnyOrder.  All the below files have .mdx files.  They should not be deleted:

ZSales.DBF This is the main file that holds proforma invoices

ZSales.DBT This holds the information from the notes area.

ZSales.MDX is the index file for ZSales.dbf

ZOrders.DBF This holds the individual products in the Item Areas

Zorders.MDX is an index file for ZOrders.dbf

PFISetUp.DBF This contains the set-up values for the Proforma Invoicing System

The following files are used by the Standing Order Module. They are copied to the back-up AnyOrder main back-up disk when you exit AnyOrder.  All the below files have .mdx files.  They should not be deleted:

StSales.DBF This is the main file that holds standing order records

StSales.DBT This holds the information from the notes area.

StSales.MDX is the index file for StSales.dbf

StOrders.DBF This holds the individual products in the Item Areas

Storders.MDX is an index file for StOrders.dbf

Other files include:

SumSales.dbf Used as template for exporting purposes, it holds all the information in a sales report.  It should not be deleted.

Header.dbf Used as a template for setting up the header file for exports.  It should not be deleted.

PackQuan.dbf Used for multi-package invoices.   It should not be deleted.

DBExprt.dbf A template file used by Advanced Export and the Flat File Utility.  It should not be deleted.

Sale00.dbf, SaleDat00.mdx, Sale00.dbt, Ord00.dbf, Ord00.mdx.  Used as the starting template files when the program does a primary data file rebuild

SaleDat.dbf, SaleDat.mdx, SaleDat.dbt, OrdDat.dbf, OrdDat.mdx.  These are also used in a primary data file rebuild. In order the protect the starting template files, above, AnyOrder copies the structure of the "00" files above and moves data from Sales and Orders into these files.  When the data transfer is complete, Sales and Orders are replaced with these files.