Operating Instructions

Software Version 1.91

Dated 17^th October 2001

PREXPORT

Table of Contents Page

1. Introduction

2. Installation

3. Basic Operation

4. Examples

5. Command line switches

6. Help

7. Support

8. Control Fields Text File

9. Importing

10. PrExport, File Transfer and Report Generator.

11. Data Validity

12. Speed

13. Spreadsheets

14. Error Messages

15. Security

16. Multi-user

17. Disk space requirements

18. Output formats:

19. Modules:

20. Version Support:

21. Upgrades

22. Managing Exported Versions.

23. Modifications.

24. Prophet File System

25. Files used by PrExport

1. Introduction

PrExport is a software tool, developed to convert data files from the Prophet Accounting System by Attache & Prophet Software, to a variety of standard file formats. It’s primary purpose is to assist those using other analysis tools to view their Prophet data. It is developed solely by McNeill Computers Ltd.

PrExport can be a key element in integrating Prophet to other software systems. There is a wealth of data viewing tools available. These can process, analyse and sort data into all sorts of information. The key to harnessing the power of these tools is being able to access basic business and accounting data transactions. Much of this is held within Prophet, as every day data entry is processed through your Prophet system. This includes invoices, which yield sales analysis, stock movements, purchases and cash transactions. PrExport provides that vital link, bridging raw Prophet data to analysis tools’ presentation power.

A further primary use of PrExport is in converting data out of Prophet into other systems. Because PrExport can convert the entire Prophet file system all in one go, with one command, it allows people converting data to see the whole picture, and choose from all of Prophet’s contents in one hit.

PrExport is itself easy to use - it is usually only one command line. The skill in using PrExport comes in dealing with the files it creates. You need to be proficient in whichever data tool you intend to use. The means you need to be able to open files, select records from files, sort files, and group files together. Many packages have very detailed help, instructions and wizards to help you through these steps.

2. Installation

To install PrExport, copy the PREXPORT.EXE file to your Prophet data directory. You can determine where your Prophet data is held, by pressing Ctrl-F1 while within Prophet. The data directory is shown as Data Files, at the bottom of the screen. The normal directory is C:\PROPHET\DATA.

Step 1: Obtain the DOS prompt C:\> or F:\>

Step 2: Tell DOS to copy the file COPY A:\PREXPORT.EXE C:\PROPHET\DATA

Step 3: Setup a Windows ICON, or menu item, or batch file to run PrExport.

3. Basic Operation

PrExport reads each of the source files in your Prophet system, and converts it to the required output format. It can convert an entire Prophet system, including master files, transaction files, group files and more. Some or all of Prophet’s data files can be converted, using wildcards (asterisks) to specify files.

PrExport has no interactive screens, and asks no questions. All PrExport options are specified on the DOS command line. This is to allow PrExport to be run in batch file mode. A PrExport session can be initiated each night to convert all, or selected Prophet data, from multiple companies with one batch file. The resulting data is ready for further processing each morning. By not asking questions once it has started, PrExport can be left to run through the files unattended.

PrExport can also be run on the spot to convert one, or a selected few files.

4. Examples

A sample PrExport command line is:

PREXPORT -T C:\PROPHET\DATA\SA*.DAT C:\PROPHET\DATA\PREXPORT\SA*.DBF

The example command line would convert all of the Sales Analysis files into Fox Pro 2.5 file format. The source files come from the default Prophet data directory, C:\PROPHET\DATA\ and the resultant output files are placed in a directory PREXPORT below this directory. The extension DBF tells PrExport which file format to convert to.

The -T parameter is required to tell the Foxpro runtime library to suppress it’s display messages. If these are not suppressed, PrExport’s own messages flash past, and can’t be read. We anticipate being able to remove this parameter shortly.

The file specifiers can be abbreviated, using DOS conventions, similar to the copy command. Full directory paths do not need to spelled out. By default, PrExport puts output files in a directory called PREXPORT below the Prophet data directory. PrExport converts to Foxpro 2.5 DBF format by default.

If you are not certain where your Prophet data files are located, start Prophet, go into the company you wish to convert, and press Ctrl-F1. At the bottom of the screen, the data file directory will show. This is the directory to specify to PrExport.

Some more examples are:

PREXPORT -T C:\PROPHET\DATA\ARCUST.DAT C:\PROPHET\DATA\PREXPORT\*.DBF

Convert only the Debtors Master file to DBF format.

PREXPORT -T F:\APPS\PROPHET\DATA\GLACCT.DAT F:\APPS\123R34\*.WK1

