How to Clean Up Your Data Folder
Occasionally, users have problems that require looking at their data to solve. There are sometimes many files in the data that don't need to be there. This generally isn't a serious problem; but it can lengthen the time needed to back up your data. In cases where people FTP their data to Publishers' Assistant support, it can certainly place an added and unnecessary strain on the communication path to our FTP server. In drastic cases, too many files in a folder can impact system performance. This page documents what should and should not be in your PubAssist data folder.
The data folder is the place where your Publishers' Assistant database is located. For single-user editions, by default, we're talking about "C:\program files\pubassist\data\". However, your data can be located anywhere on your machine or on your network. To be sure of the location of your database, go to "Help" and then "About Publishers' Assistant" on the PubAssist menu.
Contents
What should be in the data folder?
The only files that should be in this folder are those that are associated with the Publishers' Assistant database. As most of our users know, PubAssist has been developed using Microsoft Visual Foxpro. There are potentially three different file types for each table in the PubAssist database implementation: DBF, FPT, and CDX files. The DBF files are the main table file. The FPT file holds the contents of variable length fields (also called "memo" fields). The CDX files are the "compound" index files associated with the table. So for example, the CONTACT table may actually be composed of three files: CONTACT.DBF, CONTACT.FPT, and CONTACT.CDX.
The following table lists the files associated with a "clean" PubAssist database, as of version 4.2x:
INDEX FILES |
TABLE FILES |
MEMO FILES |
BISACSUBJECTCODES.CDX |
BISACSUBJECTCODES.DBF |
|
CODE.CDX |
CODE.DBF |
CODE.FPT |
CONTACT.CDX |
CONTACT.DBF |
CONTACT.FPT |
CONTRIBUTOR.CDX |
CONTRIBUTOR.DBF |
CONTRIBUTOR.FPT |
COURIER.CDX |
COURIER.DBF |
|
CTAXRATE.CDX |
CTAXRATE.DBF |
|
CUSTOMER.CDX |
CUSTOMER.DBF |
|
ERROR.DBF |
ERROR.FPT |
|
INV_TRAN.CDX |
INV_TRAN.DBF |
|
ITEMRCPT.CDX |
ITEMRCPT.DBF |
|
KEY.DBF |
|
|
LDGRTRAN.CDX |
LDGRTRAN.DBF |
LDGRTRAN.FPT |
MRKTCODE.CDX |
MRKTCODE.DBF |
|
ONIXCODES.CDX |
ONIXCODES.DBF |
ONIXCODES.FPT |
ORDERCPT.CDX |
ORDERCPT.DBF |
|
ORDERPAY.CDX |
ORDERPAY.DBF |
|
ORDERS.CDX |
ORDERS.DBF |
ORDERS.FPT |
ORDRITEM.CDX |
ORDRITEM.DBF |
ORDRITEM.FPT |
PA_USER.DBF |
PA_USER.FPT |
|
PROMOTION.CDX |
PROMOTION.DBF |
PROMOTION.FPT |
RECEIPT.CDX |
RECEIPT.DBF |
RECEIPT.FPT |
RECPTYPE.CDX |
RECPTYPE.DBF |
|
REPORTS.CDX |
REPORTS.DBF |
REPORTS.FPT |
RYLTYSPC.CDX |
RYLTYSPC.DBF |
|
SRCOMSPC.CDX |
SRCOMSPC.DBF |
|
STAXRATE.CDX |
STAXRATE.DBF |
|
SUBJECT.CDX |
SUBJECT.DBF |
SUBJECT.FPT |
TITLCOST.CDX |
TITLCOST.DBF |
|
TITLE.CDX |
TITLE.DBF |
TITLE.FPT |
WH_FEES.CDX |
WH_FEES.DBF |
|
WH_SPEC.CDX |
WH_SPEC.DBF |
|
There should be a total of 73 files in a perfectly clean data folder.
NOTE: Some who are familiar with Foxpro may note the absense of a "database container" file, like PUBASSIST.DBC. So far, the costs associated with introducing the database container seem to outweigh the benefits, so there is no database container associated with the PubAssist database. The above tables are all "free" tables.
Files that can be Eliminated
Database Updates
Publishers' Assistant automatically checks for changes in the database structure due to an update. When the update is performed, the original DBF and FPT files are renamed with BAK and TBK extensions, respectively. So, when you check this folder, you are likely to see a CONTACT.BAK and CONTACT.TBK files in addition to those listed in the table above. These files could be renamed back to their original extensions and used in a crisis situation. However, after you have performed a backup and are committed to using the new version of PubAssist, these files are extraneous and should be removed from the directory. There are likely to be MANY BAK and TBK files in the data folder. This is by far the largest contributor to extra data that should not be maintained in the data folder. These files can nearly double the size of your data folder. If your database is large, this can have a significant impact on performance in several ways.
Archival Tables
When you perform an archival, the archived data is moved to tables with the same first six characters as the original table name. For example, archived contacts would reside in a table files, CONTACHS.DBF and CONTACTHS.FPT. These tables could be used in reports for old data. This was the intent when the archival routines were developed. However, to date, no reports have been developed that make use of these archival tables. Thus, all tables ending in "HS" can be safely removed from the data folder.
Other Common Files
Older installation procedures required that at least one file be in a folder for the folder to be created in the installation. Thus there is a README.TXT file that appears in the data folder. This file can be removed. Older installations may also have included FOXUSER.DBF and FOXUSER.FPT in the data folder. These can be removed.
Users often have data folders containing the results of report exports or even report form files. Report forms are actually Foxpro tables. They have file extensions FRX and FRT. These files should reside in the PubAssist folder if they are actively being used. If a duplicate is saved to the data folder, the file in the PubAssist folder will be the ONLY one used! So, save your report changes to the PubAssist folder. Also, you should be saving customized report forms to a unique file name so they don't get overwritten when you reinstall PubAssist.
In General
Any files that do not appear in the table above should probably not be in the data folder. If you are worried about the value of a particular file, move it to another folder for safe keeping. If you don't see a use for it in a six month period, you can probably eliminate it. And, as always, if you have a question about what appears in your data folder, give RonLawrence a call.
Back to HelpArticles