Convert only the general ledger account file, from a network directory, to Lotus 123 format.

5. Command line switches

PrExport supports the following command line switches:

-T Suppress Runtime Executable Logo Screens

/T No talk mode - reduces number of messages

/? Help text

/Help Help text

/SO Structure Only - no data filled in, empty DBF’s created.

/LC Leave Control files in output directory when complete

6. Help

To obtain further help in running PrExport, type PrExport -T /HELP. This will show PrExport’s two page help screen, which contains a condensed version of the information in this manual. If PrExport stops before it completes, it will leave a message on the screen giving the reason for the stoppage. If the message flashes past too quickly, make sure you are using the -T parameter for PrExport.

For help on the files created by PrExport, refer to later sections, or the Logical Methods file layouts guide.

If processing is interupted by an error condition, a file prexport.log will be left giving details of the problem.

7. Support

We have a technical support line for PrExport. If you are having difficulty, call us on 026 108 298. Please have ready a description of the problem, and your Prophet serial number. Alternatively, our helpfax number is (09) 292 7226, or by email davemc@wave.co.nz

8. Control Fields Text File

After PrExport has finished, it will create a file called CTRLFLDS.TXT. This contains all of the control fields from control file maintenance for each module from Prophet. This is helpful in reviewing if a Prophet system has all the correct control options set. Being a text file, it can be viewed easily with DOS TYPE or DOS EDIT.

9. Importing

As it’s name implies, PrExport is strictly an exporting tool. Prexport is not able to update, import or amend any Prophet data files. The only tool available for this purpose is Attache & Prophet Software’s File Transfer module. Every record of every file in Prophet is check-summed, and any attempt to alter Prophet data files will usually corrupt at least the record, if not the whole file and it’s keys, and it’s associated files and pointers.

10. PrExport, File Transfer and Report Generator.

Prophet’s own File Transfer module also allows Prophet users to export data files from Prophet systems. File Transfer only allows one file at a time to be exported. This means that if much of the Prophet system is required, many iterations of File Transfer have to be made. An export definition must be run for each of Prophet’s 600 files. PrExport can export many files with one command line, or one batch file.

File Transfer allows the exporting of selective records and fields. It does this with pre-defined filters, and the “Possible, Chosen” dialogue box in maintain definitions. PrExport always exports the whole file. Selective records (rows) and fields (columns) can be removed from files output by Prexport by using the file processing tools that you have exported to.

File transfer can only create ASCII delimited text files. PrExport creates ASCII, as well as formats directly usable by other applications, like Lotus and Excel.

PrExport also exports deleted records, correctly marking them as deleted, but still allowing you to view them. Note that Prophet tags a record for deletion when a delete is made, but does not actually wipe the data until it needs to reuse the file space for a new record. Deleted records will not give complete transaction histories, and cannot be relied upon for comprehensive data retrieval.

Using Report Generator, Prophet’s files can be exported. Data from any combination of modules can be exported. Using Report Generator, a fixed report can be created that extracts specific Prophet data from a number of areas, and combines it into one output file. This is the approach used for bank file formats, such as direct credit schedules. When using RG to export, you must specify a file name each time you run the report. PrExport does not combine data from different files or modules. PrExport always creates files with the same base name as the original Prophet file. To combine data from different files, you should use the relational capabilities of your data tools when working with PrExport files.

11. Data Validity

PrExport will not run while any user is in Prophet. Neither will Prophet start if PrExport is running, because PrExport puts an exclusive file lock on world.dat. This is to protect the validity of both the Prophet files, and the exported files. (Neither system has to worry about what the other is or might be doing to open files). This is the safest, simplest method of guaranteeing that neither system corrupts the other.

This method is specifically approved by Attache & Prophet Software, and no changes are planned to this approach. If this is causing a problem, exit from Prophet, copy your Prophet system to another directory, and run PrExport on the copy.

12. Speed

Because PrExport uses Prophet’s own file structure system, it is not fast. Typically PrExport takes about the same amount of time as a File Recovery of that module. Because of the speed limitations, you need to plan carefully when to initiate a PrExport run, as users will not be able to get into the system while Prophet is running. If necessary, run PrExport overnight, or run PrExport on a copy of the Prophet data.

PrExport can be used to help speed up reporting in PrExport. If you have a number of sales analysis reports that take a while to run, PrExport the sales analysis files, then use a very fast tool like Foxpro to produce the reports. On a 486 with plenty of RAM, Foxpro can sort and select 10,000 records per second.

13. Spreadsheets

Spreadsheets are suitable for analysing or graphing small files from Prophet, such as the General Ledger accounts file. Spreadsheets also work well on the group files, SAGROUP and PAGROUP. Spreadsheets are suitable for cross tab analysis of the Sales Analysis year to date history file. This file is shorter than the main sales analysis history file, because it has had quantities from identical tuples combined. Spreadsheets are not really suitable for processing large files because of memory limitations. Many spreadsheets are limited to 16,384 rows. Prophet transaction and history files can often exceed this by many times.

A handy hint when working with Excel is use PrExport to convert to DBF format, rather than XLS format. Once in Excel, open the files as DBF. Save them as XLS or Normal. There are two advantages to this method.

1. The field names appear as column headings at the top of the spreadsheet

2. PrExport only has to make one pass, so runs faster.

Databases are more suited to processing long or large files. They do not attempt to hold the whole file in memory at once, as spreadsheets do. Databases are also more suited to analysing files with many links, as they can be related back by many fields. A file with many links is the Order Entry Header file. It has relational links to the customer file, the delivery address file, the order entry line file, the stock files, group files and others.

14. Error Messages

When encountering error messages, try to write down the specific error message, and the command line that caused it. Some error messages and their solutions follow:

· Out of disk space

You do not have enough disk space to continue converting files. You need to remove unwanted files from your system, use another drive, or try converting only some Prophet data files.

· Solution 6 file export format not supported yet

PrExport is not yet able to create Solution 6 accounting system files. If you require this format, contact McNeill Computers.

· RT 86 file export format not supported yet

PrExport is not yet able to create RT 86 accounting system files. If you require this format, contact McNeill Computers.

· Unsupported export format

PrExport only supports this listed export formats. Use Prexport help to see the available formats. You can not specify a format that PrExport does not support. Check the spelling of the format extension, which is the last parameter on the PrExport command line.

· File ....... does not exist

PrExport was unable to open a Prophet file that it expected to be able to export. This file will not be converted. PrExport will continue exporting other files in the Prophet system. Check the source directory specified is correct. Check that it contains a complete Prophet system. The file may not apply to the modules you have installed.

· File sign not BOZM on file .....

May not be a Prophet DAT file

PrExport checks the file signature of each Prophet file it is to convert. A file with this error may be very severely corrupted. It may be from a different Prophet series. It may another sort of file, using a Prophet standard file name. It can not be converted, and will be skipped.

· File version not 3.00,3.30 or 3.40 on file .....

PrExport can only convert files from these Prophet versions. If you have an older version of Prophet, upgrade your Prophet first. If you have a newer version of Prophet, contact McNeill Computers for an upgrade to PrExport. If you have one of these versions, the Prophet file may be corrupt, or may not be a real Prophet data file.

· Field length 0 detected

PrExport found a field whose definition specified it to be 0 bytes long. PrExport will use the default length for the type of field specified.

· File not in definitions

PrExport can not find the field definitions for the file it is attempting to convert. This is an unusual error, as PrExport should previously have created the definitions for the file before attempting to convert it. The FEFILES or FILEDEF databases may be corrupt. Restart PrExport, or skip this file.

· Switch ..... not recognised

You can not use this switch on the PrExport command line. PrExport may also have confused a switch (which starts with a forward slash / ) with a file specifier. Try changing the spacing of the switches. Make sure the switches are separated from the file specifiers with spaces. Check the list of available switches in the section Command Line switches, or the command line help. Make sure your directory specifiers use backslashes \ .

· Prophet file name to convert is longer than 12 characters

Source file names contain 8 characters, a dot, and three characters extension, which is DAT or TXT. Longer file names are not valid DOS file names. Use DIR to view valid file names. Make sure your backslash \ separates the directory name from the file wildcards.

· Prophet source directory is longer than 64 characters (DOS limit)

The directory to convert from can not be longer than 64 characters. Make sure your file source and destination specifiers are separated by spaces. Use CD to change closer to your Prophet data directory, then use abbreviated source specifiers, which do not include the full path. Try using a SUBST or MAP ROOT drive to shorten the DOS path.

· Unable to create a new file in specified destination directory

PrExport tests that it is able to create a new file in the intended destination directory for all it’s converted files. An error will often show up at this point. Possible causes of this error are:

· Insufficient network file creation or access rights

· Insufficient disk space

· The destination directory is a new subdirectory of a new directory. PrExport can only create one new subdirectory layer.

· Insufficient file open handles

· The destination drive does not exist

· PrExport is confused about where to put the files - try an alternate command line.

· A file already exists with the same name as the intended directory

· A dropped file open handle

· The temporary test file already exists from a prior failed file open test

· Converted destination directory is longer than 64 characters (DOS limit

The directory to convert to can not be longer than 64 characters. Make sure your file source and destination specifiers are separated by spaces. Use CD to change closer to your Prophet data directory, then use abbreviated destination specifiers, which do not include the full path. Try using a SUBST or MAP ROOT drive to shorten the DOS path.

The following are errors encountered while accessing Prophet files.

· File not found

PrExport was unable to open an input file. Try running PrExport from another directory.

· Too many files open (out of handles)

· Increase the FILE HANDLES= in the SHELL.CFG or NET.CFG

· Increase the /F: and /L: parameters on the SHARE command line

· Increase the number of FILES= in the config.sys then reboot

· Close some concurrent applications or windows

· Access denied, Prophet possibly still in use

Make sure no users on the network are still in Prophet. Make sure no Prophet systems are open in hidden DOS shells under Windows, OS/2, NT, DOS Shell, Unix DOS emulators or Desqview.

Make sure a backup is not running on the Prophet data.

· Invalid file handle given

An internal file handling error caused Foxpro to be confused as to which file it was dealing with. Stop PrExport and start it again.

· Out of memory

You require more base memory, or extended memory. Remove TSR’s, or exit from Windows. Purchase some more RAM, and configure it properly.

· Seek error (can't seek before the start of a file)

The file may have changed while PrExport is attempting to use it. Check the network is operating correctly, and that no-one is using Prophet.

· Disk full

Buy an additional hard drive.

· Error opening file or general failure (EOF encountered)

The file or file system may be corrupt. Check that Prophet is able to run correctly.

· Unknown file error number

PrExport was unable to process a file, and unable to work out why it couldn’t process the file. Try copying the Prophet data to a new location, and re-running PrExport.

· Unknown Boolean Type ....

A Yes/No data field in Prophet was not Yes or No. The data file may be corrupt. The data field may be a “shade of grey!”

· License violation

PrExport will only run on the serial number it is licensed to.

· A FATAL ERROR HAS OCCURRED AND IS LOGGED PLEASE CALL SUPPORT

One of 1,000 types of Foxpro errors has stopped PrExport. The details are in the .LOG file, and we are able to determine the fault from this file.

15. Security

PrExport is licensed only to your Prophet serial number. It will not operate on any serial number other than the one it is licensed to. It will Prexport any number of valid companies that you have on your serial number. You must purchase a separate PrExport for each different serial number.

16. F2 Notes

The contents of the notetext.dat file, which is all the F2 notes, for all master and group files, are included as a memo field on each record of the notepad file. Comment or slash lines in body edits are included as memo fields on the relevant files, such as OILINE, POLINE etc. Some output data formats do not support memo fields, so these may not be visible. They can be seen in DBF format, with their associated FPT’s.

17. Multi-user

PrExport will function in a multi-user environment, such as Novell or Windows NT. All Prophet users must be out of PrExport before it will start. No Prophet users will be able to start Prophet while PrExport is running. No PrExport users will be able to start PrExport while Prophet is running either. This will ensure both the integrity of your Prophet data, and the validity of the exported files. Two PrExport’s can not be run at once. Becasue PrExport takes a while to run, and people wish to have access to Prophet, make a copy of your Prophet data to a test company, then run PrExport on the copy.

18. Disk space requirements

To convert an entire system to DBF format, PrExport requires the same amount of disk space as occupied by the original Prophet system. On systems with large data files, this can amount to a lot of space. To convert to a format other than DBF, you will require the same amount of disk space as the original, plus extra space by the size of the largest file in the system. Typically OILINE.DAT is the largest file, and can grow to 90Mb or more.

You can check the amount of available space, by using the DOS DIR command. From the Prophet data directory, C:\PROPHET\DATA, type DIR. The last number is the amount of free space, the second to last number is the amount of space used by your Prophet data files. If the amount used is more than the amount free, you can not PrExport your whole system. You may have enough space to PrExport some of your files. To obtain more space, carefully delete un-needed files, or buy another disk drive.

19. Output formats:

PrExport’s native output format is DBF - Foxpro 2.5. PrExport uses this as an intermediate format in creating all other formats.

PrExport can also create the following output formats.

DBF FoxPro, dBase IV, Clipper etc.

TXT Comma delimited standard ASCII text file.

XLS Microsoft Excel spreadsheet version 2.

DIF Data Interchange Format, used by VisiCalc.

MOD Multiplan version 4.01 MOD format.

SDF System Data Format file.

SYLK SYmbolic LinK interchange format.

WKS Lotus 1-2-3 revision 1-A spreadsheet.

WR1 Lotus Symphony spreadsheet revision 1.10.

WRK Lotus Symphony spreadsheet revision 1.0.

WK1 Lotus 1-2-3 revision 2.x spreadsheet.

20. Modules:

PrExport supports the following modules in Prophet:

· Accounts Receivable

· Order Entry

· Invoicing

· Inventory Control

· Sales Analysis

· Bill of Materials

· Job Costing

· Accounts Payable

· Cashbook

· General Ledger

· Fixed Assets

· Purchase Analysis

· Database

· Purchase Ordering

· Toolbox (limited)

· Payroll

· System Initialisation

21. Version Support:

Series I Version 1.00 as file format 2.50

Series II (SE and Original)

Version 2.5 to 2.55 as file format 2.5

Series III Versions 3.00 to 3.29 as file format 3.00

3.30 to 3.39 as file format 3.30

3.40 as file format 3.40

3.50 to 3.55 as file format 3.50

3.60 as file format 3.60

3.70 as file format 3.70

3.80 as file format 3.80

Series IV Versions 4.00

4.10

4.20

4.30 (including 4.35 which is 4.30 file format)

22. Upgrades

Please contact McNeill Computers for an upgrade if your system is later than 4.35

23. Managing Exported Versions.

If you PrExport a data set, make changes to it using your data analysis tool, then PrExport again to the same location, you will loose the modifications you have made. Be careful to save changes made to the exported files to a separate location, if you want to keep the changes.

24. Modifications.

We are able to make changes to PrExport, to suit new file formats, or to produce modified output files suited to a specific use. Please contact us for more details on feasibility and cost.

25. Prophet File System

For details on the Prophet file system, refer to Attache & Prophet Software’s file layouts chapters in the File Transfer section of the Prophet manual. Alternatively, use the files FEFILES and FILEDEF created by PrExport to determine which file you need to PrExport. Also, HTML versions of the file definitions are now available on the release CD’s.

File Name	File Description
APCRED	Accounts Payable Creditor file
APTRANS	Accounts Payable transaction file
APCHEQUE	AP Cheque Ledger File
APGLMAP	Accounts Payable GL mapping file
APCURREN	AP Current period Analysis file
APTAX	Accounts Payable Tax analysis file
PAGROUP	Purchase Analysis groupings file
APFUTURE	AP Future period Analysis file
PAHISTOR	PA Aged analysis file
PAYTD	PA Year to date analysis file
ARCUST	Accounts Receivable Customer file
ARTRANS	AR transaction file
ARGLMAP	Accounts Receivable GL mapping file
ARDELIV	AR Delivery address file
ARALLOC	Accounts Receivable Allocation File
ARBANK	Accounts Receivable Banking file
ARGLSUM	Accounts Receivable GL summary file
ARONE	AR One time debtor listing file
ARANALYS	AR Current period analysis file
SACHARGE	AR Charges analysis file
SATAX	AR Tax analysis file
SAGROUP	Sales Analysis groupings file
SAYTD	SA Year to date analysis file
SAHISTOR	SA Aged analysis file
GLACCT	General Ledger account file
GLTRANS	General Ledger transaction file
GLBATCH	General Ledger Batch header file
GLLINE	General Ledger Batch line file
GLRHEAD	General Ledger Report header file
GLRRANGE	General Ledger Report ranges file
GLRTEXT	GL report text layouts file
GLRLAY	General Ledger Report layout file
ICBASE	Inventory Control master stock file
ICBRANCH	Inventory Control Branch stock file
ICBRAN	Inventory Control Branch names file
ICTRANS	Inventory Control transaction file
ICKIT	IC Kitset definition file
ICMARK	IC Markup percentages file
ICQUAN	IC Quantity discounts file
ICTRACK	IC Tracking File
ICUNIT	IC Stock Unit File
ICGLMAP	Inventory Control GL mapping file
ICGLMAPW	IC GL wastage mapping file
OIHEAD	OE/IN Invoice Header file
OILINE	IN/OE Invoice Line file
OIDISC	OE/IN Discount file
OIMST	OE/IN Standard text file
OIDATE	OE/IN Template Generation Date File
OICASH	OE/IN cash sale receipts file
OILAYOUT	Invoice / Packing slip layout file
BMBILL	Bill of Materials Bill header file
BMLINE	Bill of Materials Bill line file
BMRESERV	Bill of Materials Reservations file
BMSTOCK	Bill of Materials Reserve line file
BMTRANS	Bill of Materials Transaction file
BMGLMAP	Bill of Materials GL mapping file
BMGLOBAL	BM Global replacement file
BMALTER	BM Alternate stock file
JCPROJ	Job Costing job body details file
JCHEAD	Job Costing Job header file
JCCLAIM	Job Costing invoices produced file
JCBATCH	Job Costing Batch header file
JCLINE	Job Costing Actuals line file
JCTIME	Job Costing Time codes file
JCOVER	Job Costing Disbursement codes file
JCRATE	Job Costing Overtime rates file
JCGLMAP	Job Costing GL mapping file
JCGROUP	Job Costing analysis groupings file
CBBANK	Cashbook bank account file
CBTRANS	Cashbook transaction file
CBDEPOSI	Cashbook Deposit type file
CBLINE	Cashbook line file
CBDIRECT	Cashbook direct file
CBGROUP	Cashbook group file
CBCASHBO	Cashbook Report Layout File
CBBUDGET	CB budget/cashflow report defn file
CBCASHFL	CB Statement of cashflow rept file
CBMAPIN	Cashbook GL inwards mapping file
CBMAPOUT	Cashbook GL outwards mapping file
CBRECON	Cashbook stmt reconciliation file
RGHEAD	Report Generator header file
RGALIAS	Report Generator aliases file
RGAREA	Report Generator report areas file
RGBODY	Report Generator report body file
RGFIELD	Report Generator report fields file
FEFILES	File Exporting files available file
FESELECT	File Exporting selections file
FEFIELD	File Exporting export fields file
POHEAD	Purchase Ordering Order Header File
POLINE	Purchase Ordering Order Line File
POPRICE	Purcase Ordering Price File
POLAYOUT	Purchase order / quote layout file
PODELIV	PO company delivery address file
FAASSET	Fixed Assets Master File
FATRANS	Fixed Assets transaction file
FAGROUP	Fixed Assets groupings file
FAMAP	FA GL Integration Map File
FAFREQ	Fixed Assets Depn Frequency File
FASERV	Fixed Assets service file
PREMPLOY	Payroll employee master file
PRALLOW	Payroll allowances file
PRRATE	Payroll pay rates file
PRHEAD	Payroll timesheet header file
PRLINE	Payroll timesheet line file
PRALINE	Payroll allowance line file
PRTRANS	Payroll transaction file
PRGROUP	Payroll groups file
PRGLMAP	Payroll GL gross pay mapping file
PRGLMAPA	Payroll GL allowance mapping file
PRTAX	Payroll tax rates file
PRFACTOR	Payroll time factor file
PRANALYS	Payroll analysis file
PRPAYRUN	Payroll payrun summary file
PRGENERA	Payroll generated pays file
PRBALANC	Payroll employee balances file
PRPAYMNT	Payroll payment history file
PRMNTRUN	Payroll payment run file
PRMAKEPM	Payroll make payments file
PRAT	Payroll Allowance Transactions
PRGLCONS	Payrol GLI consolidation file
PRJCBATC	Payroll Job Batch Header file
PRJCHEAD	Payoll Job Batch Header file
PRJCLINE	Paryoll JC batch line file
DBRES	Database resource file
DBEXPN	Database expression file
DBLINK	Database link file
DBFIELD	Database field definition file
DBMIRROR	Database field mirroring defn file
DBHEAD	Database import defn header file
DBLINE	Database import defn line file
DBTEXT	Database text field file
DBATTACH	Database/Prophet attachment file

26. Files used by PrExport

PrExport.EXE The main executable

Emptydbf.DBF Empty data file used for spawning all other DBF files.

Dummy.TXT Blank file used to test file opening rights

PrExport.DBF A temporary work file

Filedef.DBF Field definitions list

Filedef.IDX Index key file for filedef

FileCtrl.DBF Control fields for each file

FileKey.DBF Index keys that Prophet uses for each file.

Prexport.LOG Text file, logging any runtime errors in PrExport.

Copyright September 1993 to October 2001

McNeill Computers Limited

Prophet Accounting Support Specialists

Buchanan Road

RD 1

Papakura

Phone ++64 9 292 7212

Fax ++ 64 9 292 7226

davemc@mcpond.co.nz