You are on page 1of 148

About Btrieve

Until June 1994, Btrieve was a product owned by Novell. Btrieve was then owned by a company called Btrieve Technologies, who broke away from Novell to develop Btrieve further, and they are now called Pervasive Software.. Btrieve is a low level database engine, which controls the storing of data and the sorting of records. One of the greatest benefits of using Btrieve is it's data integrity: the built in security against data corruption are second to none - however this does not mean that data cannot be corrupted. Btrieve writes data to a pre image file (.PRE) before updating the main data file (.DAT); this makes Exchequer very robust in events such as power loss, whereby data will usually be in tact. However, for this security you pay a price in terms of speed. You can speed up Btrieve, which in turn speeds up the operation of Exchequer by up to 3 times (especially when posting). However, we do not recommend this as it uses memory to perform it's pre imaging of files and is far more volatile than the other method. However, if it is necessary to increase the speed of a system and the client is aware of the dangers (and preferably has a UPS and a good backup discipline). then it is OK to configure the system to run in Accelerated mode on v5.10 of Btrieve.

Accelerated Mode
Running Exchequer in Accelerated mode - Btrieve v5.10. Please ensure that you back-up your Exchequer system. if you want to run Exchequer in accelerated mode, from within the Exchequer directory, firstly, you will need to copy the Rex.bat batch file if you havent previously and call it, RexAC.bat. Then edit the line that reads; excheqr to read; excheqr /AC: and instead of calling Exchequer with the Rex command use RexAC; Please be aware that running Exchequer in accelerated mode, must be on a stand alone machine, and you must be prepared to restore a back-up.(There is no Accelerated mode for v6 of Btrieve)

Accounting
1. The Accounting Equation. Net Assets = Proprietor's funds

A change in the total on one side will produce a compensating change in the total on the other side. An increase in net assets (from start to end of period) = Any capital + introduced (during the period) (for Period) Any Profits - Any Drawings (over period)

We can use the accounting equation to calculate a missing amount when one of the four figures is unknown. Illustration 1. Ivor's business had net assets of 7,500 on 1 January 19x5. At 31 December 19x5 they amounted to 12,000. During the year he introduced 300 additional capital and withdrew 1,200 for his own use. What was his profit or loss for the year? Increase in net assets (12,000 - 7,500) Profit = Capital introduced + profit - drawings = 300 + Profit - 1,200 = 1,200 + 4,500 - 300 = 5,400 2. The Balance Sheet Dr Debit Drive on the Left. Rules 1. 2. 3. 4. 5. 6. 7. 8. an increase in assets an increase in proprietor's funds a decrease in assets an increase in expenses an increase in liabilities an increase in revenue/income a decrease in liability a decrease in proprietor's funds Balance Sheet Dr Assets Profit & Loss Dr Expense Cr Income Cr Liabilities = Dr = Cr = Cr = Dr = Cr = Cr = Dr = Dr Cr Crash on the Right

Assets which are Dr in the Balance Sheet become Income or Cr in the Profit and Loss.

American Date in Form Design


American Date format can be achieved in form designer.

This worked example shows how versatile the form designer is, and how a bit of thought in conjunction with the help file, can often achieve the required results To show a date field in American format, in Enterprise, you need to split the field up and use formulae as shown below.

A B C You could take this one step further, and add the formulae together, please refer to the form designer help. the flexability of Date Printing is further extended by the FMTDATE function in Forms Designer. For example "FMTDATE[SYSTODAY,0,D,3] returns today's date in Windows Long Format. Eg. 12 January 2000 Application Error
This will come up with a popup display giving the developers information about where the error has occurred. details should be printed and faxed to us where ever possible. If not possible then all the details should be noted and passed to development with the version of Enterprise in use.

Common Instances of an Application Error It may be that these 2 PCs Have or at one time had the HP Jet Admin installed. Look for the following files in to windows Directory. calwin32.dll and clnwinth.dll If they are there try re naming them. If Novell Network and using the Novell 32 bit client, this has been known to prevent Network login. Whenever the error message is c0000001,2 or 3 you can almost guarantee it is the dll's that are causing the problem, c000006 is also usually suspect for the communications to the client server engine or comms in general. ____________________________________________________

Applying patches
Applying patches for NT servers and Workstations is recommended. For client server versions of Btrieve the latest patches should also be applied. For example 6.15.445 Netware patch for Btrieve has been known to cure some workstations reporting error 11. (This was where the client was confusing the path) also some cases of Error 94 have been resolved.

BACS

The BACS output file EXCHBACS.IMP is output from the Batch Payments/Receipts run in Procedures Batch Payments/Receipts Purchase Payments or Sales Receipts. If you are taking money from Customers then you need to send them the receipt notification two weeks before the date of the BACS payment date. Change customer/supplier to type B, and run batch payments as type B, Also set up bank account details for customer/supplier, and their own bank details in System Setup. There is also a batch file BACS.BAT for Exchequer which can be used to run the BACS SW from within Exchequer Exchequer produces files which the BACS Software will need the files are called EXCHBACS.IMP for supplier payments, EXCHDDEB.IMP for customer direct debits. (Batch payments can be found under Reports, credit control reports, batch payments in Exchequer DOS) Layout of file below
Dest Dest Zero Tran Company Company Zero Amount Destination Pay Sort Account Fill Code Sort Account Reference Account Date Code Number Code Number Name yyddmm Company Fill In Pence Name Free Format Account or Blank

6 8 1 2 6 8 4 11 18 18 18 6 123456 12345678 0 12 123456 12345678 0000 12345678901 Company Name Limtd. Users Refnce.Field Destn Account Name Paydat xxxxxx xxxxxxxx x xx xxxxxx xxxxxxxx xxxx xxxxxxxxxxx xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxx xxxxxx The total size of the record is 106 characters. 2030220443234409900000000000000000000000026438DEMO VERSION ONLY PPY000187/43 POLISHED PRINTERS 98259 4033440203020309900000000000000000000000029375DEMO VERSION ONLY PPY000188/43 SOUTHERN NEWSPAPER 98259 2132120020121209900000000000000000000001266909DEMO VERSION ONLY PPY000189/43 TAXAN MONITORS 98259 0000000000000001700000000000000000000001322722BACS 43 CONTRA DEMO VERSION ONLY 98259 Tran Code has several values as listed below. 17 99 Total Payment line

Exchequer and Enterprise link with Access Europe's BACS software packages (Access Europe and PCBACS) and Albany Software's ALBACS to name but a few.

Back Ups
Q: When backing up disk was not formatted. Message: abort/retry/fail tried pressing all three but nothing happened. A: Do not reset machine - press abort a few times and then fail something must happen eventually. Then choose drive C and go back into DOS/Exch to format the disk. Restart backup. Q: When backing up system keeps asking for next disk but isn't listing files on screen, i.e. not backing up. A: Disk drive needs cleaning. Clean it and then back up should work. Users are responsible for their own backup device, and should be made aware of the importance of backing up, and make sure it works and they know how to restore.

Disk space permitting you could use the xcopy command xcopy c:\exch\*.* c:\backup\*.* /s when done try running Exchequer in the backup directory to check it has copied all the files, and check last work input is there. Do not do whilst anyone in the system.

Bad Debts and VAT


Q - I want to reclaim VAT on a debt because it is over 1 year old. However, the company is still trading and I wish to keep a statement for them. A - This is a 3 part operation, a worked example is below: On account Macd01 there are two invoices we want to write off the VAT on. SIN 237 SIN 238 Firstly raise a Sales Journal Credit Note for the total amount of the invoice(s) that you are claiming for, ensuring that the VAT is equal to the total VAT of the invoices. Post to a nominal account `Bad Debts Written Off' in the overheads section of your Profit and Loss. code 76030 in our case.

Secondly raise a Sales Journal Invoice for the total amount of the invoices but this time the VAT will be Exempt rated. The total of this SJI should be the same as the SJC. Post this also to the `Bad Debts Written Off' nominal account.

Bad Debt Allocate


Thirdly, access the customer's ledger and allocate the SJC and the SJI together - thus leaving the customer's ledger the same as it was.

If they then pay, the VAT must be paid again. This is done the opposite way by Adding a SJI Vat rate coded to Bad Debts, and a SJC Exempt rated also coded to bad debts, and allocate to each other on the customer's ledger.

Bad Debt Write Off


Q - I want to write off a bad debt. A - Raise a Journal (SJC) and post to Bad debts nominal account (for the goods value only excluding the VAT amount). NOTE. VAT should not be reclaimed until six months after the debt has been written off. When the six months have elapsed create an SJC with VAT only This is the way we would recommend that you do the write off but check with your accountant for verification.

Bank Reconciliation
Q - I've done my reconciliation and found some omissions; I went back to the daybooks and made the necessary corrections, but when I go back to the reconciliation screen the corrections don't appear - why not? A - The corrections need to be posted before they will appear on the reconciliation screen. Check to see if they are still sitting in the daybooks, if they are then you will need to post them. Q - After doing my bank reconciliation Exchequer's cleared balance is different from the closing balance on my bank statement. A - Unclear all the entries you have cleared from the statements and make sure the balance you started with matches the balance of the last statement you cleared. If it does the error lies in the items you cleared, so clear them again carefully. If the cleared balance does not then the error has been caused by an item from a previous statement. You will need to unclear items from previous statements until you get a balance that matches a bank statement. If you suspect that the reconciling has been done correctly, try using the Check facility on the bank reconciliation screen. This recalculates the balance of all cleared items. NB this can take a long time - only do as a last resort, and when you don't need to use the computer for a few hours. Grouped items Q: Since upgrading 'Grouped items' have disappeared from the bank reconciliation. A: Check you are on a version later than v4.10a and run check, after drilling down to the bank account from the nominal ledger. Bank Reconciliation Report Q: Nothing appeared on my bank reconciliation report. A: The bank reconciliation report can only be printed if there are uncleared items in the Exchequer bank account. If the bank account has been completely cleared, nothing will appear on the report.

Bill of Materials
Quick reference for BOMs If a BOM has to be built, ie manufacturing, the deduct Materials if no BOM stock switch should be set to no. If a BOM is kitted, ie put together at time of dispatch, the deduct Materials if no BOM stock switch should be set to yes. This setting "Explodes" the components onto the transaction. This switch has been extended to Explode on Sales./ Purchases and both. See Enterprise help for futher information. With Live stock, when building BOMs nominal codes are taken from the parent BOM. This has changed from v4.31 onward and the individual component Nominal codes are used. See Enterprise help for further information. Goto BOM in Enterprise Help.

Blank Stock Code


Blank stock code v3 Exch

Description of Problem Empty stock code in their stock tree & it contains those documents(e.g. SJIs) that were generated without stock code. We do not know how they managed to save an empty stock code in the stock tree. To rectify the problem with the empty stock code follow the procedure below, after backing up and making sure everyone is out of Exchequer; 1) Do a blank install into a temp directory of exactly the same version. 2) Copy Stock.dat into the temp directory. 3) Delete the offending stock item. 4) Copy Stock.dat back into the exchequer directory 5) Tidy up by deleting the temp directory. After you have completed the above, upgrade to the latest version to avoid the problem recurring.
Btrbox95 and DOS Applications Issue: Some customers have expressed concern that their users could inadvertently close Btrbox95 while the application is still in use, thus causing problems to data. Solution: Btrbox95 gives a warning statement when a user attempts to close it while their application is still in use. It specifically states that closing Btrbox95 will cause the application to give errors with unpredictable results and provides with the option of not closing it. This should be sufficient for keeping people from closing it accidentally.

Btrieve Errors
10 : Mess:='Modify Error... Modify to Non Modify Key'; 11 : Begin Mess:='Invalid File Name.'filename' 'The path of the file being opened is not recognized as being valid.'filename' 'Check your network connection is still working, and check using Explorer'filename' 'that the file being opened can be found in the directory named above.'+#13; Mess:=Mess+'If Explorer cannot see them, then the directory or your network connection'filename' 'needs correcting.'; end; 12 : Begin Mess:='File Not Found'filename' 'The file being opened could not be found in the directory specified,'filename' 'although the directory itself is valid.'filename' 'Check your network connection is still working, and check using Explorer'filename' 'that the file being opened can be found in the directory named above.'+#13; Mess:=Mess+'If Explorer cannot see them, then the directory or your network connection'filename' 'needs correcting.'; end; 13 : Mess:='Extension Error'; 14 : Begin Mess:='Pre-Image File Open Error.'filename' 'The pre-image file (ending in extension .PRE) is damaged.'filename' 'This error normally occurs after a system or network crash on v5.X'filename' 'format files.'filename' 'This may be a temporary problem due to a current network fault.'filename' 'Try closing the system down, rebooting your machine and running'+#13; Mess:=Mess+'the system again. If the error persists, contact your supplier'filename' 'for instructions on data recovery, or ultimately the restoration of 'filename'

'the most recent backup.'filename'#13+ 'It is also advisable to convert the data files to a v6.X format, to' filename' 'avoid this problem in the future.'; end; 15 : Mess:='Pre-Image File Write Error.'filename' 'It was not possible to update the above pre-image file.'filename' 'This error normally occur after a system or network crash on v5.X'filename' 'format files.'filename' 'This may be a temporary problem due to a current network fault.'filename' 'Try closing the system down, rebooting your machine and running'+#13; Mess:=Mess+'the system again. If the error persists, contact your supplier'filename' 'for instructions on data recovery, or ultimately the restoration of 'filename' 'the most recent backup.'filename' 'It is also advisable to convert the data files to a v6.X format, to avoid this problem in the future. 16 : Mess:='Expansion Error'; 17 : Mess:='Close Error ... '; 18 : Begin Mess:='Disk Full!!'filename' 'The hard disk you are writing to is full, or there is a network fault 'filename' 'preventing the system from writing any more information.'filename'#13+ 'This may be a temporary problem due to a current network fault.'filename' 'Try closing the system down, rebooting your machine and running'+#13; Mess:=Mess+'the system again. If the error persists, use Explorer to detect 'filename' 'the amount of free disk space on your server and free up more space 'filename' 'if necessary.'; end; 19 : Mess:='Unrecoverable Error'; 20 : Mess:='Record Manager not Active.'filename' 'It was not possible to connect to The Pervasive.SQL engine.'filename' 'Check the directory you are trying to access contains a working'filename' 'Pervasive engine. Try reapplying the workstation setup for this'filename' 'machine. If the problem persists, contact your supplier.'; 21 : Mess:='Key Buffer Error'; 22 : Mess:='Record Buffer.. Length Mismatch.'filename' 'The record being read or written to the above file is the wrong size.'filename' 'This problem is normally caused by a mismatch between your data and the version'filename' 'of Enterprise being used on it. Likely causes are the non or incomplete'filename' 'application of a previous conversion. Contact your supplier for guidance.'; 23 : Mess:='Position Block'; 24 : Mess:='Page Size Multiple Error'; 25 : Mess:='Create IO Error.'filename' 'The system was unable to create a new data file. Make sure you have'filename' 'sufficient access rights to create files in the above directory.'; 26 : Mess:='No of Keys Exceeds Page Size'; 27 : Mess:='Key Position Error'; 28 : Mess:='Record Length'; 29 : Mess:='Key Length Error'; 30 : Begin Mess:='Not a valid Pervasive.SQL File!'filename' 'The system does not recognise this file as being of the correct format.'filename'

'This may be a temporary problem due to a current network fault.'filename' 'Try closing the system down, rebooting your machine and running'filename' 'the system again. If the error persists, contact your supplier'+#13; Mess:=Mess+'for instructions on data recovery, or ultimately the restoration of 'filename' 'the most recent backup.'filename'#13+ 'If this error is ocrring on all files, it is also possible that the version'filename' 'of data files is higher than v6.x and need to be converted back down to v6.x.'; end; 31 : Mess:='Extend already implemented'; 32 : Mess:='Extend IO Error'; 34 : Mess:='Extend File Name not valid'; 35 : Mess:='Invalid Path'; 36 : Mess:='Transaction not possible as an insufficient number of of Transactions has been set.'filename' 'Protected mode posting is not possible as the Pervasive.SQL engine has been set up'filename' 'with too few transactions. Adjust the Transaction setting in the engine setup.'; 37 : Mess:='A Begin Tran was called before a previous Tran had finished'; 38 : Mess:='Transaction Control File Error'; 39 : Mess:='End/Abort Transaction called before Begin'; 40 : Mess:='Transaction Max Files'; 41 : Mess:='Transaction Operation'; 42 : Mess:='Incomplete Accelerated Access'; 43 : Mess:='Invalid Data record Address'; 44 : Mess:='Null Key Path..'; 45 : Mess:='Inconsistent Key Flag settings'; 46 : Begin Mess:='Access to File Denied.'filename' 'This can often be caused by a Btrieve engine configuration mismatch.'filename' 'Check all workstations are accessing the system in the same mode.'filename' 'Either all local, or all C/S. Make sure you have sufficient access rights.'filename' 'Also check that the same mode is being observed by Exchequer (DOS).'; Mess:=Messfilename'#13+'If your data files have been copied from a CD-Rom, check the files'filename' 'are set to read/write access as CD-Rom files are normally read only!'; end; 47 : Mess:='Maximum No. of Open Files.'filename' 'The maximum number of files required needs to be increased within the Pervasive.SQL'filename' 'setup. Check EntRead for the standard settings.'; 48 : Mess:='Invalid Alt Col Seq'; 49 : Mess:='Key Type Error'; 50 : Mess:='Owner Already Set'; 51 : Mess:='Invalid Owner'; 52 : Mess:='Error writing cache'; 53 : Mess:='Invalid I/F'; 54 : Mess:='Variable Page Error'; 55 : Mess:='Autoincrement Error'; 56 : Mess:='Incomplete Index'; 57 : Mess:='Expand Memory Error'; 58 : Mess:='Compression Buffer too Short.'filename' 'The minimum compressed record size needs to be increased within the Pervasive.SQL'filename' 'setup. Check EntRead for the standard settings.'; 59 : Mess:='File Already Exsists'; 80 : Mess:='Conflict.. Record Changed By Other Station since Read';

Mess:='Lock Error'; Mess:='Lost Position'; Mess:='Read Outside Transaction'; Mess:='Record in Use'; Mess:='File in Use (by another Transaction)'; Mess:='File Full!!'; Mess:='Handle Full'filename' 'The maximum number of handles required needs to be increased within the Pervasive.SQL'filename' 'setup. Check EntRead for the standard settings.'; 88 : Begin Mess:='Incompatible Mode'filename' 'This can often be caused by a Btrieve engine configuration mismatch.'filename' 'Check all workstations are accessing the system in the same mode.'filename' 'Either all local, or all C/S.'filename' 'Also check that the same mode is being observed by Exchequer (DOS).'; end; 89 : Mess:='Name Error'; 90 : Mess:='Device Full'; 91 : Mess:='Server Error'; 92 : Mess:='Trans Full'; 93 : Mess:='Incompatible Lock Type'; 94 : Begin Mess:='Permission Error.'filename' 'Your server is refusing to grant you read/write access to the system.'filename' 'Check that your access rights are correct. If the problem persists you may need'filename' 'to update your Pervasive.SQL or your network client. Contact your supplier for further'+#13; Mess:=Mess+'guidance.'; end; 95 : Begin Mess:='Connection to server lost.'filename' 'The network session to your server has been lost. This may be a temporary problem due'filename' ' to a current network fault.'filename' 'Try closing the system down, rebooting your machine and running'filename' 'the system again. If the error persists, contact your supplier'+#13; Mess:=Mess+'for instructions on data recovery, or ultimately the restoration of 'filename' 'the most recent backup.'; end; 97 : Mess:='Data Message too Small'; 99 : Mess:='Demo Error'; else Mess:='?! Unknown Error.'filename' 'The error returned by Pervasve.SQL is not recognise. Consult your supplier.'; end; Set_StatMes:=Mess; end; Btrieve Monitor Novell Btrieve v6.x:- Run BTRMON from the server if it is not already loaded. Btrieve v7.x:- You will need a workstation with a correctly installed Pervasive client. This utility can then be run from the Pervasive/ Btrieve program group.

81 : 82 : 83 : 84 : 85 : 86 : 87 :

NT This utility can then be run from the Pervasive/ Btrieve program group.(all versions) Faults on Ver 4.21 Data entry corruption when using notes in Enterprise ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A fault has been identified when notes are added to a transaction before the transaction has been stored for the first time. If notes are added, or simply by clicking on the notes tab on a transaction whilst another user is also adding a transaction, the details of the second transaction can become superimposed on the first, causing corruption. During tests it has been found that SRC's, and PPY's are most susceptible to this problem. On most occasions the user is prevented from storing the transaction by the validation checks which are used as a transaction is stored, which should limit the scope of this problem. To get round the fault it is recommended that the transaction is reset by using the <Alt> Z key on any field in the header part of the transaction. Any allocations should also be undone at this point. Exchequer Software are aware of this problem, and have corrected it in v4.22, in the meantime it is advisable to instruct your users to only add notes once a transaction has been stored. All current versions of Enterprise are affected by this problem. Exchequer is not affected by this problem.

Range check error (201) when producing large purchase orders via the Interactive Reorder Screen ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As of version v4.20 on Exchequer and Enterprise a potential fault has been discovered when generating large purchase orders using the interactive reorder screen. As a consequence from the introduction of purchase kiting a purchase order generated via the interactive reorder screen is limited to 128 lines. If this limit is exceeded, a range check exception (error 201) is caused leaving the purchase order incomplete, and without a header. If this does happen, special function 4 must be run to recover the part of the order which was completed. This is an unintentional limitation which has been corrected in v4.22. To avoid this problem Orders raised in this way will need to be split into 128 line chunks, or raised via the normal order entry screen.

Business
Bookkeeping is concerned with recording the transactions of business. Types of Business Businesses can be organized in different ways. In deciding on the structure the owners will consider matters such as the size of the business and the impact of legislation on it. Sole Trader The business is owned and run by one individual. It is usually small. Legislation concerning accounting matters relates to taxation. Partnership Two or more people carry on a business together. The business can be very large. As with the sole trader accounting related legislation concerns taxation. Company An incorporated business. It is a legal entity in its own right. It must keep accounts in accordance with Companies Act 1985.
Cache memory allocation out of available memory Issue: The following error message is generated when Btrieve is started on a Netware server: 'Cache memory allocation out of available memory'. Solution: This problem occurs when there is not enough free memory to load the Pervasive engine. Ensure that one or more parameters in the BTI.CFG are not set inordinately high. To test the parameters, rename sys:system\BTI.CFG and try to start Btrieve. A new BTI.CFG is created with default values. You can now use a text editor to compare the values between the two BTI.CFG files.

Cash VAT Accounting to Invoice


Changing from Cash Accounting VAT Method to Invoice Method. If you are changing from Cash Accounting to Invoice Accounting it is advisable to do so at the end of a VAT period rather than part way through. You MUST also close any previous VAT periods before entering any new transactions. The procedure for changing is as follows :1. Backup 2. Add credit notes to each customer and supplier to reduce their balance down to zero. Do NOT allocate these transactions. 3. Post the sales ledger day book and purchase ledger day book completely. 4. On VAT set up F5 change the Tax Scheme from "C" to "N". 5. Add invoices to reinstate the customer and supplier balances. 6. Post the Sales Ledger Day book and the Purchase Ledger Day book completely. 7. Allocate the transactions created in step 2 against the transactions created in step 5.

Changing Periods
When changing periods in Exchequer, either the amount of periods or the length of the periods, it is important to consider the following questions; What has been posted so far ? How will changes made to system set-up effect what has previously been posted? Below are two scenarios covering changing periods as examples, but each case should be reviewed separately, as every company has there own special set of circumstances to be taken into account. If you are in any doubt, contact Exchequer Support. Example 1 A new company wants to start trading in November 1997, and for their first year, they want a 14 calendar month year, from then on they want a 12-month year. Set the financial year start as January 1998, then put F6 period to period 11 1997 for November 12 1997 for December, and then period 1 1998 for January. At the end of the financial year (December, period 12/98) draw off 2 sets of accounts, one at period 12/97 and the other at period 12/98. Add these together to produce the first years set of accounts, and from then on you will be able to operate as normal. Alternatively, set the number of periods in the year to 14. As the financial year is ultimately going to be starting in January, you should set financial year start date to January 98 and then switch off 'Set period relative to date'. You will need to manually change the period, starting in November 97 (Period 1/98) for each month until period 14/98 (December 1998). At the end of the year you can continue posting transactions into January 1999 (1/99), and once you are happy with your end of year accounts you should change the number of periods to 12. (If you then need to go back, you will need to change the periods back to 14, to view historical data for example.) You can then switch on 'Set period relative to date'. Example 2 A new company normally runs from January to January, as 13, 4 week periods, how would they do this in Exchequer. They would set number of periods to 13 in system set-up, then at the end of each four week period they

would manually change the F6 period onto the next. In this scenario, set period relative to date, would be better set to NO and show period as month in F6 would also be better set to No so as not to confuse the user. Changing file versions V6.x Non C/S :- Edit BTI.CFG and ensure that the parameter /D: does NOT exist in the OPTIONS line. C/S :- Run the setup utility on the server (6.x is W32MKSET.EXE, P7SQL is W32SSET.exe) {File settings/ create files in 6.x} V5.x Non C/S :- Edit BTI.CFG and ensure that the parameter /D: exists in the OPTIONS line. C/S :- Run the setup utility on the server (6.x is W32MKSET.EXE, P7SQL is W32SSET.exe) {File settings/ create files in 5.x} (This is not available in P7.SQL) Do NOT change to v5.x files version on sites that are exclusively running Exchequer (DOS) and are using Btrieve version 5.x No changes to the database files will be made until the files are rebuilt We do not currently recommend setting files to v7.x format, because there is currently no v7 DOS workstation engine. See also converting v7 files to v 6

Changing from Company to Daily


Change Company Rate to Daily (This is to be avoided if at all possible.)
There are two ways to approach it.

Method 1
1. 2. 3. 4. 5. 6. 7. 8. Do a Total un-post. Un-allocate all currency transactions. There is no need to un-allocate Base Currency (1) transactions. Delete all currency revaluation nominals completely. Edit the Daily Rates to be the same as the Company Rates. Change Consolidation method to Daily. Edit and store each currency transaction. There is no need to edit Base Currency (1) transactions. Re-allocate the unallocated transactions and post. Re-value.

Method 2 1. Finalise your accounts at the end of a period. 2. Install a new company copying all details possible. 3. Set-up as Daily Rate. 4. Take on all balances and stock.

Changing from Daily to Company Rate


Change Procedure - from Daily to Company Rate

1. This must be performed with all users out of the system. All transactions must be posted from all daybooks. And the F6 period should be set to the latest period containing transactions. 2. Take 2 backups of the full Enterprise directory. 3. Print Aged Debtors and Aged Creditors reports for the current period, in consolidated and individual currencies. If multiple debtors and creditors are in use these reports should be run as split by control account. 4. Print 'Full' and Simplified' Trial Balance reports. Ensure both TB reports balance, and that the consolidated currency aged reports posted balances agree to respective GL control account balances, for the last period posted. 5. Perform Currency revaluation for all currencies. All of the Daily and Company Rates should be set to the same as each other and there will be less problems later if the rates are set to the prvailing rates but increased or decreased by .000001. Rerun the reports as 3 and 4 and do the same checks. 6. Change currency consolidation method in system set-up, Daily to Company (need to log in with System Password) 7. Put a suspend on the Nominal Daybook (there should be nothing on the Nominal daybook at this stage so add a blank NOM and put on suspend. 8. Perform a currency revaluation again. Amend all the Company and daily rates to the prevailing rates removing only the .000001 increase or decrease applied in step 5 ensuring that the Daily and Company rates are the same. Then run reports as 3 and 4. 9. As a consequence of changing the currency consolidation method, and by holding back the revaluation NOM (6.), it is now possible that the aged reports no longer agree with the GL control accounts. Note the following: 10. Compare the aged reports posted balances (split by Control account if required), to the Trial Balance Control accounts balances, and note any differences. Review the currency revaluation NOM in the Nominal daybook and note the values posting to the Debtor and Creditor control accounts. Do the postings in the nominal transaction account for the differences between the Trial Balance figures and the Aged Debtors/Creditors listings If Yes, then go to step (11) The values for Creditors and Debtors Control need to be amended such that they equate to the differences noted in step 9. This must be done logging in with the System Password. Care must be taken not to enter the currency field at any time. 11. Take off the suspend and post the Nominal daybook. 12. Rerun the reports including the TB and Aged Creditors/Debtors and check that all agree now. If there are any problems restore from backup and investigate the problems before attempting again. If all is OK, take another backup, then go live with the system. Provisos: There may be differences in the consolidated value of any outstanding foreign currency invoices that had VAT. Under the Daily rate method, the consolidated worth of the whole transaction, net and VAT elements, would have referred to a single daily exchange Rate. Now as a company rate transaction, the

consolidated worth of the VAT value will continue to refer to its Daily exchange rate (as seen in header), whilst the consolidated net value will refer to the latest Company exchange rate. All systems operating the Company method, do not allow un-allocation of transactions which have been re-valued.

Citrix non client server

Citrix Evaluation
The following has been extracted from an internal report. In summary, the following Citrix set-up, where all workstations are terminals that are booting from the server, at present Enterprise will not run successfully with the stand-alone version of Btrieve. Hardware Used in Test Protocols installed A DX4/66 with a single processor and NT3.51 with Winframe 1.6 installed A Diskless WinStation IPX/SPX TCP/IP with IP address manually set

Root Directory S:\ Apps Users directory mapped as U: Program Files User Profiles Users ---------Win32app Winframe Sub-directories ---Andy Bert Sam ----Sbs ----Conclusions Exchequer runs fine using the Null transaction file creation switch in Bti.cfg. A Btrieve engine on a Citrix NT server can only be started once as a service. Workstation settings cannot be configured for each logged in user therefore only one transaction file can be created at any one time. Btrieve does not support host-based environment variable expansion for the User Working Directory therefore mapping would not work. Therefore we concluded that Citrix requires the Client / Server Btrieve engine for Enterprise. Sub-directory ---Sub-directory ---Windows Windows

Updating on Citrix

Commercial Transactions
All businesses engage in commercial transactions. These must be recorded. Bookkeeping is the recording of commercial transactions. Accounting Records The accounting records contain all the details of the bookkeeping transactions. Periodically the information is summarised and accounts are prepared. Management Accounts These are usually prepared on a monthly basis to enable the managers of the business to monitor and direct it's performance. Financial Statements These are prepared annually, mainly for the benefit of people outside the management of the business, such as the owners of the business, Inland Revenue, Banks, customers, suppliers and government. Financial Statements comprise Trading, Profit & Loss Account This summarise the effects of trading, or the financial performance of the business. Balance Sheet This presents a snapshot of the business's financial position at a moment in time. Start of Period ------------------------------------usually 1 year----------------------------------End of Period Opening Balance Sheet Trading, Profit & Loss Account xx xx xx ---xx Less Closing Stock ----(xx) ----Gross Profit Sundry Income Less Expenses Administrative expenses Distribution costs xx xx ---(xx) ----xx xx (xx) Closing Balance Sheet

Trading, Profit & Loss Account for the Year Ended...... Sales Less Cost of sales Opening Stock Add Purchase

Net Profit ----Demonstrates effect of trading over a period of time.

xx

Compass
Compass Released 24th November 1997. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Exchequer Software are pleased to announce the availability of their new configuration and performance utility - Compass. Compass has been developed exclusively for use with Enterprise to aid configuration, measure performance, and highlight stability issues within the environment Enterprise will be running on. It is hoped this tool will highlight potential problems before a site goes live so that the integrity of Enterprise is assured. Compass is strictly a reseller tool available free of charge to authorised resellers and distributors. Use of it is entirely at your discretion. Compass is available for download within the Reseller area on the Exchequer web page from today. The introduction of such a tool is a bold and innovative move which once again highlights Exchequer's commitment to supporting its products. It is understood within the accounting industry the introduction of such a tool is unprecedented, and can be used as a selling aid, demonstrating the professionalism and competence of resellers and distributors. Like all leading edge products it relies heavily on constant feedback from users, so please feel free to email any suggestions or constructive criticism. Please note that there are different versions of Compass for 4.00 to 4.30c and v4.31 and above.

Concepts of financial Statements


1. Concepts underlying the preparation of financial statements. In order to assist the preparers of accounts to decide how to reflect transactions in the financial statements the Accounting Standards Board has in issue # Statements of Standard Accounting Practice (SSAPs) # Financial Reporting Standards (FRSs) One of these, SSAP2, lays down the fundamental accounting concepts on which the preparation of all financial statements is based. 2. SSAP2 Disclosure of Accounting Policies SSAP2 defines four fundamental accounting concepts. These underline the preparation of all financial statements. 2.1 Prudence Concept Revenues and profits are not anticipated. They are only included once the likelihood of their conversion into cash is high. Costs and losses are anticipated. e.g. When including debtors in the balance sheet a provision will be made against any whose recovery is doubtful. Stock is valued at the lower of cost and net realisable value. 2.2 Going Concern Concept. The business will continue in operational existence for the foreseeable future. There can therefore be fixed assets and creditors falling due after more than one year. 2.3 Consistency Concept Similar items will be treated in the accounts in a consistent manner, and the same treatment will be used from one period to the next. e.g. All fixed assets are depreciated.

2.4 Accruals (or matching) Concept. Costs and revenues are matched with each other, as far as their relationship can be established. They are included in the profit & loss account of the period to which they relate, rather than only when they are paid or received. E.G. Cost of sales is the cost of items sold in the period, it is not purchases. FOCUS You should now be able to identify the concepts underlying the preparation of financial statements.

Contra Payments
Contra payments Q: A supplier owes us money and we owe him money. Can we contra the invoices? A: Enter the sales invoice and purchase invoice as normal. Set up a new nominal code in current assets called Contra Payments Account.

This account can be anywhere in the current assets but it has been put inside Debtors in this case It is a balance sheet account.

Contra Payment Receipt Entry


We now enter the receipt, but code to "contra account" instead of bank.

The payment amount is for 525.

Contra Payment Payment Entry


The receipt from the customer was for 1321.25 but we need to post 525 to the contra account and the rest to the bank.

Any outstanding amounts should be coded to the bank on a separate line (i.e. if after contra-ing invoices you still owe money, or they have paid you something.). This method clears amounts outstanding on both supplier and customer ledgers, ensures VAT and nominal accounts are not affected, and is approved by accountants. There is one more step to ensure the contra payments have been correctly cleared.

Contra Payment Reconciliation


You should always check the balance on a contra account is zero clear each debit and credit as on a bank reconciliation so you can identify differences.

These amounts should be cleared and the balance on the contra payment account should always be zero.

Convert Single Currency to Multi Currency

1. Take a back up of the original system!!!! 2. We advise printing a Trial balance, Stock Valuation and Aged Debtors & Creditors Reports. 3. Run Exchequer (Windows), Log into the MCM, select Rebuild, Special Functions and run Special Function 39 (In Dos this is in the Utilities|Data Recovery|Data Files menu). 4. After the conversion is finished, go to the Exchequer directory, and rename the file DEFPF044.SYS to DEFMC044.SYS 5. Run the multi currency upgrade for the version of Exchequer you are converting, for example if the system you have converted was SC/SPOP, then you need to upgrade with MC/SPOP etc. 6. If you are running Exchequer Multi Company Manager you must run the Special Function 39 on all of the companies. 7. Now is the time to consider all the issues you need to be aware of now you are multi currency. Consolidation Method Currency Rates The EMU Revaluation System Control Codes 8. Ensure that the G/L control account for currency variance is set up in the system control codes before attempting to post. The special function had been designed so it should NOT be necessary to unpost/repost. Depending on the volume of data, this will take as long as the purge to run. If the conversion is abandoned/interrupted at any point, you must restore the data before trying again. If you are running non client server, with the 6.15 DOS engine, I suggest the file BTI.CFG is edited and the setting /G:1:1 is changed to /G:500:5000 for better performance during the conversion. It needs to be set back again for normal use. 9. Run a Trial Balance in currency 0 and 1 then run a nominal history report in currency 0 and 1 and reconcile to the TB. This should be completed before any data input is attempted.
Converting 7x files back to 6x format Issue: Can you convert 7x files to 6x format? Solution: Yes, you can convert 7x files to the 6x format. In the Pervasive.SQL v7x Setup utility, select Create File format to version 6x. After required configuration, stop and restart the MicroKernel Database Engine. You can use Butil or File maintenance to create empty files based on the 7x file. The Butil clone and copy procedures are outlined in all Btrieve documentation. With the File maintenance Utility, do a Save As, and then do a Data/Copy. You can also refer to Article number 665. Correcting VAT When doing a partial unpost there will be two questions regarding VAT If your figures have gone into the wrong periods because of a VAT period being closed incorrectly then the reply should be Y to the first question and no to the second. If your totals on the detail report do not agree to the totals then you can do an unpost into the future and say N to the first question and Y to the second. To recalc which period the transactions go into Y N To recalculate the totals then you need to respond N Y To do an unpost to a future period say Y Y.

Crystal Report Previewing a new report: "Exception EOleSysError in Module ENTFUNCS.DLL at 0000C986. Invalid class string." - caused by the OLE Server not being registered. Solution=run EntReg in Enterprise directory. Customer and Supplier lists records missing Problem: Searching list and a customer/supplier is missing? Solution: If the Account is closed it will not appear in the list, re-open it. If not this could be down to possible corruption so rebuild custsupp.dat. Additionally, there is a switch in System set-up, Numeric trader codes if this is switched searching on the name, instead of the code.

it could also be that the list is

598 DDF's will fail when using the DDF Ease "Check Database" option Issue: When using DDF Ease to verify the structure on a good set of DDF's (\pvsw\demodata), DDF Ease may report the files as failing due to inconsistencies with the index or column definitions. Resolution: One reason this may happen is that the external sort path is not set correctly. For example, the external sort path may be set to a non-existent directory. Use the Pervasive.SQL Setup utility to verify the configuration setting for the External Sort File Directory setting of the Scalable SQL Engine, System Configuration component to verify the directory path. See also troubleshooting in ODBC Help.

Daily & Company Rate


Multi Currency, Daily and Company rate required Use the Daily Rate, and set up the currencies you require twice. You will then be able to use the first set of currencies as the normal daily rate for your investments for example, and then use the second set of currencies for cash deposits and treat these as if they were on the company rate. If you adopted this approach, you would loose the facility to view accounts in separate currencies in the normal manner, but could achieve the same result by utilising OLE and designing a spreadsheet.

Database Corruption Novell 4.XX


TITLE: TURBOD.EXE and BTRIEVE Database Corruption TECHNAME: Bryn Coope DATE: 25 June 1997 PRODUCT: Btrieve for Netware VERSION: All, on Netware 4.1x KEYWORDS: Status 2, TurboFatCache, Corruption, Netware 4.1x ISSUE ------------------------------------------------------------------Netware 4.x customers running applications that access Btrieve for Netware report Status Code 2, "The application encountered an I/O error." If the volume with the corrupt file is dismounted, or DOS COPY.EXE is used to copy the file to another name or the same name in another directory, the resultant file is no longer corrupt. In other words, the Btrieve application can be used to successfully access the resultant file without any Status Code 2 messages.

Do not use NetWare's utility NCOPY.EXE to verify this problem. NCOPY uses OS code which gets the file blocks using the turbo FAT. If the turbo FAT is corrupt, copying the file with NCOPY.EXE preserves the corruption. COPY.EXE uses OS code which gets the file blocks from the FAT. Copying the file will bypass the corrupt turbo FAT and use the fat which is not corrupt. SOLUTION The problem is typically seen on NetWare 4.10 and 4.11 file servers with database applications that use large files. Some timing conditions due to multiple client access to a single file can cause the turbo FAT for the file to become corrupt. Apply the TURBODIS.NLM found in TURBOD.EXE at ftp://ftp.novell.com/pub/NetWare/nsd/turbod.exe. TURBODIS.NLM will disable the NetWare Turbo FAT creation thus preventing the Turbo Fat Corruption which will produce the Btrieve Status Code 2 messages. This file from Novell includes two patches: one for NetWare 4.10 and one for NetWare 4.11.

Databases
The Exchequer Databases - Where the data is. CUST\CUSTSUPP.DAT FORMS\PAPRSIZE.DAT JOBS\JOBCTRL.DAT JOBS\JOBDET.DAT JOBS\JOBHEAD.DAT JOBS\JOBMISC.DAT MISC\EXCHQCHK.DAT MISC\EXSTKCHK.DAT Customer and Supplier information. They are separated by C or S they cannot have the same account code. Paper Sizes Job Budgets and Rates of Pay Job Actuals, Retentions and CIS Vouchers Job Records and Tree Structure Employee Records, Job Type database and Job Analysis Records On line help, Passwords, Notes, Matching Information, BOM, BACS, GL and Stock Moves, Cost Centres and Departments. Customer and Qty discounts, FIFO, Serial Number Tracking, Enterprise position and printer co-ordinates,batch payments, auto bank rec., Letters, Links, Return Line Reasons Plug-In settings and screen defaults Data dictionary look up for Report Writer, Visual Report Writer and Form Designer. Database of user designed reports Visual Report Writer - User Security Details Visual Report Writer - Report Tree Stock Tree and Records Stock Multi Location details / Alternate stock data, Telesales, Stock Sales Analysis. EMU Conv. MultiBins. On line balances all balances e.g. Customer Nominal VAT Transaction Headers

MISC\SETTINGS.DAT REPORTS\DICTNARY.DAT REPORTS\REPORTS.DAT REPORTS\VRWSEC.DAT REPORTS\VRWTREE.DAT STOCK\STOCK.DAT STOCK\MLOCSTK.DAT TRANS\HISTORY.DAT TRANS\DOCUMENT.DAT

TRANS\DETAILS.DAT TRANS\NOMINAL.DAT TRANS\NOMVIEW.DAT COMPANY.DAT EXCHQSS.DAT

Transaction Details Nominal/General Ledger Structure Nominal View Structures Company details used by the Multicompany manager and for OLE. System Setup Parameters This file contains all multi currency rates, vat rates, form names and system switches.It also stores all the G/L control codes. Next Document Numbers. Multi Company Manager - Bureau Companies within each Group Multi Company Manager - Bureau Groups Multi Company Manager - Bureau Users Tools Menu and Menu Customisation

EXCHQNUM.DAT GROUPCMP.DAT GROUPS.DAT GROUPUSR.DAT TOOLS.DAT

Dead Orders
If you get orders that will not pick or write off in Exchequer. The solution is zero the quantity on outstanding lines. Add a free type line with Quantity of 1 and write off. Deliver the order. A delivery note is produced but no invoice unless invoice all and consolidate is selected. --Transactions added to enterprise cannot be deleted and must be re used or posted blank. We suggest that a "Dump" or misc. account is used for this, to avoid "cluttering" Customers ledgers. The reason for this is to maintain the Document Audit trail. If we did not you could potentially have 2 Transactions printed for different customers and no record of either.

Delete Exchequer (DOS)


To delete Exchequer from the system cd exch Then delete all subdirectories: cd cust del cust\*.* etc for cust, misc, ms, trans and stock. Check still in directory of exch, then del *.*. Directories will still show but will be empty. This will keep mapping which is important, especially over networks like Novell..

Description lines cost price changing


Background: Costs, on average stock valuation method stock items, are now updated at the time that an order is delivered, following changes to the routine in v4.20. Issue: It is possible that some description only stock items are set to average stock valuation method, and subsequently the lines lose the cost price that was set on the order.

Remedy: Use Last Cost for description only lines. And if you cannot edit the cost price in Exchequer (DOS), change the item in question to a P type, edit the valuation type to F, then change it back again to a D type and you can edit the cost price.

Disable Multi Company Manager


Disable Multi-Company Manager. To disable the Multi-company manager, rename the file 'mcompman.sys' to 'mcompman.sec'. If you then want to re-enable the Multi-company manager, rename the file back to '.sys'. Please remember in Exchequer if you have additional companies installed via the Multi-company manager, you will need to copy all of the executable files (.exe) into the additional companies directory, then set up the respective shortcuts. There is a command line switch '/NOMC' which can be used to disable the multi-company manager when running ENTRPRSE.EXE. I This can be used to setup a system where some users have the multi-company manager and some go directly into companies (using /DIR:).

Display problems in Enterprise


If the 'OK' button has disappeared from a nominal transfer line, it is likely that the display settings are set to large fonts. change the font size to SMALL FONTS to resolve. Also loosing buttons on a batch entry can be due to large fonts. If the screen settings have been altered, and this has caused a problem, go in under SYSTEM password, and under the Help menu there is the option to reset defaults. Backgroud screen logo corrupt ? See release of v4.20b.

Double Entry
Double Entry Bookkeeping is the system used to record the commercial transactions of a business. There are three important principles underlying this system. 1. Dual Effect Every transaction has two effects. Illustration 1. I borrow 250 from Sally. The two effects are. I have 250 in cash. the "having" is an Asset. I owe 250 to Sally. the "Owing" is a Liability. The two effects are equal and opposite they balance. 2. Separate Entity A proprietor and the business are distinct. We look at the business from it's point of view. Illustration 2. I put 1,000 into my business. From the business's point of view the dual effect is It has 1,000 cash Asset It owes me 1,000 Capital A business's liability to it's proprietor is known as capital. 3. Accounting Equation. The first two principles lead to the third, the accounting equation. The balance sheet is based on the

accounting equation. Net Assets Proprietor's Funds = = Assets - Liabilities Capital+Profits(or -Losses) - drawings

1 Fixed Assets Assets acquired for use within the business with a view to earning profits and not for resale. They are normally valued at cost less accumulated depreciation. 2 Depreciation. By their nature fixed assets are intended to last for more than one year. We determine the 'Useful life' of the fixed asset (that is the period over which it will earn profit) and write off the cost of the fixed asset over it's useful economic life. Illustration Mike Baldwin buys a machine, cost 5,000 at 1 January 19x5. It has a useful economic life of 5 years. The cost of 5,000 is 'spread' over 5 years, 1000 per annum. The balance sheet value at 31 December 19x5 is 4,000. The depreciation of 1,000 is treated as an expense. 3 Current Assets Assets acquired for conversion into cash in the ordinary course of business. Current assets include stock, debtors, prepayments and cash. 4 Stocks Goods for resale. They are valued on a line by line basis at the lower of cost or net realisable value. (Selling price less expenses of sale.). Illustration JR buys an oil painting for 300 He could sell it for 450 if he incurred advertising cost of 50. Cost = 300 Net realisable value = 400 Valuation is therefore 300. 5 Debtors People who owe amounts to the business. They are valued at total amounts owed less any provision for doubtful amounts. 6 Provision for doubtful debts If doubt exists about the recoverability of some debtors, then the debtors figure in the balance sheet is reduced. 7 Prepayments These are items paid by a business before the balance sheet date but which relate to the next period. 8 Creditors Amounts falling due within one year. These amounts are owed by the business which fall due for repayment within one year of the balance sheet date. 9 Trade Creditors These are amount payable to suppliers.

10 Accruals These are items owed in respect of expenses incurred before the balance sheet date, but which are unpaid at that date. 11 Net Current Assets This can also be called working capital. It is the sub-total of current assets less creditors due within one year. 12 Creditors Amounts falling due after more than one year. These are amounts owed by the business which fall due for repayment after one year from the balance sheet date. 13 Net Assets The resources of the business.

Duplicated VAT history


Problem with VAT totals on VAT report, possibly duplicated history. Problem definition VAT Input/Output summary figures on the report are completely different to those that print at the bottom of the VAT audit report. Though the figures on the Trial Balance are correct and match the daybooks? If the figures differ it means there has been a problem at some time with posting, or they have lost transactions which made up the totals originally. If you suspect corruption rebuild. They could try partial unpost to a future period not in existence, and get it to recalc the vat totals, this could be a way round it. Suggest they back up etc first,answering Yes to both VAT questions. Try this first, otherwise it is unpost/ repost, but partially unposting to get the Vat totals recalculated is often much quicker. See Correcting VAT

EPOS
Linking to EPOS (Electronic Point of Sale) A link is under development to an EPOS system, this is being developed for Retail only at present via FUTURA Software.
ENTFUNC ERRORS (If you suspect a registry problem, try running ENTREG.EXE as a first step) Error no Meaning 500 Server Error 511 Invalid GL Code 512 Invalid Year 513 Invalid Period 514 Invalid Currency 515 Invalid Customer

516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 600 601-699

Invalid Company Invalid From GL Code AddNomTransfer Invalid To GL Code AddNomTransfer Invalid Cost Centre AddNomTransfer Invalid Department AddNomTransfer Invalid Job Code AddNomTransfer Invalid Job Anal Code AddNomTransfer Invalid Stock Code Invalid Price Band Invalid Value Invalid Supplier Invalid Location Permission Denied - User not authorised to use this function Invalid Document Type Invalid Budget Type Invalid Total Type Invalid Rate Type Record Lock Error Btrieve Errors

Entread FAT32
The latest Windows 98 with FAT32 which is an updated disk o/s that some OEM i.e. not original Microsoft releases have compatibility problems with Btrieve, Go onto the WS and explorer, right click over the hard disk and look at properties, above the pie chart it should say type: Local disk for normal FAT, Local disk (FAT32) for FAT32, on the server it would say NTFS if it is FAT32. Error 5's, and transactions that bring up previous transactions details are typical symptoms. Remedy, restore back-up and go back to old FAT for time being. This does not seem to always be a problem, Genuine Microsoft versions of Windows seem to run with no problems, however OEM versions which have been specifically bound to hardware will not work reliably in FAT32 mode with either DOS Exchequer, or Exchequer Enterprise. Again this issue would only affect sites, where the machine where Enterprise resides is a Windows 95/rel B running FAT32. In our experience this will only happen at smaller sites running Windows 95 as a Windows for Workgroups peer to-peer network. NT3.51/NT4 NTFS is not affected by this issue. There are products on the market like "Partition Magic" from Quaterdeck which will allow a FAT32 system to be reverted back to FAT16 without reformatting the hard disk. Please refer to EntRead for more details.

Entreg
There is a new set of checks on the setup of Enterprise to check the system has been configured correctly. If trying to log into Enterprise any anomalies are encountered the following screen will be displayed. . It is recommended that you tick Fix when the system will offer you the option of reconfiguring the settings. See Setup Help For Further Information
Error 046 This has been known to come up if RW or PRINTSBS.SYS or any other Enterprise file has read only attributes. The access rights to the ENTERPRISE directory must be READ, WRITE, CREATE, MODIFY, DELETE.

This normally indicates that you are attempting to Run Exchequer/Enterprise using the stand alone version of Btrieve instead of Brequest. This Error is the inverse of Error 85 See the section on installing the DOS workstation. or Installing Enterprise Workstation It can also mean that one workstation has accessed Exchequer/Enterprise using the local Btrieve engine, whilst another is attempting to load Exchequer/Enterprise using the Client Server Btrieve Engine. Mixed engines are not allowed on the same data files. Check the Interface section of the MicroKernel Setup program on all Workstations, and make sure they are all attempting to use the same Btrieve engine. This error has also been known to occur on Novell networks where some workstations are using the Novell 32 client, whilst others are using the Microsoft client for Novell. Mixing network clients is to be avoided. This error means that either the number of concurrent users Btrieve is licensed for has been exceeded, or the Active Clients setting on the Btrieve server has not been set high enough. Try increasing the Active Clients using the 10 x number of concurrent users formula, reset the server engine once this value has been changed, and try again. If changing the Active Clients setting does not work, then it may be necessary to purchase more users for the Btrieve engine. Error 161 Running Exchequer from the Multi Company Manager.(MCM) When entering Exchequer (the DOS program) from the MCM the MCM is left open behind the Exchequer and Btrieve considers this as a user. When you have entered DOS you should alt+ tab and close the MCM to reduce the Btrieve user count. 161: The maximum number of user count licenses has been reache

You attempted to open another session when you were at the limit of your user count license. Either close a session or upgrade your user count. . You can use the Monitor utility to determine which users currently have connections to Pervasive.SQL.
Error "Cannot Load MSVCP60.DLL" when entering PCC Title: Error "Cannot Load MSVCP60.DLL" in Pervasive Control Center (PCC) Issue: When you select Pervasive Control Center from the Start menu, you may get the following error - 'Cannot Load MSVCP60.DLL' - making PCC inaccessible. A search for the Visual C++ files required for Pervasive Control Center indicated that they did not exist in the \Windows\System directory. However, all other Pervasive.SQL 2000 client components were installed. Solution: Ensure the virus scanner is disabled during product installation. Then, reinstall the client components to make sure the Visual C++ files are written in the \Windows\System directory. Error 'Cannot Add Pervasive.SQL 7 License to a Pervasive.SQL 7 Server' Title: Error "Cannot Add Pervasive.SQL v7 License to a Pervasive.SQL v7 Server for NetWare" Issue: You may get the following error when you add a User Count license to a Pervasive.SQL v7 NetWare server using the User Count Administrator from a workstation: 'You cannot add a Pervasive.SQL v7 license to a Pervasive.SQL v7 engine'. Solution: Add the license count to the engine from the server prompt. 1. At a server prompt type (assuming the floppy drive is A:): Load NWUCUTIL -da: <enter> 2. When prompted, insert the license key floppy. 3. Stop the engines using SQLSTOP or BSTOP. 4. Restart the engines with the SQLSTART or BSTART command. Error 001 Disk Full Warning I/O Error Cause Exchequer has sensed that there is less than 1Mb of free disk space left on the hard disk. It has therefore disabled the ability to Add a transaction or Customer/Supplier until space is made available. Remedy You must free some space on your hard disk. Try and remove any programs or data that you do not use. if this is not possible you may need to purge some old Exchequer data or purchase a bigger hard disk. DOS runtime error = Invalid function number

Error 002 "A serious data error has occurred, could be corrupt file" This is a serious error indicating that one of your data files is damaged. This can be caused by an unexpected power cut or faulty hard disk. Remedy Rebuild data from within Exchequer but you may loose data. Outside Exchequer not so likely to loose data. If unable to rebuild restore from last backup. also see problems rebuilding I/O Error Or When printing a form perhaps the file specified in system setup is invalid. - Not serious set up form correctly and try again. If this is a Novell 4.xx network, see the following document concerning possible causes of database corruption DOS runtime error = File not found. If Workstations or the server itself are Windows 2000 or XP The presence of the Microsoft QoS Client in network setup has been known to cause continual Error 2s, especially in a non Client Server environment. This is installable on Windows 2000. It is installed and enabled by default on Windows XP Exchequer Software recomends that this is removed fromall PCs including the Server. For further details about QoS traffic control see the MS KB (Q233203)

Error 002 Novell 4.xx The following document is for Technical people, basically it gives possible reasons for previously unexplainable error 2's, and by rebuilding we are effectively copying, and moving files. Additionally Downing the server, and bringing it back up can clear a lot of problems with the FAT ----------------------------------------------------------------------TITLE: TURBOD.EXE and BTRIEVE Database Corruption TECHNAME: Bryn Coope DATE: 25 June 1997 PRODUCT: Btrieve for NetWare VERSION: All, on NetWare 4.1x KEYWORDS: Status 2, TurboFatCache, Corruption, NetWare 4.1x

ISSUE ------------------------------------------------------------------NetWare 4.x customers running applications that access Btrieve for NetWare report Status Code 2, "The application encountered an I/O error." If the volume with the corrupt file is dismounted, or DOS COPY.EXE is used to copy the file to another name or the same name in another directory, the resultant file is no longer corrupt. In other words, the Btrieve application can be used to successfully access the resultant file without any Status Code 2 messages. Do not use NetWare's utility NCOPY.EXE to verify this problem. NCOPY uses OS code which gets the file blocks using the turbo FAT. If the turbo FAT is corrupt, copying the file with NCOPY.EXE preserves the corruption. COPY.EXE uses OS code which gets the file blocks from the FAT. Copying the file will bypass the corrupt turbo FAT and use the fat which is not corrupt. SOLUTION The problem is typically seen on NetWare 4.10 and 4.11 file servers with database applications that use large files. Some timing conditions due to multiple client access to a single file can cause the turbo FAT for the file to become corrupt. Apply the TURBODIS.NLM found in TURBOD.EXE at ftp://ftp.novell.com/pub/NetWare/nsd/turbod.exe. TURBODIS.NLM will disable the NetWare Turbo FAT creation thus preventing the Turbo Fat Corruption which will produce the Btrieve Status Code 2 messages. This file from Novell includes two patches: one for NetWare 4.10 and one for NetWare 4.11. Error 003 File Not Open Cause Exchequer was unable to find one of it's data files. This can be caused if one of the files has accidentally been deleted or if Exchequer has been called from outside it's normal directory. Remedy Make sure you are in the correct directory before running Exchequer. If you are running from the correct directory and still a

problem restore from last backup. DOS runtime error = Path not found. It may simply be that the PC has been idle for an extended period and the network or Btrieve connection has timed out or a network fault has caused the session to be terminated. The ability to browse the network drive using Windows Explorer is no guarantee that this is not the case. Check the Btrieve monitor utility and verify that a connection still exists. The action taken depends on the operation being performed at the time. E.G If posting:Protected mode on. -- restart W/S and try posting again. check Management reports (TB, aging etc). if there is a problem (TB does not balance) It will be necessary to Unpost or restore a backup Error 004 Key Value not Found Cause Corrupted data or program error. Remedy Should be 100 files minimum in config.sys. and if running v5.10 of Btrieve May also need to edit the Rex Batch file to read Btrieve /u:1 /F:128 (Only change the Btrieve settings if FILES= does not work). 1). other software hasn't closed files when exited, therefore not enough room for Exchequer to open all the necessary files; often happens when running Exchequer inside Windows 3.x - need to exit Windows before loading Exch. 2). other software (e.g. windows) has been installed and has modified the config.sys file; 3). config.sys file needs editing to increase files available: (Should be FILES=100 Min.) c:/config.sys ( On a Windows NT / 2000 / XP, PC this file is in a subdirectory on the WINNT(or whatever) Directory SYSTEM32\CONFIG.NT (EG WINNT\SYSTEM32\CONFIG.NT)) Should say FILES = 100 (or more). If server , need to edit files also, see Entread. If Enterprise over an NT network, it could be that NT has not released previous logins, therefore the number of instances on the network could be wrong. Try downing the server to clear.File/Handle Table Full Windows me (Millennium edition). Run the configuration program MSCONFIG.EXE (Start meny / run / msconfig) In the System.ini tab, under the [386Enh] section, add the following entry. PerVMFiles=100 If this Fails Either restore the last good backup or rebuild the file that is giving the error. Error 005 Duplicate Key Value - Also see Error 202,203 and problems with SHARE. This maybe due to crashing when adding a transaction, you may need to move on the next document number and folio number. If a pre-posting report reveals loose lines you may need to run SF4 to collect these up. This should not normally happen with Enterprise and Exchequer v4.24 and above. Run time Error 5 can occur when restoring compressed data onto computer. You need to either uncompress data or restore last backup. If Importing Stock Records check Stock Folio no in system setup is at least 1 greater than the number of stock records including groups. Also, if an error 5 is encountered storing a non-financial document, you may need to use Setafolo DOS run time error = File access denied. Could be file permissions. Error 5 whilst using Exchequer C/S) appears to be related to the internal net numbering numbering not being setup under NT. Symptoms I have a Novell server and a NT4 server both with the v6 Btrieve client server engine, Both Enterprise and Exchequer work fine under Novell, But when I connect to the Exchequer (DOS) that is installed on the NT4 Server, I see the Btrieve requester for DOS

then get error 5. When I try to load Enterprise it is fine and I get a client server connection. Solution The internal network number needs setting up on the NT4 server. See Troubleshooting Btrieve, error 5 in EntRead for more details. Error 006-010 Duplicate Key Value DOS runtime error = Invalid file handle Invalid Key No. See Error 004 The file is most likely corrupt. restart and retry. May need re build or restore Error 012 File Not Found Cause Exchequer was unable to find one of it;s data files. This can be caused f one of the files has been accidentally deleted or Exchequer has been called from outside it's normal directory. Incorrect Network privileges Must have full access to all directories. Including file scan. Remedy Ensure you are in the proper Exchequer directory before running Exchequer. If in the correct directory then you need to restore the last backup. If on the Card System run RSYS.bat DOS runtime error = Invalid file access code. Error 014/015 Pre Image Open I/O Error Cause Exchequer was unable to use an internal file. This Error occurs most often on files that are v5.x format. Having recovered the file/s as Described below, Run Enterprise and go to {help/session information} If this reports that the files are v5.x format it is worth considering a total rebuild, setting the Btrieve engine to maintain files in v6.x format. See Changing File Format Usual causes running v5.10 of Btrieve are disk or directory full or hard disk fault. Could be not exiting correctly from accelerated mode. Could mean that:-The header record for this file is corrupt and it must be rebuilt. From the Exch/Ent path run REXBUILD.BAT and select Rebuild data From there rebuild the file that it is complaining about. If still getting error try deleting the .PRE files Try freeing some disk space and retry the system.. If the error persists you will need to restore the last backup Tip: To find out how much free disk space is available in DOS get to the root of drive (E.G. C:\) and type dir /s This will list all files in directory, and at the end the total disk space used, and disk space free will be displayed DOS runtime error = Invalid drive number. Running v6.x and above of Btrieve, it is likely that a user/server has crashed badly going into Ent/Exch or during heavy file usage and one or more files have a damaged header. The first symptom is that the application seem to hang going in. Give it up to 15 minutes to report the Error then take a backup and use Rexbuild or if the file is EXCHQSS.DAT is not in the same directory as the Program Files, follow the procedure described in 'Rebuild under Multi Company Manager. see Error 14 running Btrieve v6.15 Error 017 Close Error Cause Exchequer was unable to close it's files. Faulty equipment or network fault. Remedy If this happens on a network it is likely the main computer has been switched off or broken down. Reset the whole system

and check the last entries you were working on. If you discover a problem restore the last backup. DOS runtime error = Cannot rename across drives. Error 018 Disk Full Cause See Error 001 Can mean corrupt file. DOS runtime error = No more files. Error 019 Unrecoverable Error Cause This normally means a corrupted file. Remedy Reset the system. If the problem persists follow the procedure for Error 002. On Client / Server sites, this can also be cause by the files being version 7.x format. See Error30 forfurther Intormation. Error 020 Record Manager Inactive Cause Exchequer was run without first running Btrieve. Most common cause is that the W/S is set to run Enterprise or Exchequer C/S mode and the C/S version of Btrieve is not running on the server. If this is a C/S site. On the NT server goto {control panel/services} and verify that the Btrieve database engine (Server edition) is running. On a Novell Server type Modules and look for Btrieve.NLM. Try running Bstart or bringing the server down and restarting. Remedy Use the REX command to run Exchequer. See Trouble shooting Btrieve

Error 021/023 Buffer too short. See Error 006/010 Could also be corrupt file. (rare) Error 024 Page Size Error Cause See Error 020 The Btreive engine has not been correctly set up. Verify the setting in Entread for CS or run a W/S Setup Error 025 Create I/O Error Cause Exchequer was attempting to create a new file over an existing one which is already open. this usually occurs on Networks. Remedy Exit from Exchequer and re boot your computer. If the error persists re-set the entire Network. Error 030 Btrieve Error Not a Btrieve File Cause One of the Exchequer files is corrupt. see Error 002 On C/S sites it could be that the files have been set to v7.x format and Enterprise is now running local mode. You will need to change the files to v6.x format using the C/S engine across the network. See Changing file versions DOS ONLY If Windows 3.11 and Smartdrive present, ensure write caching disabled. Error 35 Printing problems giving this error can be a mapping problem. The shortcut must have a drive in the path e.g. F:\Entrprse and cannot just be \\dir.

This can also be an OLE error. Check the directory that Enterprise is mapped to in the multi company manager as if the data has been moved the the OLE server may be looking in the wrong place for the Ole Server. See Entread Troubleshooting Btrieve ERR35 Note If the server and the PC have the same computer name on the network, when the client server engine tries to load it looks for the client server engine on the first path it finds (The PC not the server) I would imagine that you would be pretty unlucky to come across this one, but it is possible. Error 36 Insufficient number of transactions set in Btrieve set-up. When protected posting is enabled in Enterprise, the Btrieve set-up client / system transactions the transaction setting needs to be 15. Run a Workstation Setup on this PC. Error 042 Btrieve Error Cause Accelerator Mode not closed properly Remedy Try rebuild from outside Exchequer or restore from backup. Should only occur where one or more of the files are v5.x format consider rebuild all file see Changing file Versions Error 043 Invalid Data Record Btrieve Error Cause S/W bug Btrieve trying to redisplay something which has just been deleted. No data loss not serious. Remedy If you delete group in stk in Enterprise you need to exit tree and re enter to avoid error. Fixed in V2.22. v 4.20 If you have not run the conversion from 4.10 to 4.20 and try to edit the module release code you may get this error. If you do, run v410 to v4.20 conversion, with care. On v4.31 + versions contact Exchequer Support for possible down time manual correction Error 047 Maximum Open Files Btrieve Error Cause Exchequer is unable to open some of it's files due to too many files being open already. Incorrect Btrieve settings, In Enterprise run a W/S setup on this PC Remedy Increase the number of files allowed inside your CONFIG.SYS (refer to your DOS manual on how to do this). On a Network increase the number of files on the main server computer and reset the system. set files to 100+ see Error 86 on how to do this. Error 052 Error writing cache Cause see Error 017 Error 057 Expanded Memory Error Cause The expanded memory has become corrupt. Normally caused by another program using the same expanded memory as Exchequer. Remedy Remove any other memory resident program likely to be using expanded memory at the same time as Exchequer - reset the system. Check for "Live" Virus Scanners or /SYSTRAY/ applications(Win95/8/NT) that may be corrupting memory. Error 058. Compression buffer too short. In v3.00 Exch, this could be that Btrieve has been started without /u:1, and v4.XX check BTI.CFG Error 059 File Already Exists Cause See Error 025 Error 078 Deadlock Detected Cause A network conflict has caused 2 screens to wait for the same information.

Remedy Refer to your network supervisor and reset one of the screens. Decide which screen is performing the Least "active" task. I.E. if one is viewing a ledger or transaction and the other is processing a Daybook. Reset the one that is viewing. Restart and check the record/transaction that was being worked on at the time. Error 080 Record Locked Cause Conflict record changed by another workstation since read. This may be a temporary fault in a multi user network, another screen may be locking the record fault. Check any operation on both screens has actioned correctly. Escape out only a warning not a

Also note that a number of record locking errors over networks, giving error 80, were resolved in versions later than v4.10a.

Error 081

Lock Error - Cause Exchequer attempted to unlock a record which was not locked.

Remedy for Exchequer (DOS) - New Btrieve not running properly (it needs 4Mb extended RAM) Run Rex510.bat instead which uses old Btrieve or get more extended memory. Also could be SHARE not running /L:50 in Autoexec.bat Remedy for Enterprise (1)Btrieve is unable to lock any more records because it has run out of space to store details of new record locks. The maximum number of locks Btrieve can handle can be altered See Troubleshooting Btrieve for how to increase the locks. run a Workstation install on this machine as a first step. (2) There is also a setting inside the Btrieve Setup:FILE SETTINGS|DELETE LOCK FILE. This should be set to OFF on non C/S Enterprise Btrieve engines, as it can cause error 81. This may have been the cause at One Site, and it would be worth verifying with them if it is still set to ON. As I understand it the .LCK files are temp. files Btrieve uses to indicate a file is in use, I guess if two W/S attempted to delete it simultaneously it would cause problems, so by default we should not allow these files to be deleted as they are harmless. On NT Workstations this is generally file handles. In the WINNT (or whatever) Directory there is a sub DIR SYSTEM32, need to Edit CONFIG.NT and ensure there is a line 'FILES=100'.. (This mostly effects Exchequer (DOS). Error 082 Maximum files in use Cause Too many files in use. See Error 86 on how to fix. Remedy Check number of files allowed in config.sys file. Run a WS install on this PC as a first step. Error 084 Record or Page Locking Cause Btrieve 6 Locking files Remedy all other users out of the system should clear problem. If running over a network also see possible problems with SHARE. (NOTE: Windows Workstations use VSHARE in the [386Enh] section of the System.INI file). Error 085 File Locked Cause Two screens on Exchequer attempted to open exchequer files at exactly the same time. This can sometimes cause a problem It could also be due to running in accelerated mode. (Exchequer) Remedy Reset your screen, if the problem persists reset the network and try going in one at a time. If you crash in accelerated mode you will need to restore last backup. If a Client Server Site has users in the system using the Local Engine and another user attempts to run Enterprise in Client Server Mode then Error 85 will occur. This Error is often the inverse of Error 46. Get all users out of Enterprise and log them in one by one until ERROR 46 or 85 occurs. then investigate the Btrieve settings for C/S local on this PC. this should be Local=No, requester=Yes. Although they may both be set to Yes. If one PC consistently gives this Error, it would indicate that it has a network connection problem. (Network

settings, address, Fault cable or network card). Error 086/087. File/Handle Table Full Cause There are too many files for Exchequer to open at once. ERROR 86 on Client server is usually the 'file settings,, Open files' section of Btrieve setup is too low Refer to Entread For how to set this on Novel and NT Windows95/98 Remedy Should be 100 files minimum in config.sys. and if running v5.10 of Btrieve May also need to edit the Rex Batch file to read Btrieve /u:1 /F:128 (Only change the Btrieve settings if FILES= does not work). 1). other software hasn't closed files when exited, therefore not enough room for Exchequer to open all the necessary files; often happens when running Exchequer inside Windows 3.x - need to exit Windows before loading Exch. 2). other software (e.g. windows) has been installed and has modified the config.sys file; 3). config.sys file needs editing to increase files available: (Should be FILES=100 Min.) c:/config.sys ( On a Windows NT / 2000 / XP, PC this file is in a subdirectory on the WINNT(or whatever) Directory SYSTEM32\CONFIG.NT (EG WINNT\SYSTEM32\CONFIG.NT)) Should say FILES = 100 (or more). If server , need to edit files also, see Entread. If Enterprise over an NT network, it could be that NT has not released previous logins, therefore the number of instances on the network could be wrong. Try downing the server to clear.File/Handle Table Full Windows me (Millennium edition). Run the configuration program MSCONFIG.EXE (Start meny / run / msconfig) In the System.ini tab, under the [386Enh] section, add the following entry. PerVMFiles=100 If this Fails Either restore the last good backup or rebuild the file that is giving the error. Error 094 User tried to open/create a link in a directory without proper access rights. (User needs read/write/create/delete) The application encountered a permission error. you can receive this status code in the following situations; 1)The application tried to open or create a file in a directory without the proper privileges. The MicroKernel Database Engine does not override the network privileges assigned to users. 2)The designated server is in the server routing table, but your particular workstation is not logged into that server. 3)Both the server-based and workstation MKDEs (versions earlier than 6.15) are trying to access the same file at the same time. 4) Also see Error 94 on Novell v4.xx client server installation for possible issues with the NetWare Runtime server. And Error 94 on Windows NT/95. 5)Ensure latest patches are applied. Including Network Client 6) The Server is NT technology and the 'Everyone' Group does not exist. Create the group and give all users at least List and Read Aceess to the Enterprise Directory. On Client-Server Sites Try running Entreg.exe and reconfiguring the B.trieve Engines.

See also Pervasive.SQL 2000 and Windows 2000 and Status 94 is occurring on client machines even though user has appropriate rights
This is a Privileges issue of some type Winsock Error 10049 with NT 4.0 SP4 Applied Issue: The WINSOCK.DLL and WSOCK32.DLL from Windows NT Service Pack 4 may return Error 10049 because of a defect in

NDISWAN. NDISWAN services is returning addresses not bound to TCP/IP when the Window Socket application makes a GetHostByName socket call. Resolution: For complete details see Article Q217001 on Microsofts Support knowledge base. This article references the fixed component RNR20.DKLL's date and size. Article ID#: FYI00607 ModifiedDate: 15 February 1999 Server: Windows NT 4.x ServerVersion: Client: Cross-Platform ClientVersion: Error 101 DOS runtime error = Disk write error. Usually Disk Full see error 001. Over Networks this could be the client reporting the disk space incorrectly. The Novell 32 client can have this effect, also if the workstation concerned was previously the Novell 32 client, Windows add and remove programs, may have left some residual files that still report the disk space incorrectly. try re-installing the client, or re-install Windows. Another possible reason is that the memory is being managed through Windows 95, DOS box memory should be set automatically. In Enterprise/Exchequer v4.31 on, can also be caused by the absence of a SWAP. This directory must exist for each Enterprise data set. Dos runtime errors 102 103 104 105 106 File not assigned File not open File not open for input File not open for output Invalid numeric format

Error 11 Exch Client Server under NT/95


(Extracted from Pervasive's Tech Talk) Title: Running the DOS Requester from Windows NT Product: Version: Btrieve for NetWare and Btrieve for NT, Server Engines v6.15.x Date: February 13, 1996

Issue: What do you need to run a DOS application from a Windows NT command prompt using the Btrieve DOS Requester? Solution: NW16.EXE and VWIPXSPX.EXE must be loaded prior to loading BREQNT or BREQUEST. We recommend you load them from AUTOEXEC.NT. These files are located in the WINNT35\SYSTEM32 directory. You can also install them from your NT Installation CD. Use the network icon from the control panel to verify NWLink IPX/SPX compatible transport is installed. You can use the add software button to install this software. From the DOS command prompt, load BREQNT or BREQUEST. --------------------------------------------------------------------------------------------------------

Title: WFW Setup for DOS Applications Product: Btrieve for Windows NT Version: 6.15 Date: 6/30/95 Issue In order to run a Btrieve DOS application in client/server mode and target a Windows NT server from a Windows for Workgroup workstation, you are required to use BREQNT.EXE. This requester requires a full redirector in order to function correctly. A WFW DOS box is a full redirector by default, but in a straight DOS Client mode, you must use NET START FULL to load a full redirector. (If you do not use NET START FULL, the DOS workstation will return a status 11.) To verify the mode of the redirector, type the command "net ver". This will tell you if the redirector is running in "basic" or "full" mode. The list of what needs to be loaded at a DOS workstation to connect to a Windows NT server is as follows: In autoexec.bat LSL.COM LAN Card Driver IPXODI.COM NET START FULL In config.sys IFSHLP.SYS You can load most of these drivers high, using emm386. LSL.COM, LAN Card Driver, IPXODI.COM, IFSHLP.SYS, and most of NET START FULL will load in upper memory. You do not need to load NETX if you are not connected to a NetWare server. Please note that you may run into some problems using Microsoft SPX protocol stack instead of NetWare SPX protocol stack.

Error 14 running Btrieve v6.15


A Status 14 (Pre-Image Open Error) indicates that Btrieve thinks that a file should have a pre-image file available to rollback on the Btrieve open call. If the pre-image file does not exist then Btrieve cannot open the file. What is the best procedure for recovering from a status 14? Our rebuild module should recover it ok, but the 'records stored' detail will show as zero, so you will need to make an educated guess as to whether any files are missing or use BUTIL as detailed below; Before doing anything make a copy of the file to a safe location. 1) Create an empty pre-image file. If the Btrieve file is CUSTOMER.BTR create a file named CUSTOMER.PRE. Using a Btrieve utility (BUTIL,BSIM,B), open the file. If this creates a status 15 (pre-image i/o error) follow step two.

2) Using a hex debugger, such as DEBUG, change bytes HEX 22-23 and HEX 2C-2D to 0. Try step 1 again, to attempt to open the file. Note: Doing a BUTIL -STAT on the file will open the file. Once the file can be opened it will need to be recovered, but you should be able to use BUTIL-STAT to establish the number of records. See other rebuild utilities on how to use BUTIL to recover a file.
Error 200/201 Usually corrupt data or program fault. Try rebuilding or restore backup. DOS Critical Error 200 Division by zero / 201 Range check error. Error 201 If adding a transaction, could be corrupt DEF*.sys system file (try restoring this file or get it from last upgrade disk) copy the TXFR.exe into a temporary directory, taking it from the upgrade disk, run it to release the files and copy the relevant ones into the exchequer directory. Also see issues regarding Pentium2.(Err 200) and check the date format on the PC has not been switched to american format. Error 201 not getting into Exchequer/Enterprise check system date is not greater than 31/12/2049. In Enterprise with multiple companies running from MCM and attempting to run Exchequer (DOS). This Error can also indicate that the data Directory contains invalid or out of date *.DEF files. Copy these files from a company that runs OK. Error 202. Stack Out of stack memory Run time error. Caused by "finding" lots of codes in nominal ledger and not escaping back in between. A: Reset machine and remember to escape between hot keys/finding. If running v5.10 of Btrieve you could run by using the REXLO batch file to call Exchequer. It uses less memory. ( You would need to call REXLO on all workstations). Copy Rex - Rex615, Redo Rex (cannot run old Btrieve if Enterprise) See Memory Errors Error 204 DOS Critical Error Invalid pointer operation. Error 203

DOS Critical Error Heap overflow error.


Not Enough memory. For example trying to print stock record when drilling down, and can depend on how many other hot keys were in use at the time of printing, better to use find whilst in the stock tree instead of drilling down all the way.See Memory Errors Exchequer (DOS) needs at least 540-560k free DOS memory to run. Error 205/207 Usually corrupt data or program fault. Try rebuilding or restore backup. Dos runtime errors 205 Floating point overflow 206 Floating point underflow 207 Invalid floating point operation

DOS Critical Errors

210 Object not found 211 Call to abstract number 212 Stream registration error 213 Collection index out of range 214 Collection overflow error 215 Arithmetic overflow error 216 GENERAL PROTECTION FAULT.

Error 91 & 97 on NT
(Extracted from Pervasive's Tech Talk) Title: Setting the IPX Internal Network Number Product: Btrieve for Windows NT Server edition Version: 6.15 Issue / Problem If the workstation hangs on the first attempt to access a Btrieve file on the NT server or the Btrieve requester returns status 91 or 95 to the application when attempting to open a Btrieve file make sure the IPX Internal Network Number on your NT server is set to a non zero value. Solution 1) Set "NWLink IPX/SPX Compatible Transport" frame type to manual mode (select at least 2 so that the internal network number remains set). 2) Set the Internal Network Number to a unique non-zero value if you have not done so already. 3) Restart the server. 4) You can go back to "NWLink IPX/SPX Compatible Transport" configuration and remove the extra frame type. Restart the server again. Run IPXROUTE CONFIG from server's DOS prompt to verify that the internal network number is non-zero. It is necessary to choose two frame types in order to set the internal network number. However, once you set that value, you need to remove the extra frame type. Note: IPXROUTE CONFIG, a Windows NT utility run from a DOS box, displays the Internal Network Number (if set), as well as all other bound networks with associated network numbers and frame types. ---------------------------------------------------------------------------------------- -------------------------------------Title: Status Code 91 with Btrieve for Windows NT, Server Edition Product: Btrieve for Windows NT, Server Edition Version: 6.15 Date: February 7, 1996 Problem:

You may receive a Status Code 91 from your workstation when attempting to target a Btrieve for Windows NT Server using the Btrieve Requesters. In some situations, the workstation may appear to hang instead of returning a Status Code 91. This may happen when the network frame type that SPX uses on the Windows NT Server does not match the network frame type that SPX uses on the workstation. Network frame types on the Windows NT Server are specified in the Control Panel, Network, NWLink IPX/SPX Compatible Transport dialog box. Network frame types on a Windows for Workgroups workstation are specified in the Network Setup, Drivers, IPX/SPX Compatible Transport, Setup dialog box. Network frame types on a DOS workstation using the Novell ODI drivers are specified on the Protocol IPX entry of the Link Driver <network card> section of the NET.CFG file. Solution 1. Determine which network frame type your Local Area Network is using. In most cases, this is either 802.2 or 802.3. 2. Set "NWLink IPX/SPX Compatible Transport" to Manual Frame Type Selection and select the appropriate frame type. Select only one frame type. Do not use Auto Frame Type Detection. 3. Restart the server. 4. Restart the workstation and retry the Btrieve operation(s). 5. If the problem persists, configure the frame type at the workstation. For Windows for Workgroups workstations, specify the correct frame type via the Network Setup, Drivers, IPX/SPX Comparable Transport,Setup dialog box. For DOS workstations using the Novell ODI drivers, specify the correct frame type on the Protocol IPX entry of the Link Driver <network card> section of the NET.CFG file. 6. Restart the workstation and retry the Btrieve operation(s). -------------------------------------------------------------------------------------------------------Title: Status Code 97 with Btrieve for Windows NT Server Edition Product: Btrieve for Windows NT, Server Edition Version: 6.15 Date: February 7, 1996 Problem: You may receive a Status Code 97 when attempting to target a Btrieve for Windows NT Server using the DOS Requester. The problem usually occurs because the Windows NT IPX/SPX driver is sending larger network packets than the Btrieve DOS Requester is able to receive. Solution: Two methods exist to force the Windows NT IPX/SPX driver to use a network packet size that the Btrieve DOS Requester can receive.

The first method is to set the IPX/SPX MaxPktSize in the Windows NT REGISTRY to 576 decimal or 240 Hex. To reach the MaxPktSize, run REGEDT32 and take the following path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\ Services\ NwlnklPX\NetConfig\ <LANDriver Name>\ MaxPktSize You can find more information about modifying MaxPktSize in the document NETWORK.WRI on the Windows NT v3.51 CD. Modifying MaxPktSize affects all IPX/SPX sends from the Windows NT server. The second method is to set the VirtualNetworkNumber in the Windows NT REGISTRY to a non- zero value. To reach the VirturalNetworkNumber, run REGEDT32 and take the following path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NwlnklPX\Parameters\VirtualNetworkNum ber You can also reach the VirtualNetworkNumber as the Internal Network Number shown in the Control Panel, Network, NWLink IPX/SPX Compatible Transport dialog box. *Running the NWLink IPX/SPXCompatible Transport dialog box can reset the VirtualNetworkNumber to zero under some circumstances. Setting the VirtualNetworkNumber apparently only affects the size of the SPX network packets. Workstation Hang ---------------If your workstation hangs on the first attempt to access a Btrieve file on the Windows NT Server or the Btrieve Requester returns a Status Code 91 or Status Code 95 to the application when attempting to open a Btrieve file, ensure the IPX Internal Network Number on your Windows NT Server is set to a non-zero value. Follow the steps below to set the IPX Internal Network Number: 1. Set "NWLink IPX/SPX Compatible Transport" frame type to manual mode (select at least 2 so that the internal network number remains set). 2. Set the Internal Network Number to a unique non-zero value if you have not already done so. 3. Restart the server. 4. From the "NWLink IPX/SPX Compatible Transport" configuration, remove the extra frame type. 5. Restart the server again. 6. Run IPXROUTE CONFIG from the server's DOS prompt to verify that the internal network number is non-zero. You must choose two frame types in order to set the internal network number. However, once you set that value, you must remove the extra frame type. Note: IPXROUTE CONFIG, a Windows NT utility runs from a DOS box, displays the Internal Network Number (if set), as well as all other bound networks with associated

network numbers and frame type

Error 91 Server Error


The following document was obtained via Pervasive Softwares Tech Talk; Title: Status 91 Using the OS/2 NetWare Requester With Token-Ring Document ID: BTR-97081801 Reference ID: N/A Creation Date: 18 August 1997 Modified Date: 08 September 1997 Document Revision: 1.02 Product: OS/2 NetWare requester for OS/2 Btrieve and Btrieve for NetWare Version: 6.15 Environment: OS/2 and WINOS2 Category: Status: Verified Access: Public Author: Don Hedding Keywords: OS/2 NetWare requester, WINOS2, Status Code 91, Token-Ring ISSUE --------------------------------------------------------------------A Btrieve application running on an OS/2 workstation configured with the NetWare OS/2 requester may receive a Status Code 91, "Server Error," in a Token-Ring environment. SOLUTION -----------------------------------------------------------------Add the following to the NET.CFG file on the OS/2 workstation: Link Support buffers 14 4210 Log out of the network and log back in after adding this to the NET.CFG file.

----------

Error 94 Client Server Novell v4.xx

As well as the issues discussed in Entread such as clients and invalid paths, if you still continue to get error 94 when installing onto a Novell v4.xx check the user name, and refer to error 99 in Entread, as the following situation may have occurred, if the Netware Run time server support is enabled (/C:1). The application tried to access a file using NetWare runtime support with the specified username. Specifically, one of the following situations exists regarding the supplied username; -The user is not a valid user on the NetWare Runtime server. NetWare runtime is a Novell product that was made available with client/server NetWare SQL v3.0. NetWare Runtime is not available through Btrieve Technologies. -The user does not have the appropriate rights to access the file. -The username is ADMIN or SUPERVISOR. For security reasons, the MKDE does not enable you to use ADMIN or SUPERVISOR as a username when enabling NetWare runtime support. Set up a user who has full access rights to the Enterprise directory, and log in as that user, from a fresh boot. This issue applies to client server versions of Btrieve only running on Novell. One of the reason that this used to happen was that the version 6 requesters for Btrieve were not NDS aware and therefore a error 94 (Permission error) would sometimes occur. If the client is using the Pervasive SQL7 Client server engine they should upgrade Enterprise to at least 4.30b as this version of Enterprise has the option under the upgrade of using the version 7 requesters. Please note that if you are using the Btrieve version 6 client server engine you should continue to use the version 6 requesters

Error 94 on NT/95
(Extracted from Pervasive's Tech Talk) Title: Status Code 94 Using the 32-bit Btrieve Requester

Product: Btrieve for NetWare Version: 6.15.x Date: February 13, 1996 Problem: You may receive Status Code 94 (permission error) when using the client/server Btrieve for NetWare with the 32-bit Btrieve Requester for Windows NT/Windows 95. Solution: 1. The 32-bit requester always uses the MicroKernel Database Engine's runtime server support to check a client's rights to a file. To do so, it uses the username used to log in to the preferred server or to log in to the workstation to verify if the client has the proper rights and privileges to access the Btrieve files on the targeted Btrieve server. You must ensure that the username you use to log in to your workstation or to log in to the preferred server exists on the Btrieve server, and that user must have the appropriate rights to access the files.

For example: Login name USER1 Log in to the workstation, preferred server, and Btrieve server using Login name USER1. As long as USER1 has the proper privileges to the Btrieve files, the file access is successful. II. Login name USER1 and USER2 Log in to the workstation and/or preferred server using Login name USER1. Then log in to the Btrieve server using Login name USER2. USER1 does not exist on the Btrieve server, so the Btrieve operation fails and you receive a Status Code 94. 2. If the 32-bit communication module, W32BTICM.DLL (formerly known as NTBTICOM.DLL), is missing from the path, the Btrieve Requester returns Status Code 94 to the application. 3. If Limit Concurrent Connections is set to Yes and Maximum Connection is set to 1 on a Novell Server using the Account Restriction Option under Syscon, the requester returns Status Code 94 to the application. The Maximum Connection must be set to at least 2. The reason for this behavior is the 32-bit Btrieve Requester uses the NetWare Runtime Support. Therefore, the MicroKernel Database Engine performs a Login using the username and password passed to it via the 32-bit Btrieve Requester. This means the user must have permission to at least two concurrent logins to the NetWare server.

Error 95 on NT/95
(Extracted from Pervasive's Tech Talk) Title: Status Code 95 with Btrieve for Windows NT (Server Edition) Product: Btrieve for Windows NT, Server Edition Version: 6.15 Date: February 7, 1996 Problem: You may receive a Status Code 95 when attempting to target a Btrieve for Windows NT Server using the Btrieve requesters. The problem is usually the result of the SPX drivers changing network frame types when trying to resend a network packet. Solution: 1. Determine which network frame type your Local Area Network is using. In most cases, this is either 802.2 or 802.3. 2. Set "NWLink IPX/SPX Compatible Transport" to Manual Frame Type Selection and select the appropriate frame type. Select only one frame type. Do not use Auto Frame Type Detection. 3. Restart the server.

4. Restart the workstation and retry the Btrieve operation(s). Several larger NT client server sites have been experiencing frequent Btrieve error 95's whilst attempting to log in to Enterprise after 15 users had already logged in. This particular cause of error 95 is cured by increasing the SESSIONS parameter within the Microkernel setup program on the server itself. The SESSIONS value is accessed by altering the top combo box to BTI COMMUNICATIONS SERVER. A recommended value of 10 x the number of concurrent users should be applied. See also Error 95 on Token Ring

Error Log
Error Log from v4.20
V4.20 sees the introduction of error logs to aid support in both Exchequer and Enterprise. Every time an error message is displayed,an entry is made into an error log file. This error log can be viewed via system setup under daily password control. In addition, the error log also records any users who crash out from Exchequer or Enterprise. In support situations where data has become corrupt, you should immediately check the error logs to see which error messages have been occurring, when and by which user.

If you view the error log with other users logged in you may be misled to believe they have not exited correctly. This is because as soon as a user logs in the error log is created, and the error log is then removed as the last part of the exiting procedure. (once all the files are closed) Your own error log that is created when you log in will be hidden from you. Therefore when viewing error logs ensure all users are out of the system.

All Btrieve errors and Exchequer errors as well as Exception errors are logged and the details can be printed. The only exception to this could be running Exchequer through Windows 3.1 when Windows runs out of resources, as there may not be enough resources to write the log. The error logs are stored in a 'Logs' subdirectory. And they can be viewed from outside of Enterprise or Exchequer by opening them with a text editor of your choice.

However, we would suggest that the ability to view the error logs externally is not brought to customers attention as they are less likely to delete them if they do not know where they are. Additional Q: Exchequer directory disappearing? A: We suspect this is because the user does not have the correct access rights over the network. (They

need read/write/create/delete) And the problem revolves around the 'LOGS' directory, not being created. As it cannot be created Exchequer is trying to set the directory's hidden attribute, and is failing to do this, in effect changing the Exchequer directory's attributes instead. To remedy this situation change the attributes of the Exchequer directory back, and ensure users have the correct access rights.

Error Problems with SHARE


The following applies to Exchequer DOS only. ERROR 5s + 84s on networks are often caused by Multiple copies of SHARE running I.E. Vshare in Windows and SHARE.EXE in Autoexec.bat use one, or the other but NOT both. In Autoexec.bat check the line Share /L:50 is present if stand alone machine. Also it is preferable only to run Share on the File server machine only. If they are sharing printers, this has been known to cause Datafile Corruption when using Peer-Peer networks. Set the printers to only print locally and see if this improves. NOTE: Windows Workstations use VSHARE in the [386Enh] section of the System.INI file. Therefore the above refers to DOS only. For Win95/8/NT/2000 refer to Btrieve SET-UP that relates to the WS opperating system. (See Entread "Trouble shooting btrieve") Types of Error I/O Error These are not generally very serious and indicate problems reading file such as Document Layouts. The system will continue to operate but may be unable to print some layouts. Run time These errors are serious in that Exchequer/Enterprise has found a problem internally which it cannot solve and will therefore stop the program. The most common cause is insufficient memory. Fatal These are very serious errors which may simply cause the system to freeze forcing you to reset your computer. they generally indicate a problem with memory or equipment. Btrieve These errors are related to the data Exchequer/Enterprise is handling. They range in severity, but will generally not stop the program from running, just simply prevent it from performing certain functions.

Error list
Also see: Application Error Ole Error on NT History/Graph Crashes Keyboard Hanging Error logs Error Types Memory Errors Stream Error Exception Errors/Access Violations and General Protection Faults Login Errors Crystal Report IO Error reading in Printer Definitions Unknown Form printing statements Purge Errors. O/S Bugs on Ver 4.21 Winsock Error 10049 Btrieve Errors Errors Messages upgrading v4.30c and above

See also troubleshooting Enterprise and troubleshooting Btrieve Error 001 Disk Full or Invalid Operation No. Error 002 I/O Btrieve Data File Damaged Error 003 File Not Open Unable to find a file. Error 004 Key Value Not Found Corrupt Data or Prog Error Error 005 Duplicate Key Value - ( Could be that Stk Records were Imported) Error 006/010 Duplicate Key Error 007 'Different Key No. to Prev Operation Error 008 Invalid Positioning... Update/Delete called before positioning Error 009 End of File Reached.. attempt to read beyond EOF marker. Retry the operation. Error 011 Invalid path. See Entread helpfile-and ensure latest Btrieve patches are applied. Also see Error 11 running Exchequer Client Server under NT Error 012 File Not Found Error 014/015 Unable to use an internal File Disk Full or Hard Disk Fault. Error 016 DOS runtime error =Cannot remove current directory. Error 017 Close Error Faulty Equipment or hard disk fault. Error 018 Disk Full or could be corrupt data. Error 019 Unrecoverable Error Corrupt File Error 020 Record Manager Inactive Btrieve not run before Exchequer Error 021/023 Key Buffer too Short see 005/010. Error 024 Page size Error see Error 020. Error 025 Create I/O Error Error 030 Not a Btrieve File File Corrupt see Error 002. Error 035 Mapping problem related to printing Problems Error 036 Btrieve settings Error 042 Accelerated Mode not cleared properly. Error 043 Invalid data Record. Error 046/088 See Entread conflicting Btrieve versions or incomplete access rights to a file. Error 047 Maximum open files. Config.sys. Error 051 The owner name is invalid Error 052 Error writing cache see error 017. Error 057 Expanded Memory Error Error 058 See Entread helpfile- Trouble shooting Btrieve Error 059 File already exists see error 025. Error 078 Deadlock Detected. Error 080 Record Locked Error 081 Lock Error Btrieve 6.15 not working correctly. Error 082 Files Problem Error 084 Record Locking in Btrieve 6.15 Error 085 File Locked could be Accelerator Mode. Error 086/087 File Handle Table Full Btrieve /F:128. Error 088 Possible Btrieve conflict see Entread Error 091/097 See Trouble shooting Btrieve, Server Error also see IPX issues on Win NT Error 094 No Access Rights on network. Error 095 See also Entread helpfile- Trouble shooting Btrieve, and IPX issues on Win NT Error 096 Active Clients on Btrieve not set correctly. Error 099 See Entread helpfile- Trouble shooting Btrieve Error 100 DOS runtime error = Disk Read Error Usually layout .DEF or .LST files. Error 101 Unable to write to file. Error 102/106 DOS Critical Errors Error 132 The file has reached its size limit Error 150 DOS Critical Error Disk write protected usually disk full. Error 151 DOS Critical Error(Bad drive request struct length) Error 152 DOS Critical Error Lost network connection (Drive not ready) Error 154 DOS Critical Error CRC error in data. Error 156 DOS Critical Error Disk seek error.

Error 157 DOS Critical Error Unknown media type. Error 158 DOS Critical Error Sector not found. Error 159 DOS runtime error = Printer out of paper. Error 160 DOS runtime error = Device write fault. Error 161 DOS runtime error = Device read fault. Error 162 DOS Critical Error Hardware failure lost connection. Error 200/201 Run time Error Corrupted data or program fault. Error 202/204 Stack overflow Error not enough RAM memory to run program. Error 203 Heap overflow error Not enough memory. Error 205/207 Run time Error Corrupted data or program fault. Error 208 Overlay Manager not installed. Check network connection. hardware error. Error 209 Overlay File read error. Check network connection. hardware error. Error 210/216 DOS Critical Errors Error 217 DOS Critical Error. usually occurs under Win95 original edition Error 500 Server Error Error 511 Invalid GL Code Error 512 Invalid Year Error 513 Invalid Period Error 514 Invalid Currency Error 515 Invalid Customer Error 516 Invalid Company Error 517 Invalid From GL Code AddNomTransfer Error 518 Invalid To GL Code AddNomTransfer Error 519 Invalid Cost Centre AddNomTransfer Error 520/600 Entfunc OLE Errors

Error

601/699

OLE Btrieve Errors

Error 1002 Error 2001

See Entread helpfile- Trouble shooting Btrieve & Install/ Upgrade Errors v4.30c + See Entread helpfile- Trouble shooting Btrieve

Error when disconnecting first client in client list using DTI Title: Error Disconnecting First Client with Distributed Tuning Interface Issue: When you attempt to disconnect the first client in the client list using Distributed Tuning Interface (DTI), you may get error 7010. This is a catch-all error and has no real meaning in this situation. Solution: This is currently entered as defect 19300. Use the Monitor utility to disconnect all clients.

Euro Symbol
The Euro symbol is available for windows 95 from http://www.microsoft.com/windows/euro.asp this has a patch for Windows 95 and Windows NT 4.0 so the Euro symbol can be accessed in Arial and MS Sans Serif. The keyboard shortcut is ALT + 128, Windows 98 already has it in there. How to add the Euro symbol into Enterprise. In order for your printer (Laser or ink jet only) to print the symbol you need to go into the printer set up , select the fonts option and choose "Download TrueType fonts as bitmap softfonts". EuroEquivalent figures in DOS If you want to display the euro equivalent of say the invoice total:Add a field on the .DEF file in the position you want the value to appear just as you would any normal field. In the .LST file instead of just putting &I110 (which is the variable for invoice total) add the line

!X &I110 &I009 7 R 2 in Exchequer DOS. !X &THTOALU 7 R 2 For PCC Form in Enterprise. Where:!X VVV FFF TTT JJJ DD ! = special form definition function X = currency conversion function. (There are presently no others, but we are allowing for more of these in the future) VVV = is the value of the amount to be converted, this can be a field like &I110/THTOTALU FFF = is the currency we are converting FROM. In this case we are using &I009/THCURR which is the invoice currency number. You can also hard code a value. Please also note this must be currency number, not symbol. In most cases for invoices &I009/THCURR will suffice. For statements which generally are in currency 0, you would hard code this to currency 0. TTT = is the currency number we are converting TO. In this example the euro has been set as currency 7, again you can hard code a value or use a field, in most cases this will be hard coded. JJJ = is the justification command R/L/C. Can be left blank. DD = is to force the number of decimal places. Can be left blank. If Using PCC forms in Enterprise then the field names are of course the dictionary fields not the Innn fields.

Exception Errors/ General Protection Faults/Access Violations.


These could be due to a number of things, if it relates to viewing history in Enterprise, check Entreg has been run, and refer to Entread. It could be a program fault, these are becoming fewer and further between. It is important that you Exit Enterprise and restart the workstation. If you cannot get out, log yourself off of any file server before softbooting. (TIP: Go to the index of Entread and type Exceptions, for more info and related topics) It could also be down to programs conflicting with Btrieve like screen savers, so make sure all screen savers are disabled, as well as other TSR's like virus scanning software. If the problem recurs, report it, and check you are on the latest version. (Also see OLE Exception Errors on NT4)

Exch main directory


The programs held in exchequer's main directory are :EXCHEQR.EXE EXCHREP.EXE SBSFLAG.EXE BTRIEVE.EXE Read Only Main Exchequer program file.

Read Only Exchequer System Set Up Batch Payments & Export Data ('Please Wait' when Loading) Read Only Works in the same way as ATTRIB see read only files.

Must always be running in memory before Exchequer programs are loaded. This is usually done inside REX.BAT Must have switch for compression set i.e. BTRIEVE /U:1

Can be given lower memory settings i.e. BTRIEVE /U:1 /M:32/B:1 Disadvantage is that memory buffering is reduced which slows down the system slightly. No extensions for new BTRIEVE Must run same version of BTRIEVE on all workstations. EXCHBULD.EXE Exchequer's own Data Rebuild utility that can be run externally from Exchequer Using REXBUILD.BAT or by selecting Utilities,Data Rebuild inside Exchequer. DEFPF044.SYS Screen definition program files are used to support different countries. MES044.SYS By changing the country code in General Settings certain fields will change MES065.SYS to that language. This is currently used to support different ways of expressing MES061.SYS VAT in other countries. Countries supported are UK (044 - VAT) Singapore (065 - GST) and Australia (061 - STX) PRINTSBS.SYS REX.BAT MS.BAT MSDEF.BAT BAKUP!.BAT Holds printer driver records. Loads BTRIEVE and runs Exchequer. Linked to the Word processor option in Utilities by default this loads Microstar Supplied with Exchequer but can be edited to load another WP. Linked to the Edit Form Definitions option in Utilities, by default this loads Microstar with *.def filename filter. Linked to the BACKUP! option in Utilities. By default this option uses the DOS BACKUP command to backup all Exchequer files. This can be changed to run tape streamer software or MSBACKUP. Linked to the 'Send to BACS' option in the Batch Payments Menu. This can be used to load BACS software. Linked to SBS System this can be used to shell out to any other DOS program, such as a spreadsheet or bespoke front end.

BACS.BAT SBS!.BAT

Exchequer Form Definitions


Exchequer forms printing effects Applies to PCC forms in Enterprise if edited via Exchequer (DOS). (refer to page 272 of the Exchequer reference manual)

CTRL O-D
CTRL P-A CTRL P-B CTRL P-D CTRL P-E CTRL P-N CTRL P-S CTRL P-T CTRL P-V

brings up the printing effects


Condensed (on/off) Double strike Emphasised Enlarge Italics Underline Quality Vertical Enlarge

Exchequer News Group

Owing to the growing list of resellers we are changing the way we send bulk email over to a list based server. In order to continue receiving bulletins from us or advance copies of ENTREAD etc., please join our list server as follows:* Create a new email * Send it to ftlist@exchequer.com * LEAVE the SUBJECT of the email BLANK * the first line of the message body should read JOIN EXCHEQUERSUPPORT * add no other lines of text to the email * send the email. * You will be notified of your membership of the list by return email. If at any time you wish to cancel your subscription to the list, repeat the steps above, and change the body of the message to LEAVE EXCHEQUERSUPPORT Thank you in advance for your cooperation, we feel that this is a much better way of controlling who wants to continue receiving our bulletins. We are also quite happy for any contact from within your organization to join as you feel is appropriate to ensure the right people are advised of any news from Exchequer Software.

Exchequer and Rounding.


NB: Exchequer works on a line by line basis when doing calculations, this is because We use line method type B for calculating VAT. Given a worked example of ; Quantity Price 2.75 47.5

The expected outcome is 130.625. But in reality, it is difficult to account for half a penny. When rounding transactions, it is important from an accounting perspective to remain consistent. With reference to SSAP2, Similar items must be treated in the accounts in a consistent manner, and the same treatment must be used from one period to the next. Therefore, when setting up Exchequer, there are a number of settings that should be considered which effect rounding. And once they have been set, they should not be altered without noting your accounting records accordingly, and preferably referring to your Accountant for guidance. Decimal places on cost price, sales price and quantity are the switches concerned, and can effect the rounding. For example going back to our worked example, with all decimal places set to 3, the outcome would be;

This is what we would expect, however with decimal places all set to 1 we get a different result;

This result is also perfectly acceptable; 2.75 rounded to 1 decimal place = 2.8 2.8 * 47.5 = 133.00. provided you are consistent in your methods. Please refer to your Accountant for guidance or clarification if required, when setting up Exchequer.
Special Function 54 Please note: When a multi-currency customer upgrades to v4.30, and wishes to use the new triangulation fields for EMU currencies, they MUST POST ALL DAYBOOKS and run Special Function 54 from EXCHEQUER before setting up the new rates via a Currency Revaluation. See EMU in enterprise help. Before you run SF54 make sure you have at least two backups. Run SF54 with nobody in the system. Once you accept the running of SF54 you will be asked the following question. Enter the Nominal Revaluation number or enter and the following screen will display. You will then be required to enter the currency number of the Euro. You will be asked to confirm the currency A progress window will appear showing the progress of the job. Once this is complete a status report should be printed. This can either be printed or put to the screen.

FDO Menu
FDO MENU SYSTEM To install FDO MD FDO Copy a:\FDO\*.* c:\FDO Copy a:\menu.bat c:\DOS Before adding menu batch file to DOS directory, type Autoexec to start menu. To get computer to come straight to menu screen, need to alter autoexec file - add "menu" on line at end. Enter root directory - edit - Autoexec.bat - add "menu". The following facility is unavailable now, older users still use it though. To set up Back Up option Return to FDO menu.F9 Add Choose number for option "Back up Exchequer" DOS "Backup c:\exch\*.* a: /s" To set up Restore option As above, but: "restore a: c:\ /s" File Handles on NT Server Our recommendations on file handles we feel should be followed and should not cause problems but the following was issued as a warning from Pervasive so I have included here just in case.

Issue: A Btrieve Create function generates a Dr.Watson error on a Windows NT Server after the installation and configuration of the Pervasive.SQL engine. Solution: During the configuration of the engine, an extremely high value for the number of Open Files Setting was entered. The engine reserves 1024 bytes of memory per file in the Open Files table. This means the Operating System allowed us to over run the assigned upper bounds address (instead of telling the engine that the required amount of memory is not available, and the engine would have failed to load). The number of open files should not be more than the expected maximum number of physical files open at one time by the engine. How To: The best way to set the number of Open Files is to figure out the number of Btrieve files your database contains. Then add some arbitrary value to it to allow for a little buffer for the creation of temporary files, or new files on the server. Then, take that number and multiply that by the number of workstations you have, plus an arbitrary number for your Handles setting. Open Files is a setting that states - "I have this many Btrieve files on my system that I will have open at one time." Handles Setting is the logical number of file handles that the users will be using to find position on a file. Analogy The best metaphor we can provide for this is a file as a trolley car. For people to be able to hang onto and use the trolley, they must have a grab handle available to them, which is representative of the Handles setting. So, if all the workstations, running one application access all the calculated files they can on your system, then that would equal the number of open files times the number of your workstations. In short, unless your application changes per environment or per version, then the number of Open Files setting will be static to your application. The number of files handles will be the one that changes depending on the number of workstations you will have using your application.

Form Definitions
When editing form definitions you need to ensure that both the .DEF and.LST files are updated, and that the filename of the new form has been saved on page 4 of system set-up. Field I326 Document type, this field is for use in the header part of a form, and not for use with-in a loop in a statement for example. a new field has been added I410, in Exch 4.10a to achieve this result. INSTRUCTIONS FOR EDITING FORM DEFINITIONS ========================================= There are two files for each layout; the .DEF file and the .LST file. .DEF This is the definition file, which shows the layout of the document and the position of the fields. .LST This is the list file, which is a list of the field numbers that are used in the definition file. This list of field numbers must be in the order that they are printed in the definition file. For a full and up to date list of field numbers, under editing form definitions, print the formdef.doc.

Form Design
HOW TO DESIGN A FORM ==================== The best way to design, for example, your invoice layout is to type a manual invoice from this Word Processor, print it out and amend it until you are happy with the layout. You should then replace your fields (such as Date, Invoice No.,Description, etc.) with the underscore

symbol '_', allowing one underscore for each character of the field. Therefore if the Invoice Description is 50 characters long then you should type 50 underscores in the body of your invoice. Note: If you only type say 40 underscores in your layout, the description on your printed invoice will be truncated at 40. Once you have entered all the fields that you wish the computer to take from the typed invoice, you should enter any '@ commands' that may be necessary. @ COMMANDS ========== @ Commands are otherwise known as print formatting commands and are generally used for send commands to the printer for settings such as Page Length, Page Offset, Margin Top/Bottom etc. Exchequer also uses the commands as instructions for logical expressions. i.e. IF (condition 1 = True) THEN (Print this) ELSE (Print that)

DOS/ PCC Forms


Signs Q: On a debt chase letter, the sign printed as a #. A: The printer needs to be reconfigured - check dip switches, printer set up etc. Could be as simple as switching off and on if it has worked previously, and another piece of software has been used to print just before printing from Exchequer. System Setup on Printer Ascii Code 77 (Alt+), in the field for currency. Printing Documents Q: A trading history print out did not show one line. A: Go into edit form definitions and look at .def file. Is there a gap between the last line and the @ER Y? If so, delete the blank line.
GPF in MIF by Protected Mode DOS Program through btrbox95 Issue: Running some protected mode applications through BTRBOX95 on Service Pack 5 causes a General Protection Fault in W3MIF10E.DLL. Solution: This has been logged as defect 19572. Repair time unknown. Indication is that the fix is not to simply go back to the previous MIF.

GST
This section is a reference for Australian Companies;

A METHOD FOR GST REPORTING IMPORTANT: READ THESE INSTRUCTIONS FULLY BEFORE PROCEEDING This is only one of several ways to cope with GST transactions, and get the GST report to show enough

detail. It is a suggestion only. You will need to test it to make sure it meets your needs.

In GST Setup edit the GST Rate 3 to read ' Import GST', and leave it at zero %. This will be used for GST paid to Customs. In GST Setup edit the GST Rate 4 to read ' GST Paid', and leave it at zero %. This will be used for GST paid to the IRD, from your GST returns.

Try the following transactions in your demo system: 1. To put an invoice in for GST paid to Customs, enter either a PIN or PJI against the creditor, and add a line which is description only with a note ' Import GST on shipment x' . Put in no value, and select Rate 3 for GST. Click OK, this will bring you into the footer. Tick the 'Amend GST' box and enter the GST amount in the GST column and Rate3 row. Click OK. This will now show the total payable, which is all GST. The Nominal Ledger will debit Input GST and credit creditor. 2. Instead of entering a nominal journal to reflect the payment of GST to the IRD, I enter a PJI or PJC (depending on whether it is a refund or payment). On the PJI/PJC enter a description only line noting 'GST Return for May', and put the amount payable to the net amount field , and select GST Rate 4. If you have set the IRD up as a creditor , and their default account as your GST Payments code (the third account), this is the code this line will go to. Save the PJI/PJC. This will debit the GST Payments account and credit the creditor, so you can process the payment just like any other creditor, and will show up separately on the GST report. I normally enter this as at the last day of the month, and then run final GST reports, then close the GST period.

General Disclaimer
Should the need arise for a copy of a clients data to be taken off site, or set to another site for inspection or repair purposes, we would suggest a disclaimer is issued, an example disclaimer is below' Dear (CUSTOMER) We confirm our telephone conversation of today (DATE), requesting that a copy of certain Data files be sent to (COMPANY NAME). To protect your data it is in your own interest that we advise you to send us COPIES of your data. The request to send such media containing live or sensitive data shall be at your own risk .The cost of any carriage and insurance charges to and from (COMPANY NAME) shall be born by yourselves. Consequential corruption or damage to files or data whilst in the care of (COMPANY NAME) is taken on a 'best endeavor or intention' basis and that (COMPANY NAME) accept no claim for such consequential loss of business data other than in the replacement of the media on which the data was received. Failure of such files or data is deemed to be covered by your own insurance scheme. Please make sure you have an alternative back-up of your data at the time that copies of your data are sent to (COMPANY NAME). We (COMPANY NAME) agree to take reasonable steps to ensure that the confidentiality of all data on our premises is assured at all times. Yours Faithfully.

(Co.Rep)

General Problem Submission


Following is a suggested layout for submitting problems to Exchequer HelpLine Support;

All fields are mandatory, even if the response is "not known"


-------------------------------------------Cut Here-------------------------------------------------

E-Mail/Letter Reference: (if you have one, internal call ref. forexample) Customer: (If Possible their Exchequer Account/support Code) Network: (Novell, NT, W4WG, Include O/S version) Workstation:- O/S and Specification (Include version of Internet browser if appropriate) Version: (include Ent or Exch) Module: (in which Module is the Problem, i.e. SOP, TS, JC etc.) Details: (What is the problem, How does it manifest itself and What exactly is the user doing at the time, if possible immediately before. Can you reproduce the problem). Steps to Solve Problem: (What have you tried and what did you find) Possible System Changes: (Including Hardware Software) Your Suggestions:
Check List (Has it ever worked, intermittent problem, only on some WSs -------------------------------------------Cut Here------------------------------------------------The more relevent and accurate the information that is provided to the helpdesk, the faster the solution. If it is a percieved fault, does it only manifest itself at the client's site or can you reproduce it and exactly what steps are required.
General Protection Fault in Patch16 with Pervasive.SQL Service Pack 3 Issue: When executing the Patch program on Windows NT machines for Service Pack 3, you may receive the message "Patch16 caused a general protection fault in Patch16.exe" or "Patch16 caused an error in Patch16.exe". Solution: The 16-bit version of Patch is being launched erroneously. The work around is as follows: 1. Execute the patch and select Setup. This will unzip the patch files into the c:\temp directory and invoke the initial installation screen. 2. Open Explorer and browse to the c:\temp\~wzs????.tmp directory. 3. Execute Patch32.exe. 4. Return to the installation screen and continue with the patch.

General Rebuilding/Special Functions


General note about Rebuilding Unposting and Special Functions;

If you suspect odd behavior from a database point of view, a rebuild may be in order. Rebuilding generally has no effect on data content, that is why we need the Special Functions. Special Functions deal with known problems and special sets of circumstances that may sometime arise. If a problem occurred during posting (for example a power failure) and reverting to a back-up is not a viable option, you may need to unpost and then re-post.. In some situations you may need to use combinations of these procedures. Please refer to the worked examples section of this help file for examples on how to apply these techniques.

General networks
Networks are complex systems, and require a certain level of management. Every company should have an employee designated as the 'System Administrator'. This person is responsible for the management of the network and the accounting system. Your System Administrator should be the first contact if the operators experience problems. The System Administrator must have the necessary skills and training to administer the network, with specific network training in the Network Operating System, administration of the Accounting system, and any other related hardware and software (eg Tape Backup and Restore). This will save time and expense in the event of a system failure. The System Administrator should ensure that adequate daily backups are taken. The building blocks of a good network are: quality hardware and cabling, quality network operating systems , clean power, and a good network administrator. Without these you are more likely to have problems with your network and your accounting system. Do Something About This Before Its Too Late!! TIPS Buy the best computers you can afford. Pay particular attention to the quality of the network cards and any hubs. Make sure Hardware support is Onsite. Ensure you have a good network provider supporting you. Use a quality tape backup every night. Keep a copy each night plus a weekly tape. Avoid anything other than Category 5 cabling throughout. Watch out for power problems , and if in doubt , get some protection. (This is more common than you think, and accounting systems on networks are more susceptible to this) If you move hardware, or want to install your accounting system on a new workstation, please advise your reseller. Occasionally your old accounting system will be running an older version of Btrieve. In cases where this conflicts with Enterprise it pays to have the old system on a separate pc, and it pays not to run the old with the new. Conflicts have been found to occur with NZA, and Sybiz

Going Live
Before proceeding to put on transactions press F5 and change your VAT period back to the previous quarter, when you have put on your opening balances then you can close that VAT period (F5 and 'C') and then your real transactions will be the only items that show on your first VAT return. This is not essential but if you do not do this you must remember to deduct from your first VAT return the turnover you have created by putting on the opening balances.

Also see notes for Setting up Exchequer to be Euro Prepared

Putting on Opening Sales & Purchase Ledger Balances


Obviously when you commence using Exchequer you have outstanding debtors/creditors which need to be entered onto the control accounts. The only way to get balances onto the Sales & Purchase Ledger control accounts is to create a transaction within the daybooks. (If you are using multiple debtors and creditors control accounts, we suggest you go through the opening balances procedure dealing with one control account at a time.) If you hold Creditors/Debtors balances in different currencies it is probably better to deal with each currency in turn. E.g. Opening creditors in sterling ( steps 1 - 7) then Opening creditors in US Dollars ( steps 1 - 7 ). This would mean entering two figures in the opening trial balance, Opening Creditors in sterling and opening Creditors in US Dollars. To put on the opening balances : 1) Enter onto the relevant Daybook, select Add,Batch. 2) You then have a screen with a box at the top which you should complete, use the last day of the old year as the date (usually period 12 of the last accounting year). Enter the total of your outstanding debtors/creditors in batch total field(for the Purchase Ledger enter a minus sign before the amount i.e. -2354.50) 3) Select Add, Journal Invoice(SJI). Enter the account code, the date(prompted by the date in the top section) you can choose to enter either a balance for every account or individual invoice values, if you are entering individual invoices you may wish to over type the date which can be quite time laborious but will give you a correct debtors/creditors report if required immediately. In the Your Ref field you can either enter O/Bal or in the case of individual invoices the original invoice number. In the description field enter the words Opening Balance. The Nominal code will be the one for sundry debtors/creditors (just type sundry and a pop up menu will appear & choose the appropriate one.) Enter the gross amount of the invoice/balance, then enter 'Z' in the VAT code column.(This is because the VAT will already have been accounted for on the original invoice.) (N.B. If on cash VAT accounting enter the net amount and the VAT separately.) 4) Press the insert key on your keyboard and the next Journal Invoice (SJI) number will appear, you can then press the Tab key on any field that is the same as the line above, such as the reference, description, nominal code. This makes entering the balances very quick. 5) When they are all entered the batch difference figure in the top box should be zero. 6) Press F9 to store. 7) To get these balances onto the customer/suppliers accounts you have to post the Daybook, press F6 to ensure the period is set to the period of your batch then press 'D' Daybook post, 'P' - post this Daybook.

Putting on Opening Stock Balances.


Before using stock you should where possible enter your opening stock balances, the degree of importance of this exercise depends on which method of valuation method is used. (When working on FIFO problems are caused by going into negative stock.) If you are using Multi-location stock, you will need to put on the opening balances location by location. (EG Filter by location, process, filter by next location and process) 1) From main Menu select Order Processing, On Screen Stock Lists, Stock Take List.

2) Select 'Z' to freeze the screen You are then prompted for a new stock take press 'Y' You are then prompted for posted stock press 'Y' Now any stock movements that happen whilst the figures are being entered will not affect this screen. 3) By pressing the enter key the cursor flashes in the Act Column for you to enter the stock quantity, (you can leave this screen and re-enter it again later) when all stock is entered you then select the Process option. 4) If you now go onto the Issues & Adjustments Daybook there should be an adjustment transaction(ADJ) which has put them into stock. Select Print to keep a record of the opening quantities entered onto Exchequer. Then Print a stock valuation report (using live stock) which should match the value on the Trial Balance. 5) You now have to post this ADJ which in turn creates an automatic accounting movement. Normally when you create a stock adjustment for any reason i.e. damaged, losses etc. you need the accounting movement, but in this instance the accounting movement will be manually entered by the trial balance from the accountant. To overcome this, select Nominal Ledger from the main menu, nominal transfers and there should be a nominal transfer (NOM) with a description of Stock take, print this for reference then enter onto it and delete the description and all the lines contained within it and press F9 to store or Alt Z in period field.

Putting on the Opening Trial Balance. Before doing this, check the Nominal Structure and Nominal Control Codes have been set up (refer to the Manual), making sure Auto retained profit is a control account, and that it comes physically below the profit and loss accounts. This is entered as a Nominal Transfer.
1) From the main menu select Nominal Ledger, Nominal Transfers, Add 2) The next available nominal transfer number will appear (NOM), use the last day of the old year as the date (usually period 12 of the last year). Enter Opening Trial Bal. as the description. 3) Select Add, Enter Opening Trial Balance in the description field, the relevant nominal code and amounts in the Dr or Cr columns. There are certain control accounts nominal codes that cannot be used, these are : Creditors Control - Use Sundry Creditors code instead (this should be the same code used when entering the purchase ledger balances, hence bringing the balance to nil on that code.) Debtors Control - Exactly the same procedure as above but using Sundry Debtors code. VAT - use Vat payments Code. Retained Profit - Either use the Retained profit opening balance nominal code, or if you are setting up at a year end, you could put this to any type A account, in period 12 of the preceding financial year, as it will become Auto retained profit at the year end.

Opening Bank Reconciliation


Part of the opening trial balance includes the cash book figure, but this is not particularly useful to do the bank reconciliation. To overcome this add a new nominal transfer with the title Opening Bank Reconciliation, then enter the details as the example below. Description Opening Trial Balance Statement @ 31/12/96 O/s transaction Nominal Code Bank Account Bank Account Bank Account Dr 4000 1500 Cr 5000 Reversal of TB column entry Amount in bank at going live Uncleared Amount

O/s transaction O/s transaction

Bank Account Bank Account

400 100

Uncleared Cheque Uncleared Cheque

Job Costing
Enter these as NOMs with an in and out to the same GL Code with the Job and Analysis Code on the Debit line but no Job/Analysis Details on the Credit Line.

HP Jet Admin will cause Access Violation Issue: After installing HP Jet Admin, the client workstation kept getting access violation on running SmartScout, InstallScout etc. Solution: Discovered that HP Jet Admin installs calwin32.dll and clnwinth.dll, which reportedly cause access violations. After removing these two files (or deinstalling HP Jet Admin) everything worked fine again.

Hanging on NT with Pervasive SQL Title: Multiple Returns to Minimal State Cause Insufficient Resources Issue: The client application stops responding, and the Windows NT 4.0 server returns the following error: * "Not Enough Resources Available to Complete This Task" The problem is reproducible when the MicroKernel Engine setting 'Back to Minimal State If Inactive' is enabled. This setting allows the Microkernel Engine to release memory and thread resources, and go back to its initial state when no clients are active. When an application establishes a session with the MicroKernel Engine, it forces the engine to allocate resources. With this setting enabled, and once the application terminates its session with the MicroKernel Engine, the engine releases the resources allocated for that session. After several sessions are established and released continuously, the resources that have been released by the MicroKernel Engine may not necessarily be set free by the Operating Systems. This is because the Operating Systems are too busy allocating additional resources to the new sessions. As a result, the application stops responding due to lack of memory available on the server. Solution: This problem can be resolved in two ways. 1) Increase the machine's physical RAM to 64 Megabytes or more. 2) Disable the option for the engine to return to minimal wait state. This causes the engine to get resources and use them till the engine services are shut down. Note: Set the Microkernel Engine setting 'Back to Minimal State if Inactive' to off. By disabling this setting, the Microkernel Database Engine(MKDE) will not free up memory and thread resources to the OS until the MKDE service is shutdown. How To: * To increase RAM, please refer to your Hardware vendor. * To disable minimum Wait state, use the Setup Win32 utility on the server. 1. Choose Start ->Programs ->Pervasive SQL 7 ->Setup Utility (Win32). 2. From the drop down Component list, choose Microkernel Database Engine. 3. Select System Resources/Directories for Categories. 4. Set 'Back to Minimal State If Inactive' to off. 5. Save. Exit utility and stop Btrieve and SQL services. 6. Restart. IO Error reading in Printer Definitions This error message can occur when Enterprise is starting up if the PRINTSBS.SYS file is missing. If PRINTSBS.SYS is missing, it could be that a recently performed installation or upgrade failed, or that

the file was deleted. Try running the last disk of the last upgrade again.

Installation Tips / Btrieve Tips


IPX/SPX is only likely to be an issue on NT and BTI.CFG is only relevant Non-Client Server Quick reference table; ____________________________________________________________________________________ ___ ____________________________________________________________________________________ ___ Non-Client Server Client Server LOCAL ENGINE REQUESTER MODE ____________________________________________________________________________________ ___ The local engine is an executable called Btrieve (v5.10 has been re-named BTR510) v6.10c of Btrieve or above (6.15 of Btrieve only on NT)

Exch Either v 5.10 of Btrieve or v6.10 On NT ensure IPX/SPX is the primary (V5 Btrieve file format will work with v6 protocol (See Entread as to how to edit but not the other way round. You get error2 The network packet size, or set the If you need to convert v6 files to v5, rebuild virtual network number if busy network.) with the /D: switch added to the option line of BTI.CFG) NT - Requester - BREQNT.EXE Novell - Requester - BREQUEST.EXE If multi-user, check the /G switch in options in BTI.CFG. It should be set to /G:1:1 On NT Btrieve runs on the server is BTRIEVE.EXE, on Novell it is BTRIEVE.NLM ____________________________________________________________________________________ ___ Ent V6.15 of Btrieve only The Local Engine in this case is a DLL WBTRV32.DLL If running Ent and Exch multi-user, check the /G switch in options : in BTI.CFG. It should be set to /G:1 v6.15 of Btrieve only, apply patch to v.6.15.445 Client Server Requester is W32BTICM.DLL On Novell use BTRMON, and on NT use the Microkernel Monitor on Server to monitor Btrieves activity.

On Novell, use the 'Microsoft client for Novell' where possible. If you have to use the Novell32 client, ensure 'Bindery Emulation' is switched ON. ____________________________________________________________________________________ ___ Btrieve settings on Workstation = Btrieve settings on Workstation =

Local - YES Requester- No

Local - No Requester - Yes

____________________________________________________________________________________ ___ ____________________________________________________________________________________ ___ There is a new ENTREG which on entry to Enterprise splash screen will check the Btrieve settings and advise you if we anticipate any problems with the settings see ENTREG. The quick reference table above is aimed to help point to areas to look at when troubleshooting either an installation or general stability problem, there are also other area's covered in Entread. Remember to break problems down, and get one workstation communicating with the server first, then add the next workstation and so on. Ensure all drive mappings,and clients are the same , and that no TSR's are running in the background. Also ensure all of the latest patches for Btrieve, Novell and NT are applied, a number of which are available from our Web site. (You can get patches for Novell and NT to v6.15.445 from Pervasive's site. The address is http://www.pervasive-sw.com/support/ftp/upd_btrieve.html) If you think that problem may revolve around a particular PC, or the network in general, use our Diagnostic tool Compass or Pervasive's Super Scout to try to determine this. Both are available to be downloaded from our Web site. Tips on improving Btrieve performance on NT peer-peer networks Interpreting MKDE-1180 and MKDE-2039 System Errors Subject: FYI00972 - Interpreting MKDE-1180 and MKDE-2039 System Errors Title: Interpreting MKDE-1180 and MKDE-2039 System Errors Issue: The MicroKernel Database Engine (MKDE) sometimes puts one or more of the following messages in the PVSW.LOG file: * * MKDE-1180: System Error: nn.nn.nn or MKDE-2039: System Error: nn.nn.nn

where nn.nn.nn are numbers, such as 116.5.0. What do these messages mean? Solution: The MKDE uses the System Error messages to record unexpected errors resulting from an operating system call made by the MKDE. For example, if an error is returned when the MKDE makes a file I/O call to the Operating System, that error is recorded in the PVSW.LOG as a System Error. The format of a system error is id.op.rc where: * id - unique System Error identifier * op - Btrieve operation being performed at the time * rc - any unexpected return code from the Operating System The id corresponds to a section of code in the MKDE where the OS call took place. There are different id ranges depending on which MKDE is being used: * Common source base 100 - 299 * NetWare 300 - 399 * OS/2 400 - 499 * Windows 500 - 599 * Windows NT 600 - 699

WIN95/NT

700 - 799

The common code base contains all the file I/O requests, variable allocations, caching, etc. The platform specific ranges cover other file open, close, read, and lock requests. These codes can guide us to the portion of the MKDE code that was executing when the System Error occurred. For example, ids ranging from 110 - 124 correspond to the I/O Subsystem of the MicroKernel where disk I/O calls are made, and system errors with these ids usually correspond to file corruption problems. A complete list of ids is not available to the public since this is considered company confidential information. The second piece of the system error is the operation code. This corresponds to the Btrieve request that was being processed when the error occurred. For example, a 5 is a GetEqual operation. Refer to a Btrieve Programmer's Reference for more information about Btrieve operation codes. If the system error occurs while the MKDE is performing some task that is not specifically associated with a Btrieve operation, the op will be set to -1. The third piece of the system error is the OS return code. The meaning of the values reported here varies depending on the OS call made and the type of failure that occurred. A return code value of 0 for different ids is likely to have different meanings. In many cases, the appearance of an occasional System Error does not indicate a problem. It is likely that the operation being performed retried without an error and processing continued normally. If there is a problem that would cause an interruption in normal operation, the System Error would correspond to a Pervasive status code returned to the application. For example, attempting to access a physically corrupt file will produce a system error such as 116.5.0 and the application will receive a Status 2. How To: If you experience repeated occurrences of a specific system error, along with abnormal behavior of your application, and you do not find any documentation in our knowledge base (www.pervasive.com) about the error. You should contact Pervasive with a description of the system error and the symptoms of failure in the application, and we will provide more details about the system error in question.

Introduction

Last Modified 27/02/2006

Errors Special Functions Rebuilding Btrieve tips This help file is for Dealer/Distributor use only and has been written to be used in conjunction with the 'Entread' , Entrprse, Enterole, Enttutor, Formdes and any other related Exchequer help files, the 'Readme' files and manuals, with specific reference to the trouble shooting sections. It includes quick references to correct procedures, and guidelines on how to correct things should they go wrong. It is important to remember that a lot of the procedures outlined in this help file, especially those that require the System password, should be done under supervision as otherwise serious data corruption may occur. When reporting problems, please use our suggested LAYOUT , or at least include the basic information therein, ie O/S, version of Enterprise, exactly what the problem is, should a copy of your client's data be requested, please issue the standard disclaimer. Also when asking for release codes, try to use the Phonetic Alphabet to save mistakes. For the latest details about future developments see the Reseller Page on the World Wide Web. (www.Exchequer.com) The password for this section of our Web site will be updated monthly and will be included in the Exchequer Support Bulletins. If you did not receive the last bulletin,,SUBSCRIBE NOW! or call helpline for further information. If you would like to receive Bulletins via E-Mail, join the Exchequer News group

Disclaimer:

Any information given on accounting practices within this document must be approved by your Accountant. All information is supplied "As Is" and without warranty Expressed or implied. IRIS Enterprise Software accepts no responsibility for any Interpretation of the notes and or instructions contained herein. Note New Special Functions since last release.

Invoice to Cash Accounting


You need to complete the next VAT return but do not close it. Make sure they are happy with the figures etc. Then change the VAT scheme to Cash Accounting and run the VAT return again. This will produce a cash accounting based VAT return, then close the period. The problem is that as any invoices get allocated they will start appearing on the next VAT return, so they will have to check all VAT returns and manually deduct any duplicated invoices, until all the outstanding invoices at the time of the change over, are completely paid. Note once you close a VAT period under cash accounting you cannot re run that or a prior VAT return report.

Job Costing Problems


Job Costing - Unknown Heading. On several jobs when selecting Totals screen there is one line that states Unknown Heading, and has no data, where as other jobs list the totals, which shows headings exist. We have seen this happen on odd occasions, it happens when the Job is first created, it should create the totals screen at the same time, but for some reason, it has not. To rectify please follow the steps below; 1. Take a copy of the system 2. Delete any job with the problem on the copy version 3. Add the job in with the same Job Code on the copy version 4. Copy JOBS\JOBHEAD.DAT from copy into original version 5. Run rebuild all totals in JOB utilities menu to recalculate all the totals for all jobs.

Keyboard Problems
bQ. During data entry, Enterprise hangs, especially if the Alt key has been used heavily. In some cases the Alt key appears to be stuck on.
A. This has been traced to some faster P2 Pentium computers. It appears that if the keyboard repeat rate is set too high, Enterprise can crash or appear to have the Alt key stuck on. The only current solution is to increase the keyboard key delay rate found in control panel. to as long as possible. By default this appears to be set to the shortest delay when windows is installed.

If the problem persists, it maybe a hardware issue requiring a BIOS update.

Known issues v4.30/4.30a


Exchequer and Enterprise v4.30a Known issues Last Updated 03/02/1999

General Guidance.

The issues below currently exist in v4.30a of Exchequer and Enterprise, and have been recorded here for your information to help resolve support problems. Our current policy for this year is to limit the number of versions to avoid the different state of upgrades we got into last year, however should an issue require urgent fixing at a particular site, then it may be possible to let them have a beta (SPOP only) as an interim fix.

Exchequer
General It is possible to enter an incorrect nominal type within a nominal record. No work around. Fixed in beta. B430a.005 Stock If prevent negative stock is enabled, it is not possible to credit in a BOM via an ADJ. Work around: Temporarily use a different password to credit BOMS. SPOP

Job Costing New Features

Enterprise
It is possible to enter an incorrect nominal type within a nominal record. No work around. Fixed in beta. B430a.005 Stock If prevent negative stock is enabled, it is not possible to credit in a BOM via an ADJ.

Work around: Temporarily use a different password to credit BOMS. SPOP Job Costing It is possible to enter a job type greater than 3 characters when adding new job types. Work around: Should a job type be added it will still only be possible to search for it by its first three characters. Do not enter job type codes of more than 3 characters. Fixed in beta. B430.018 Items on the Automatic Daybook with a job code appear in the job Daybook. No work around., other than do not add job codes to auto transactions. Fixed in beta. B430.018 New Features

Exchequer and Enterprise v4.30 Known issues Last Updated 19/01/1999


General Guidance.

The issues below currently exist in v4.30 of Exchequer and Enterprise, and have been recorded here for your information to help resolve support problems. Our current policy for this year is to limit the number of versions to avoid the different state of upgrades we got into last year, however should an issue require urgent fixing at a particular site, then it may be possible to let them have a beta (SPOP only) as an interim fix. There currently exists both a single and multi currency beta version which will contain fixes to many of these problems.

Exchequer
General When a translation currency is specified on the Audit Trail report, the translation of values is not being carried out, and the amount shown remains in the currency of the report. No work around. Fixed in beta. B430.018 When generating a PPI via a batch, subsequent editing of the batch line causes a new cheque number to be generated each time. Work around: If a batch line is edited, then a manual edit of the cheque number will also be required. Fixed in beta. B430.018 The Batch Payment/Receipts Routines, ignore items on hold and includes them in the list of transactions to be paid. Work around: Compare the batch payments report with the payments due report as this does not show those transactions on hold, and manually ignore those on hold.

Fixed in beta. B430.018 The checking of an accounts credit status includes the committed balance twice, and so causes false warning to show, however the on screen values are correct. Work around: Manually check the on screen values, and ignore any incorrect prompts. Fixed in beta. B430.018 Stock When a sales or purchase unit of stock was in use, the auto picking and set Picked quantity via the picking list does not suggest the correct quantity. Continuous use of the auto pick option causes the system to suggest different pick quantities, until the correct value is arrived at. Work around: This is mainly a display issue, and should not have any serious knock on effects. Suggest items are picked manually. Fixed in beta. B430.018 SPOP When a Purchase Order is printed directly to a printer, the printed status does not get set. No work around. Fixed in beta. B430.018 The VAT EDI routine incorrectly includes items from entire VAT quarters, on SSD submissions. No work around. Suggest a beta is sent out to any site attempting to submit via EDI. Fixed in beta. B430.018 Job Costing Items on the Automatic Daybook with a job code appear in the job Daybook. No work around., other than do not add job codes to auto transactions. Fixed in beta. B430.018

Enterprise
General When a translation currency is specified on the Audit Trail report, the translation of values is not being carried out, and the amount shown remains in the currency of the report. No work around. Fixed in beta. B430.018

When generating a PPI via a batch, subsequent editing of the batch line causes a new cheque number to be generated each time. Work around: If a batch line is edited, then a manual edit of the cheque number will also be required. Fixed in beta. B430.018 The Batch Payment/Receipts Routines, ignore items on hold and includes them in the list of transactions to be paid. Work around: Compare the batch payments report with the payments due report as this does not show those transactions on hold, and manually ignore those on hold. Fixed in beta. B430.018 When reproducing a Batch Payment run, it is not possible to select the currency required. Work around: Temporarily set the desired currency within the next batch run, and then rerun the batch required. Fixed in beta. B430.018 When the ability to hide any margin information via a password is in effect, it is being ignored by the option to show GP (switch button) in the customers ledger. Work around: Access to the ledger may need to be disabled if this information is very sensitive. Fixed in beta. B430.018 The checking of an accounts credit status includes the committed balance twice, and so causes false warning to show, however the on screen values are correct. Work around: Manually check the on screen values, and ignore any incorrect prompts. Fixed in beta. B430.018

ObjectFind does not find account codes by VAT registration numbers correctly. Work around: precede the VAT registration code being searched for by a 'C' when looking for customers, or an 'S' when looking for suppliers. Fixed in beta. B430.018 When the ObjectPrint button to print a transaction currently being edited, the printed copy only reflects the state of the transaction currently on the hard disk, ignoring any current on screen changes. Work around: Do not use ObjectPrint until after the transaction has been stored. Fixed in beta. B430.018 Stock When a sales or purchase unit of stock was in use, the auto picking and set Picked quantity via the picking list does not suggest the correct quantity. Continuous use of the auto pick option causes the system to suggest different pick quantities, until the correct value is arrived at.

Work around: This is mainly a display issue, and should not have any serious knock on effects. Suggest items are picked manually. Fixed in beta. B430.018 If the option to separate any discounts given is enabled, the stock value posted to the average cost includes discount. No workaround. Fixed in beta. B430.018

SPOP When a Purchase Order is printed directly to a printer, the printed status does not get set. No workaround. Fixed in beta. B430.018 When filtering the Sales Order Daybook (With large amounts of data on it) by Delivery Notes, and then choosing to filter by tagged items when there were none, the system enters a loop, and crashes. Workaround: Users must wait for the list to finish refreshing before attempting to apply a new filter. Fixed in beta. B430.018

Sales Orders with settlement discount within them are incorrectly set to 'Hold until allocated' as they are stored if the System Setup switch 'Disable auto hold status' is not enabled. Workaround: Users must check status of orders, and manually remove the hold until allocated status. Fixed in beta. B430.018 When a location transfer includes serial numbers, the 'in' location for the serial numbers specified from the out location is not being updated. Workaround: Manual editing of the location at the time of the serial number selection will be required. In addition the serial numbers should not be marked as used in this instance. Fixed in beta. B430.018 The VAT EDI routine incorrectly includes items from entire VAT quarters, on SSD submissions. No workaround. Suggest a beta is sent out to any site attempting to submit via EDI. Fixed in beta. B430.018 Job Costing It is possible to enter a job type greater than 3 characters when adding new job types. Workaround: Should a job type be added it will still only be possible to search for it by its

first three characters. Do not enter job type codes of more than 3 characters. Fixed in beta. B430.018 Items on the Automatic Daybook with a job code appear in the job Daybook. No workaround, other than do not add job codes to auto transactions. Fixed in beta. B430.018 New Features Prior to a revaluation, a check is made for any unposted transactions being allocated, if any are found, the revaluation will fail. If the currency of VAT return is different to base. it is now possible to edit the vat exchange rate. This ensures full compliance with the UK VAT requirements. The System Setup switches External Customer has been implemented fully in Enterprise so that when enabled, it is not possible to add or edit customers from within Enterprise, as this switch assumes this function is being handled outside of Enterprise. The System Setup switches External Sales Invoice has been implemented fully in Enterprise so that when enabled, it is not possible to add Sales Invoices (SIN) or Sales Credit Notes (SCR) from within Enterprise, as this switch assumes this function is being handled outside of Enterprise. When searching for a stock item from within the Stock List by Code, Description, or Alternative Code, the searching has been speeded up by use of internal database indexes. The System Setup switch Print Sales Receipts has been implemented fully in Enterprise so that when enabled, the user is prompted to print the SRC as it is stored. The ability to print stock labels from SQU,SDN,SOR, POR,PDN,PQU has been added, so a label for each product can be produced with varying quantities.
Printing Multiple packaging labels in v4.10 Enterprise (multiple labels on the same sheet) In the form designer, system set-up form definition sets under options choose global defaults. For demonstration purposes set Sales delivery label to ACCLBL. (Picture 1) Picture 1

Save this option, then exit Enterprise. Then re-enter Enterprise and add a sales order, entering the number of labels you require in box labels in the footer and store the order. ( See picture 2) After storing the order, pick the order. You then need to Deliver picked orders, see picture 3.

Picture 2

Picture 3

Delivering picked orders will bring up the following box, set the options as follows;

Send to the printer, and you should get one delivery note, and the multiple labels you require. (You need the Prompt for paper change tagged at present but will not need this option tagged following the next upgrade. Also the print to screen error will be fixed by the next upgrade.) The following prompts will appear, OK them both;

And finally, select where you want the labels to start printing on the page.

Should you have any problems printing, you can re-print a printing run.
License Modules This is the way that modules are released and release codes can be obtained by giving the security code of the module requiring release to the help desk who will then give you the code to enable the module. You have to be logged in as SYSTEM with the daily password to access this function in system setup license options. If you are using multi company manager then from the file choose Login and enter the daily password. Then file again to go to license options. Doing it this way you release the modules for all companies at the same time.

Locking or running slow


The three most common causes of either Exchequer or Enterprise locking up or running slow are listed below; 1) Btrieve settings, see Entread. For example the Interface settings (Local and Requester, one should be set to yes and the other no) and the BTI.CFG timing. in the options section the switch for non client server should be /G:1:1 2) Client conflicts. If you had one user using the Microsoft client and another using the Novell client. 3) TSRs (Terminate and stay resident programs) Screen savers and virus scanning software. Including the Standard Windows95 and NT screen savers.
Login Errors

Message "One of the library files needed to run this application cannot be found" after the Login screen. This is due to the fact the ENTSM1.DLL file is not in your main enterprise directory. This should be

installed when setting up Enterprise but people with pre Euro versions may experience this if adding a company to their system. New companies are set up as Euro as a default and need the Euro bit map.

Low Resources
It would appear that if Internet Explorer 4.0 is installed, Enterprise uses considerably more system resources than it normally does (when IE4.0 is not installed). The system can drop to 20% resources, causing a crash, after about 12 windows are opened in Enterprise. With Internet Explorer 4 removed, this number increases to around 30 windows, before resource levels become critical. The Message "Low Resources" issued by Enterprise has much more to do with Windows resources THAN actual memory. This goes back to the early days of MS Windows where a unit of around 300 was allocated to Graphical User Interface (GUI) resources. This was originally taken to be screens that were open but it turns out to be pretty much any Windows control that can receive focus. Therefore the more CONTROLS/BUTTONS/EDIT BOXES that can be SEEN IN AN OPEN Window the more "Resources" it uses. In fact this equates to the number of CONTROLS on a screen, even those that are not currently visible, like the ones on the various tabs on the stock record screen for example . The various versions of Windows and Explorer combinations allocate these recourses in different ways. Win 95 is less hungry that Win98. A PC with Internet Explorer 3 installed, tends to be less hungry than one with Internet Explorer 4. Likewise Internet Explorer 5 seems less hungry than Internet Explorer 4, Internet Explorer 6 seems to have gone back to a state that is nearer Internet Explorer 4.

MC Manager and Networks


Under the Multi Company manager we recommend that where possible all drives map to the same place. This makes supporting and maintaining your network simpler. N.B. At the time of going to print, to the best of our knowledge the Novell Lite network has been reported as unstable and being withdrawn by Novell. Under a WIN95 network, it is possible to map a local drive as a directory, so that all drives map to the same place. Add the following into the AUTOEXEC.BAT on the main machine; SUBST F:c:\Dirname This will map the root of F: to the directory 'Dirname' From the release of v4.20, it will be possible to edit the path under the multi company manager, and you will be able to map to different drives if you so wish. You would need to edit the path and take out the drive to leave it \Exch\ then machine 1 could map to J:\Exch and machine 2 could map to c:\exch. (the relative paths would still need to remain the same). Manuals in RTF Format Manuals are being prepared in rtf (word document format) for distribution with Enterprise. Some of them are available now in very rough draft but you must have the settings in word as shown in the bitmap below.

Having the RTF files overcomes the problem of printing pictures from the help file with pop ups clouding the printout. You will be able to select and print anything from the manual. Manuals under development. Manual Status Getting Started Rough Draft Stock Rough Draft OLE Rough Draft Currency Rough Draft Report Writer Rough Draft Technotes Rough Draft Job Costing Rough Draft SL/PL/NL Just Starting SOP/SPOP Not started Yet Form Designer Not started Yet Any one who wants a pre release to proof read can request them provided you realise that they are rough draft and feedback would be appreciated. And before you ask there will be page nos and contents and even an index eventually but Rome was not built in a day and my time to generate these is limited by other commitments.

Mapping
*Mapping - getting it right You need to map all drives to the same place, and avoid the root of the server, and also avoid long path names, example step by step instructions are below; 1) Map part of the server as drive M. 2) create sub directory EXCH. 3) Go to W/S and map to drive M. 4) Open up drive M and check Exch is under it. 5) Double check, M:\Exch is the same on both machines, server and W/S 6) Go to W/S and copy the live version from the local drive to M:\Exch so that if you want to find custsupp.dat, you would open up my computer, drive, exch, cust. And make sure this is the same from Server as well. 7) Then run upgrade Ent from Server, pointing at M:\Exch. 8) Check you can get in to Ent, and Exch on server. Then come out. 9) Go to W/S and from a fresh boot, go through M to Exch to Wstation, and do W/S install. 10)Check he can get in to Ent and Exch from Server and W/S 11)Then you may need to also upgrade additional Exchequer modules like Job Costing and Exch Report Writer, which you can do from either W/S or Server from the supplied CD or floppy disks. (NB: From v4.20 you can edit the multi-company manager therefore drives will not need to map to the same place, however relative paths will still need to be the same.) WHEN MAPPING TO ENTERPRISE, ENSURE THAT THE ENTERPRISE DIRECTORY IS NOT MAPPED AS THE ROOT. For example, ALL workstations should see the Enterprise directory as M:\Exch. Therefore if you wanted to run Exchequer, you would run the REX.BAT from M:\Exch\Rex.bat. (If it was M:\Rex.bat, it would be wrong)
Memory Errors Disk space being reported incorrectly This could be that Client they are using over the network is NOVELL32, as this seems to report free disk space incorrectly.

Also, uninstalling the Novell 32 client may not leave the Registry correct, it may leave some DLL's behind,which could explain why the disk size is still being reported incorrectly. Try re-installing the client.(Failing this, try re-installing Windows) In addition, check that the memory is not being managed through Windows, It seems that sometimes, users could have set the memory, Conventional and EMS, through Windows. They may have either set it incorrectly, or Windows may be failing to manage the memory correctly itself. Make sure there is enough free DOS memory, and try letting Windows manage DOS box memory automatically. Memory Leak in ODBC Memory Leak with ODBC 2.54.0.300 Issue: Memory leaks in the ODBC driver with the following query: insert into randall2 (col1, col2) select First_Name, First_Name begins with 'A' ?? Right(Rtrim(substring(First_Name, 1, 5)), 5) :: substring(First_name, 1, 5) from Person; (Query is based around Demodata) Solution: Service Pack 5.

Memory Problems Error 203


Not enough memory Error 203 To find out how much memory is available (base memory), drop into DOS and type MEM. The largest executable file wants to be at least 560-570K. If it is not, you will need to free up more memory. This can be done by editing two files, CONFIG.SYS and AUTOEXEC.BAT. Before you edit either we suggest you copy both files by: copy config.sys config.sec copy Autoexec.bat autoexec.sec Then if you need to go back to the originals you can copy the files back e.g. copy config.sec config.sys copy autoexec.sec autoexec.bat You can load many drivers, and even parts of DOS into high memory, you will need to refer to your DOS manual as to how to do this. You could try running MEMMAKER from version 6 onwards of DOS, but we do not recommend it.
Mismatched ODBC Components Issue: When Creating a Data Source using the ODBC Administrator or accessing your database via MS Access through Pervasive ODBC driver, you may encounter the following error: The ODBC resource DLL (C:\WINNT\SYSTEM32\ODBCINT.DLL) is a different version than the administrator C:\WINNT\SYSTEM32\ODBCAD32.EXE). You may also see the following error when you use Crystal Reports v6.0 to access the data via Pervasive ODBC driver v2.5x: Specified driver could not be loaded due to system error 127 (Pervasive Software ODBC -32). These errors can occur due to mismatched Microsoft ODBC system components. One way to replicate this problem is to install Crystal Reports 6.0 on a system that already may have MS ODBC Driver components installed. For instance: 1. Install MS Office 97 which will install MS ODBC driver version v03.00.2301. 2. Then install Crystal Reports. Some of the ODBC*.* system components will be overwritten and, as a result, you will have a mixture of MS ODBC driver manager v3.0.2822 and v03.00.2301.

Another method of replicating the problem is to: 1. Install Pervasive ODBC driver 2.5x. The Pervasive ODBC installation will install MS ODBC driver v2.50.3006 06/06/95. 2. Then Install Crystal Reports. Some of the ODBC*.* components will be overwritten, and you will have a mixture of ODBC v3.0.2822 and v2.50.3006 drivers. Solution: First reboot the workstation Uninstall Pervasive ODBC driver Remove ODBC*.* from your \system or \system32 directory Install Pervasive ODBC driver Reboot the workstation Install the MS ODBC 3.x system components from MS ODBC 3.0 SDK or Office 97.

Motor Scale Charge


Motor Scale Charge. Firstly we suggest that any accounting practice should be verified with your Accountant. Quick Method. You cannot post directly to the VAT control accounts, therefore set up HMCE as a client, and raise a journal (SJI), enter the amount of the MSC as a negative and put to the petrol nominal code on the transaction line, then edit the VAT manually to the same amount. The transaction will store with nothing outstanding, and the VAT will be amended. This would result in the required movement between Output VAT and, for example, the petrol nominal account. Full Method. The only slight problem with the quick method is the Net value and VAT content of the VAT report will be out by the amount of the Motor Scale Charge. To effect the net amount as well, you would need to use a Sales Receipt with invoice (SRI). A worked example is below. From the tables supplied by HMCE if for example the table showed; Motor Scale Charge 330.00 VAT per car 49.14 The 330 is inclusive of VAT, so; (330 /117.5) * 100 = 280.85 Therefore, enter a SRI for 280.85 and post to the petrol nominal account, and leave at standard VAT, adjust if necessary to the 49.14.

Then when you come to do the payment part, also put this to the Petrol account. We suggest that you split this amount up to show the VAT content as per the picture below.

The result is in effect two movements, which can be seen more clearly by splitting the payment part of the SRI as below; 1) Movement in and out of petrol of the 280.85, Debit and Credit which cancel each other out. 2) The desired movement between the petrol and VAT account. We also recommend that you use automatic journals to automate this process.

Move v4.10
Using move in the Nominal Ledger, in some cases in 4.10, when moving nominal accounts from one level to another, sometimes didn't move all levels of the history. As a result, the balance sheet won't make sense. Where possible, try moving the accounts back to their original positions. If you cant remember which accounts you've moved you will need to do a full unpost and re post to resolve. Then upgrade to the latest version. See Unposting

Multi Company Manager


Additional note for use with the Multi-Company Manager. Running Exchequer(DOS) under multi-company manager. - Copy all .SYS files from the MAIN company directory into the additional company's directory. (This will allow the option 'Exchequer' from the multi-copmany manager to work correctly) - To set up a short cut to the Rex.bat file, for the MAIN company this remains the same. - To set up a shortcut for an additional company; 1) copy the shortcut to the MAIN company. 2) rename the shortcut. 3) make the following additions to the 'command line' which reads something like; C:\Exch\Rex.bat to read as follows; C:\Exch\Rex.bat /DIR: {full path} for example; C:\Exch\Rex.bat /DIR: C:\Exch\addcomp If companies were created before the multi-company manager was installed, then given a release code

the following situation may occur; You can Get to Enterprise for the MAIN company, and the ADDITIONAL Company, you can get to Exchequer for the MAIN company, but for the additional company the security check screen comes up with '..' as a security code. You will need to copy the *.SYS (excluding mcompman.sys) files from the MAIN directory into the Additional companies directory, then load the multi company manager, and select file/security release code,this should cure it.( Remember to delete all the exe files in the additional companies directory, and point all shortcuts to the MC manager.) Also see Mapping and Disabling

Multi Currency & Stock Revaluation


Summary of changes to v4.10b All Multi Currency Stock Control Versions from v4.10b The ability to prevent any balance sheet nominal from being revalued introduced a potential conflict with regard to stock valuation in that although the balance sheet value for stock would remain unvalued, the cost of sales calculation would be at the current rate. This conflict has been overcome for FIFO,LIFO, Serial No. valuation methods by storing the exchange rate of the FIFO/LIFO entry at creation time, and using it to express the cost of sales back at the original rate. House keeping :- for Fifo stock items, running 'check' will store the rate for existing Fifo entries. Summary :- if NOT revaluing stock, from v4.10b use FIFO LIFO or SERIAL/BATCH so that exchange rate is preserved. For other methods use sterling only.

Multi User License This screen shows and allows you to give a new release code to increase the number of users allowed on a system and this code can be obtained from the help desk at Exchequer.

NT ISSUES
A recent report from one of our resellers stated that a 5 user NT based Client Server site had been experiencing severe stability problems when attempting to use Enterprise on Windows 95 Workstations connecting to an NT3.51 Server. With the aid of compass and smart scout the problem was traced to a second backup network card installed on the server which was being mistaken by the Btrieve Client Server engine as the primary network card and consequently causing errors. Although this problem is quite obscure, it does highlight the benefit of addressing IPX segments of networks instead of leaving them as default since it is possible to address individual cards with an IPX address under NT to help resolve this type of conflict. IPX addressing has been made a lot easier under NT 4, but is still required.

Networks in general
Novell Networks; Novell Lite - Unstable and has been withdrawn by Novell.

Personnel Netware - Problematic, it does run, but we have notice problems in connection with sharing printers such as timing out on slow print jobs. Novell Intranetware - Another version of 4.1 netware and is fine. Should be aware of possible problems with Turbo FAT as with Netware, for which there is a patch. NT Networks; All service packs should be applied, and ensure the NT Screen saver is disabled on the server, as well as the clients.

Nominal Ledger
Difference between nominal total and sub-total Q: I have discovered a difference between the Cost of Sales total and the sum of the sub-totals underneath. A: The computer is imbalanced somewhere. Suggested solution is to unpost and repost. Take full backup of system, then phone SBS to be talked through unposting. Once complete, repost and check amounts again. Nominal Based Reports All main nominal headings must have carry forward figure to "Financed by" (including Profit and loss). For operating profit put c/f figure in last line before financing costs and carry forward to "financed by". Nominal Set Up of second system If running two companies on Exchequer, the nominal layout can be copied from the first to the second copy nominal.dat file. Nominal codes Pre set up Nominal ledger before installing on site Set up nominal layout on blank Exchequer, then copy onto disk: copy c:\exch\trans\nominal.dat a: When new version of Exchequer installed on site, copy files into new system: copy a:nominal.dat c:\exch\trans (Or change directory into C:\exch\trans and copy a:nominal.dat etc). Always check that control codes haven't been changed. Utilities - System Set Up - Nominal Control Codes. If nominal.dat will not copy: see Read Only Files
ODBC Error: SQLSTATE = S0002 Subject: FYI00927 - "ODC Error: SQLSTATE = S0002, Native error code =-1305" when try to open System Files in SQL Data Manager Title: Error Opening System Files in SQL Data Manager Issue: You may get error ODBC Error: SQLSTATE = S0002, Native error code = -1305 No such table or object. Unable to open table: X$File.- when different locations for Data Dictionary Files (DDF) and Data Files in Pervasive.SQL 2000 prevent the user from seeing the data in System Tables for the database or use Create Table Wizard to populate table definition for a Btrieve file in a location different than DDF files.

Solution: As a workaround, put DDF and Data files in the same directory. This has now been entered as a defect 19577.

OLE Error 500-699 Btrieve error, take 600 from the number and see error list for standard Btrieve Errors. (Eg error 602 in OLE is error 2) --------------------500 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 Server Error (OLE Incorrectly configured. See OLE Help) Invalid GL Code Invalid Year Invalid Period Invalid Currency Invalid Customer Invalid Company or Canceled Logon Invalid From GL Code AddNomTransfer Invalid To GL Code AddNomTransfer Invalid Cost Centre AddNomTransfer Invalid Department AddNomTransfer Invalid Job Code AddNomTransfer Invalid Job Anal Code AddNomTransfer Invalid Stock Code Invalid Price Band Invalid Value Invalid Supplier Invalid Location Permission Denied - User not authorised to use this function Invalid Document Type Invalid Budget Type Invalid Total Type Invalid Rate Type Invalid Posted/Committed Flag Invalid Start Date Invalid End Date Invalid Account Code Unknown Error Aborted By User Invalid Aging Date Invalid Quantity Invalid Aging By Units Invalid Aging Interval Invalid Line Number Invalid GL List Invalid Description List Invalid Currency List Invalid Amount Invalid Amount List Total Not Zero Invalid Cost Centre List Invalid Department List Invalid Job Code List Invalid Analysis Code List Invalid Rate Invalid Rate List Invalid Alternate Stock Code No prices stored on Alt Stk Code record Invalid Line Type Invalid VAT Code Invalid Revised End Date Stock/Location Field Disabled

562 563 600

Save Functions Not Available Job Closed Record Lock Error

SEE ENTEROLE.HLP for further information on OLE.

OLE Exception Error on NT4


(The following is an extract from Pervasive Software's Tech Talk) Title: GPF with ODBC Document ID: ODBCTT33 Reference ID: Creation Date: 09/23/97 Modified Date: 10/22/97 Document Revision: 1.0 Product: ODBC for Windows NT/Windows 95 Version: 2.x Environment: Windows NT, Windows 95 Category: Status: Verified Access: Public Author: Michael Beris Keywords: ODBC, GPF, ODBCCP32.DLL, ODBCCP32.CPL, DSN, Data Source, SP3, Service Pack 3, Office97 ISSUE When creating a data source name (DSN) using the Pervasive Software ODBC Interface for Windows NT/Windows 95 on a Windows NT 4.0 Workstation with Service Pack 3 installed, a General Protection Fault (GPF)in ODBCCP32.DLL or an error message, "An error occurred while Windows was working with the Control Panel file ODBCCP32.CPL," may occur. SOLUTION A Customer reported this problem, and it was resolved by applying the Office 97 Service Release 1. ----------------------For further OLE Errors See OLE.HLP. ------------------------------------------------------OLE Error on NT
If when installing an upgrade or doing a W/S install on NT the update windows OLE files is ticked several files will be lost. The following list is the files you need to copy back from another workstation windows\nt\system32 directory. OLE2.DLL OLE2.REG OLE2PROX.DLL OLE2MLC.DLL OLEDISP.DLL OLE2CONV.DLL OLEPRO32.DLL OLECLI.DLL OLESRV.DLL COMPOBJ.DLL STORAGE.DLL

MSC40.DLL MSVCRT.DLL MSVCIRT.DLL MSVCRT40.DLL SEE ENTEROLE.HLP for further information on OLE.

OLE Troubleshooting
If you have been through the linkage tutorial and are still having problems, check which version of the OLE server you are looking at, and which version of the add-ins using by using the two functions below: Entserverver() Entaddinver() Entaddinver2() Entstkaddinver() entstkaddinver2() Check that the version match the Major Enterprise version that you are using. Eg. v4.00.123 for Enterprise v4.00. Note that entstkaddinver2() & Entaddinver2() are only available to system with OLE Save released. SEE ENTEROLE.HLP for further information on OLE.

Other rebuild utilities


The utilies described here can be fould in the Utils Directory of you Tecnote CD. There are other utilities that can aid when rebuilding such as BUTIL and BCLEAN. BCLEAN is a Novell utility that can be an aid as it can be used to re-create headers, and you need to be licensed to use BUTIL. ******************* Sample Batchfile to use Butil to repair Reports.dat (view this full screen) -------------------------------------------------------cut here------------------------------------------------------------------@Echo OFF REM ******************RECOVER.BAT***************************** REM REM Make sure correct version of Butil and you are REM licensed to use it. REM REM Copy reports.dat and Btrieve into a temp directory REM with this batch file, if v6.15, copy BTI.CFG, PMSWITCH REM and BSTOP into the directory, as well as the files for REM BUTIL which are; REM BUTIL.EXE, BUTILDOS.MSG, and BREQUEST.EXE and BREQUEST.MSG REM Only clone old dat file if 'clean' dat file is unavailable. CLS REN Reports.DAT Reports.SEC Btrieve REM Btrieve /U:1 *U:1 needed only For v5.10 BUTIL -CLONE Reports.DAT Reports.SEC REM BUTIL -COPY Reports.SEC Reports.DAT *Copy is not as effective as Recover & Load BUTIL -RECOVER Reports.SEC Reports.SEQ BUTIL -LOAD Reports.SEQ Reports.DAT REM BCLEAN Reports.SEC Reports.DAT *BCLEAN is a Novel Utility, v5.10 Btrieve only DEL Reports.SEQ

BUTIL -STAT Reports.DAT > repdat.txt BUTIL -STAT Reports.SEC > olddat.txt BSTOP REM BUTIL -STOP *for version 5.10 ECHO Finished..... ECHO Now compare the 2 reports, repdat.txt and olddat.txt ECHO Pay particular attention to the number of records Pause -------------------------------------------------------cut here-----------------------------------------------------------------******************* Using BUTIL to recover a file (expanded). 1) Create a new Btrieve file. a) use BUTIL -CREATE with a description file to create a new Btrieve file. b) BUTIL -CLONE clones the file based on the old file's header. This should be used second to a BUTIL -CREATE due to the fact that the control information for the file may be corrupt. 2) Move the data from the corrupted file to the new file. Any of these methods to recover the file can be used. a) Using BCLEAN, recover the file. b) Using BUTIL -RECOVER, BUTIL -LOAD, recover the file. c) Using BUTIL -SAVE, BUTIL -LOAD, recover the file. d) Using BUTIL -COPY, recover the file. (Remember if rebuilding on the server use butil.nlm, or if rebuilding from a workstation at a client server site, load the requester brequest or breqnt instead of Btrieve.)
Note: BUTIL.EXE is a developer tool shipped with Btrieve Development Kits. BUTIL.NLM is shipped with NetWare SQL and is available on CompuServe (NOVLIB Library 7, BUTNLM). BCLEAN can be found on Compuserve in Library 7 in BTOOLS.ZIP.

Payroll Export from Job Costing


The file layout explained below is for 'Earnie' and is fixed length, this is the format that Intex Software use. Intex Software produce 'Earnie' which is a payroll package. Each line is made up from 3 parts. (10 Characters, 2 characters, and 8 characters) Field 1 This is 10 characters long, and is the employee code (From the Employee Record - Payroll number) This is the only simple field, fields 2 and 3 will take a bit more explanation. Fields 2 and 3 There is the Pay Rate (This is set in job costing under utilities, time rates, payroll code) and this can be

from 1 to 10. And there is the number of hours for each rate, for each employee. For every pay rate used we export 2 lines, field 1 is like a key field and this starts each line. We then give the information of the pay rate and number of hours, but unfortunately not simply. (It is in the format that Intex have requested to suit their package, so you may need to write something to manipulate the data into your required format) 10chars line1 Employee code line2 Employee code 2chars Pay rate (Pay rate + 20) 8chars (No. of hrs * 100) (Pay rate * 100)

So for Example that data in the system is; Employee01 1 2 Pay rate 5 10 No. of hours

The Exported data would be (in fixed length fields); (10 char) EMPLOYEE01 EMPLOYEE01 EMPLOYEE01 EMPLOYEE01 (2 char) (8 char) 1 500 21 100 2 1000 22 200

Pentium 2
Bulletin 24th October 1997 Pentium II (P2/P6) issues ~~~~~~~~~~~~~~~~~~~ Further to the previous announcement regarding the compatibility of Exchequer (DOS) and the new Pentium II processor; the problem has been narrowed down to a timing issue caused by the speed of these new faster processors. In essence they are running too fast for some DOS programs to cope with. After subsequent testing the problem has been successfully cured. The fix will be incorporated within the forthcoming release of Exchequer v4.21. This problem extends to all upgrade, installation and add on modules, which will all be re-released. Unfortunately conversions prior to v4.20 will need to be run on non P2 machines. The v4.20 conversion and all future conversion will be P2 compatible. Enterprise was not affected by this issue.

Periods
Exchequer can quite happily deal with 13 periods in a financial year. however, we would suggest that you switch off the 'set period relative to date' question in system set-up, and you need to remember to change F6 at the end of each four week period. This is because the switch 'set period relative to date' is only a monthly feature, instead you will be moving the period on manually.

CHANGING DATES/PERIODS NB. Period 11/92 to 10/93 will always show as 92, i.e. May 1993 will be period 7/92. This causes confusion, particularly every January when actual year changes. Suggest if after a split year when moving onto a calendar year use numbers for months instead of words until period 1 of new accounting year. Q: Our financial year starts in January but if F6 set to 01 1993 the month comes up as April. A: Check year start date in General Settings - this is probably set to April.

Phonetic alphabet
A - Alpha B - Bravo C - Charlie D - Delta E - Echo F - Foxtrot G - Golf H - Hotel I - India J - Juliette K - Kilo L - Lima M -Mike N - November O - Oscar V - Victor P - Papa W - Whiskey Q - Quebec X - Xray R - Romeo Y - Yankee S - Sierra Z - Zulu T - Tango U - Uniform

Posting
Q: Posting run done but transactions still remain in daybooks. Why? A: Check period set in "F6", and dates and periods of transactions. Transactions cannot be posted ahead of today's date/period. Brought forward figures on Posting reports On certain new systems sold recently figures have been carried forward on the first posting report - to remove them simply unpost and repost all transactions. Q: Can I carry on adding transactions whilst posting? A: The only way would be to put a 'suspend' on the last entry you want to post on the daybook before posting. Otherwise Exchequer will try to post transactions that are being added and problems will occur. If you are posting the daybook(s) in protected mode then it is OK to continue posting transactions. Q. When I try to post in Protected mode the machine hangs and nothing gets posted. A. Try rebuilding JOBS\Jobmisc.dat.

Print Queue in Enterprise


There are no plans to include a print queue in Enterprise. This is because there is the facility under Windows 95 to 'work off line'. This is done by selecting the printer and then using a right click, and putting a tick against work off line. Print jobs will then automatically queue, until you choose to enable the printer again.

Printing Problems
Also see: Unknown Form printing statements - Terminal Service Printing Fix - 2000 Server. (Still Under review) http://support.microsoft.com/default.aspx?scid=KB;EN-US;q328020& may help some issues There is one obvious thing that should be checked like: 1) Is the printer mapped accordingly over the network. 2) Is it switched on and on line and have paper in it.

Q. Client calls and he cannot get anything to print. A: Need more information, firstly Exchequer or Enterprise. If Enterprise 1) Is a default printer set up? 2) If so check no screen saves or other TSR programs like Virus scanners are running in the background. (this can be the cause of many unexplained errors and is documented in Entread If still having problems what are they trying to print? 1) If it is a form, check the form is set up. (Global defaults in form designer) 2) If the form has been altered, check the alterations for any errors. Try printing to screen, if it is a large report it may be that the size of the document is causing the problem. Under Windows NT there can be a problem with printing large documents or reports over a network. It is a conflict between a program that controls printing 'Spool32' and NT so printing to screen first then sending the output to the printer is a work around for the time being. Q. Document prints but some of the details are missing. A. If the document will print but some of the details are missing, like the last column on a trial balance. Try decreasing the unprintable area. If you are still having problems try a different printer driver, a later or more recent driver may achieve better results. Q. Enterprise hung printing a number of invoices. A. Again try a different driver, for example some users have reported when printing to a Hewlett Packard LaserJet 5 printer a LJ3 printer driver proved to be more satisfactory when printing multiple documents. It could also be that the driver for the printer, may not have installed properly itself. one user had inconsistent printing problems, tried re installing the driver and the problems evaporated. If you still can't get anything to print, try printing in Exchequer, it could be a problem that is isolated to Enterprise only. If this is the case report it and check you are on the latest version. Printing problems in Exchequer. If there is a problem printing in Exchequer, again check the obvious. 1) Is it on with paper in it and is it online. 2) Is the form definition set up in the system setup If not the standard form, how has it been altered? Try printing the standard form, then examine the .DEF and .LST files. Q. The form prints half way then stops. A. It could be that it has stopped at a corrupt field. try rebuilding the relevant files and try again. If it is just one transaction and a rebuild doesn't cure the problem, it is probably zero that transaction and enter a fresh one. the printer worked fine before, check the printer codes haven't been corrupted. Q. Running over a network, nothing prints in Exchequer until I exit Exchequer. A. This is more of a network problem. Firstly check the capture settings, and time out. For example on a Novell Network load up SYSCON to look at the Login scripts. There should be a line that says #Capture The # is because 'capture' is a DOS command, various parameters are passed to it. The /t is the timeout, try setting this to 20. If the parameter 'autoendcap' is included in the line, this will stop the printing until the package has been exited, so try removing it. Errors in printing reports in Enterprise could be caused by the printer driver used. For example the

Panasonic KXP-6100 has it's own print manager which initialises the printer before a print job. After reinstalling the printer driver and disabling the power saving features in the print manager Enterprise should print correctly. It is also important to note that when printing over a windows network, the printer names on each workstation should be the same.

Protected Mode Posting


If the system hangs on protected mode posting try rebuilding jobs\miscjob.dat as corruption in this file will cause this problem.

Problems Rebuilding
Problems when Rebuilding? Message on the log stating it had been unable to rename files ? It is quite likely that on the hard disk the .new files will be just sat there, in other words the rebuild has not completed,this is due to access rights, usually over a network. You can complete the rebuild by manually renaming the files *.new to *.dat. And next time if novell, log on as network supervisor, from a fresh boot. You MUST check for this, it is not good enough just checking the totals at the bottom. Logging on as network supervisor from a fresh boot is important, as often it is the only way to be sure that the user has the correct access rights, incorrect access rights may also return error 5. Q:Records Partially read in History.dat, and no back-up to go back to ? A:Ideally, you should revert to a back-up, so if you cannot, follow the procedure below; 1) Stress the importance of good back-up's and set procedures. 2) Do a back-up, then if you only have partially read records in history.dat you can try to recreate the History. 3) Do a full unpost, and check history zeroes down. (If it doesn't zero, do a blank install into a temporary directory, and copy history.dat across, this must be the same version) 4) Do a full repost, then check all account balances, and check all stock. 5) Audit accounts attemption to identify the missing transactions or Records. ** Error 2 in Rebuild? Normally you would have to go back to a back-up. There are other utilities that could be tried, BUTIL which is provided by Btrieve (you need to be licensed to use it), BCLEAN - which is a Novell utility, and you could try to upgrade to the latest version and try running the latest rebuild module. But these options may well prove to be less successful than the rebuild module. THERE IS NO SUBSTITUTE FOR A BACK-UP. CHECK THAT A BACK-UP AND ROTATION PROCEDURE IS IN PLACE MAKE SURE THE BACK-UP SOFTWARE IS IN WORKING ORDER, AND THAT YOU CAN RESTORE FROM A BACK-UP.

Getting Error 2 may also be down to the options in BTI.CFG, if you go from one version of Btrieve to another, as outlined in the scenario below; Q: Problem with Error 2 MLOCSTK.DAT, after a recent upgrade, and still running v5.10 of Btrieve A: This could be caused by the file not being created in correct version of Btrieve. Edit BTI.CFG and add /D: parameter to options, Then run the rebuild externally. (Via the Rexbuild batchfile) If the file was created for v6.15 of Btrieve, and it needs to be v5.10, rebuilding will convert it to v5.10, please remember to edit BTI.CFG to exclude the option once complete. NOTE: If the files are version 5 Format Enterprise Protected Mode Posting will be disabled.. Problems unloading Pervasive under Netware(4.x and 5.x) Enhancement 16194 PROBLEM: After modifying Btrieve configuration parameters often Btrieve needs to be restarted in order for it to use the new values. On NW5 (and recent service packs of NW 4.11) it is not possible to issue a BSTOP command. This happens because of OS NLMs (such as CSL.NLM) holding references to BTRIEVE.NLM (which in turn has dependencies on NWMKDE.NLM). There is a circular chain of NLM references and it becomes impossible to shutdown Btrieve. Several customers have been complaining about this. SOLUTION A method is required for de-coupling BTRIEVE.NLM and NWMKDE.NLM so that NWMKDE can be shut down and restarted. It is assumed that users of this facility are aware of the risks involved in shutting down NWMKDE if applications still have open files etc. An NLM obtains references to symbols in other NLMs by 1) Specifying them in an import list at link time and having the OS resolve those imported symbols at the time the NLM is loaded, or 2) Using the ImportSymbol API to import a symbol at run time. So, as a first step Btrieve.NLM needs to use the ImportSymbol API to import the symbols it needs from the MKDE (in particular the mkdeID() entry point). To detach from the MKDE the UnimportSymbol could be used later to get rid of a symbol reference. Now a method is needed to inform BTRIEVE.NLM to perform the UnimportSymbol() in order to do a forced shutdown. The simplest idea seems to be use the RegisterConsoleCommand() NW API. This allows an NLM to register a command line parser and any command typed on the server console that NW does not recognize is passed to the registered parsing routine to handle it if it so desires. BTRIEVE.NLM will register a command line parser. If the command BTRV UNLINK is typed then Btrieve.NLM will detach itself from the MKDE by unimporting any MKDE symbols that it was using. At this point NWMKDE.NLM can be unloaded without any problems. After the NWMKDE is restarted BTRIEVE.NLM needs to be told to reattach itself to the MKDE. This is done through the BTRV LINK

command that can be placed inside BSTART.NCF. The BTRV UNLINK command must not be placed inside BSTOP.NCF. BSTOP will remain the same as before. Quite often people issue a BSTOP without realizing that other software (e.g. SSQL) may be using BTRIEVE. The errors from BSTOP (because of referenced symbols) give them an opportunity to cleanly shutdown the other software that is using Btrieve. By typing BTRV UNLINK administrators make explicit their intent to force a shutdown of Btrieve. Issuing the BTRV LINK (or BTRV UNLINK) command a second time in succession should not have any effect. Users of this feature must be aware of the risks involved. If an NLM is actively performing Btrieve operations at the time the "BTRV UNLINK" command is issued then that NLM will receive Btrieve errors because Btrieve.NLM can no longer pass on calls to the MKDE. This is not the case with an NLM like CSL.NLM, which does not have any Btrieve files open when the system is in steady state. So it is still recommended that entire system be restarted whenever possible since by shutting down NWMKDE.NLM any NLMs that continue to perform Btrieve calls will get errors (status code 20) because the MKDE is not loaded. By virtue of the fact that OS NLMs are accessing Btrieve.NLM then Btrieve.NLM effectively becomes an OS component itself and it is not unusual for the OS to require restarting after config parameters are modified. Various scenarios considered: 1. LOAD BTRIEVE (MKDE is not running) BTRIEVE will auto-load MKDE as before, and then import the symbols it needs from the MKDE. 2. LOAD BTRIEVE (MKDE already running) BTRIEVE will just import needed symbols from MKDE. 3. UNLOAD BTRIEVE BTRIEVE will unimport symbols first and then shut itself down. 4. BSTOP (but some OS NLMs are using Btrieve) NW will not allow BTRIEVE to be unloaded. So the NWMKDE cannot be unloaded as well. This is the same as before. At this point the Admin can attempt to unload NLMs that are using Btrieve. 5. Forced shutdown Admin will issue the following commands BTRV UNLINK and BSTOP BTRV UNLINK will unimport the symbols Btrieve is using from the MKDE. When BSTOP is run; BTRIEVE will fail to unload as before. But NWMKDE will get unloaded. An explicit command ensures that admins are aware of what they are doing. 6. Restart after a forced shutdown. BSTART.NCF must be modified to have the following command BTRV LINK after the LOAD BTRIEVE command. When doing a restart after a forced shutdown the LOAD BTRIEVE command will fail with the error that BTRIEVE is already loaded. The BTRV LINK command tells the loaded BTRIEVE to reattach itself to the MKDE. 7. Normal BSTART The BTRV LINK command will have no effect. Other Info 1. The commands "BTRV LINK" and "BTRV UNLINK" must be typed exactly as shown with a single space separating the two words. 2. If BTRIEVE.NLM is not loaded then NetWare will display the error message "Unknown command" if either the BTRV LINK or the BTRV UNLINK commands are issued. Documentation Changing configuration parameters usually requires shutdown and restarting P.SQL components.

Under certain configurations of NetWare it is not possible to shutdown the MKDE because some OS NLMs (such as CSL.NLM) have references to Btrieve.NLM. In these cases the only method of restarting Btrieve has been to reboot the entire system. With this enhancement (16194) it becomes possible to shutdown and restart the MKDE (NWMKDE.NLM) even though BTRIEVE.NLM is being referenced by other NLMs. However it is still recommended that entire system be restarted whenever possible since by shutting down NWMKDE.NLM any NLMs that continue to perform Btrieve calls will get errors (status code 20) because the MKDE is not loaded. By virtue of the fact that OS NLMs are accessing Btrieve.NLM then Btrieve.NLM effectively becomes an OS component itself and it is not unusual for the OS to require restarting after configuration parameters are modified. Issue the following commands on the NetWare server console to perform a forced shutdown: 1) BSTOP (or SQLSTOP) 2) Note the errors and attempt to shutdown all the NLMs that are still accessing Btrieve and the MKDE. If it is not possible to unload all of them because of circular references and it is desired to force a shutdown of the MKDE, perform the following commands 3) BTRV UNLINK This command must be typed exactly as shown above with a single space separating the two words. This command detaches BTRIEVE.NLM from NWMKDE.NLM thus allowing NWMKDE and other NLMs to be shutdown on the next step. 4) BSTOP After this command only BTRIEVE.NLM and NWAIF103.NLM remain loaded. Note that BSTART.NCF has a BTRV LINK command in it. So a subsequent BSTART will automatically reattach BTRIEVE.NLM to NWMKDE.NLM. Users of this feature must be aware of the risks involved. If an NLM is actively performing Btrieve operations at the time the "BTRV UNLINK" command is issued then that NLM will receive Btrieve errors because Btrieve.NLM can no longer pass on calls to the MKDE. This is not the case with an NLM like CSL.NLM that does not have any Btrieve files open when the system is in steady state. Tests These tests are manual 1) On a NW 5.0 (and NW 4.11 SP 5/6) BSTART Verify that after the BTRV UNLINK and BSTOP commands are issued as described above then the NWMKDE.NLM gets unloaded and that Btrieve.NLM remains loaded. 2) On NW 5.0 (and NW 4.11 SP 5/6) BSTART BTRV UNLINK BSTOP Run a Btrieve NLM application (e.g. the test case for Enhancement 17306) and verify that it receives error 20. 3) With no P.SQL components loaded issue the LOAD BTRIEVE command. Verify that the MKDE gets automatically loaded. 4) If #1 is performed on a NW 3.12 system there should not be any adverse effects. All Pervasive NLMs should get unloaded.

Problems with Matching


Transactions that have been allocated that have zero amount outstanding are still appearing on customer statements.

If multi-currency, check that there is nothing o/s in currency, and consolidated. Filter by sterling and consolidated. There may be something still showing as O/S. If nothing is showing as O/S,it may be that there is a tiny amount O/S like .001 of a penny. firstly, just try pressing Allocate, as this can some times tidy it up. If not, go in under SYSTEM, and change rate in currency set-up back (When other users are NOT adding any transactions) Un-allocate, then re-allocate, then change rate back. (Effectively, rematching should clear) Remember you need to match payment first, match the payment to the invoice. If matching goes wrong reports like Aged Debtors/Creditors will sometimes not make sense as they rely on this information. Note: Under the System password, you can leave the ledger with an amount outstanding, which will have zeroed the next time you go back to the ledger. Should you do this incorrectly, you will have to use check, and Un-allocate, and rematch the ledger.

Purge Documentation
As of v4.20 of Exchequer it is possible to remove (purge) old historical data from the system. This will improve performance in some areas, and optionally reduce the overall size of the data files. There are reported faults in version 4.20 and 4.21 see Errors below. The purge routine is separated into orders and accounting data. Purging Orders ~~~~~~~~~~~~~~ This option is only available for SPOP versions of Exchequer, and allows the selective removal of completed orders up to and including a given period. it is possible to specify the inclusion or exclusion of specific customer and supplier accounts, if for example you do not wish to remove the orders from a single account. Purging Accounting data ~~~~~~~~~~~~~~~~~~~~~~~ This option is available on all versions of Exchequer. It is a destructive procedure and irreversible, so the need to backup in case of unexpected interruption cannot be Emphasised enough. Purging should only be done when you are satisfied the period you are purging up to is complete and finalised. Purging may only be performed up to and including whole accounting years. It also possible to instruct Exchequer to subsequently remove any empty customer or supplier accounts, empty stock records, empty locations, and used serial numbers sold within the purge year. Both purges give the option of shrinking the files after the purge is complete which involves the equivalent of running a rebuild on the main data files. Purging will remove any transactions with a financial period equal or less than the purge year specified. Any transactions which remain outstanding will not be purged. After a purge the Nominal Ledger will remain intact, although it will not be possible to drill down from some balances as the data will no longer be there. Any future unposting will only go back as far as the purge year, so transactions which remain from a purged period will not be unposted. During the purge a copy of the file HISTORY.DAT is placed in the file HISTPRGE.DAT. This copy contains balances for the purge period and will be used as a replacement to the main history file in the event of a total unpost. This file should NOT be deleted. The main History file is copied into HISTUP.DAT for emergency use only. If a transaction is added subsequent to a purge which belongs in a financial period prior to the purge, it will be accepted on the daybook, but will have no effect on stock or account balances, and will not be

posted to the Nominal Ledger. For this reason check on an account or stock ledger will ignore any transactions which belong to the purged period. If you run check on an account, and choose unallocated everything, it may be necessary to use the system password to reallocate transactions which no longer have the opposing allocating entry present within the ledger. If you run check on a stock account which uses FIFO valuation, an opening value equal to the posted stock level at the time of the previous purge will be added by the system. For this reason purging should only be performed when there are no unposted transactions containing stock movements with a financial period corresponding to that of the purge period. Purging must be performed on incrementing years, for example it is not possible to purge everything up to 1996, and then purge everything up to 1995. This system will also only allow purging up to one year before the current financial year. Reported Errors Two errors have been reported after purge. Check Cleared Accounts. If check is run on a bank account to recalculate the cleared value, the value calculated is incorrect. Should this happen, the interim fix is to "Move" the G/L account type to a different type, then "Move" it straight back to its correct type. This action forces Exchequer to recalculate the cleared value correctly. Check Stock Levels If check stock levels (individual or all) is run, the posted stock level value is incorrect. There is no work around for this fault at present, however if a site is suffering from this problem, an advanced beta of 4.22 can be made available to recalculate the posted stock level. Both problems are processing rather than data related, so although inconvenient, the fault is not permanent and can be fixed by running check on Ver 4.22 once it becomes available. This problem will only affect systems which have been purged. Non purged systems are unaffected by this issue.
Read only files To turn on/off read only files in Exchequer: cd\exch "SBSflag -R e*.exe" turns read only off. copy/change files, then "SBSflag +R e*.exe" turns read only back on.

Real-Time Data Compression and Data Compression File Flag Issue: What is the difference between "Real-Time Data Compression" and "Data Compression File Flag". Solution: 'Real-Time Data Compression' is a requester configuration option that allows the data being sent to the server to be compressed before being written into SPX or TCP/IP packets. This allows the data to be sent over the network in smaller and/or fewer packets, reducing network load and improving network performance. This option is only available on the DOS TSR requesters BREQUEST, BREQNT and BREQTCP. 'Data Compression File Flag' allows you to create a Btrieve file with compression enabled. In such a data file, records are stored on a disk in a compressed format. The engine reading and writing to the file compresses and uncompresses the records. In a Client/server environment, the server engine uncompresses a record after reading it from the disk and before sending it over the wire to the client application. This feature affects disk storage size only, and has no effect on network performance. It could, potentially, have an impact on the MKDE engine performance, since the MKDE has to compress/uncompress the data, but customer response has consistently indicated that no performance impact is seen when using compressed files. How To:"Real-Time Data Compression" is, by default, disabled. To enable this feature, load the DOS requester with the /O option, as in:BREQNT /O.

The "data compression file flag" must be set when the file is created; compression can not be enabled on an already existing file. Refer to the Pervasive.SQL Programmer's Reference for more information on creating files with compression enabled.

Rebuild under Multi Company Manager


Running Rebuild under multi-company manager. - For the main company no change - For additional companies: 1) modify Rexbuild.bat to read; btrieve exchbuld %1 %2 bstop 2) copy printsbs.sys from main directory into the additional company's directory. (You may have already done this to run Exchequer) 3) If you are a non client server site take a copy of the BTI.CFG file to BTI.USR Edit the options line to say options=/L:20 /F:50 /H:60 /T:0:NUL /U:1 /W: /I: /B:1 /S:1 /M:1024 /G:500:5000 Then continue by runing Btrieve and Exchqr /AC as below not forgetting to copy BTI.USR back to BTI.CFG on completion. Drop into DOS and get to the main Exchequer directory and run Rexbuild with the command as follows; Rexbuild /DIR: {full path} for example; cd exch rexbuild /DIR: C:\exch\addcomp

Rebuilding Files
Also see the general note about rebuilding and special functions. This was introduced in v 2.22 negated using Novell's utility BUTIL (which required a license) See running Rebuild under Multi Company Manager Problem Storing a transaction Missing a Customer/Supplier Missing a Stock Record Missing transactions Suggested files to rebuild Rebuild document.dat (SF4 or SF12) details.dat and may need to move document and folio numbers on. Rebuild custsupp.dat Rebuild stock.dat Rebuild document.dat

Missing a nominal code Trying to post a daybook

Rebuild nominal.dat Restore previous backup Rebuild document.dat(all files) details.dat history.dat nominal.dat Rebuild exchqchk.dat (Exchequer DOS only) Rebuild exchqchk.dat Rebuild exchqchk.dat Rebuild details.dat

Help screens wrong Passwords gone Allocating a transaction Trans Lines Muddled, repeated lines(that are the same.) Screens corrupt

Restore from backup def044.sys (defmc044.sys) (Exchequer DOS only) Rebuild Document.dat Rebuild CustSupp.dat

Aging report stops part way through Arrow keys running through Customer or Supplier database playing up. (Throwing you back to the beginning)

Batch Payment screen unable to scroll Rebuild Exchqchk.dat and Exstkchk.dat up/down Notes pick up wrong information e.g. Customer notes pick up wrong Customer Notes. Wrong prices being picked up e.g. sales Order picking up cost price Rebuild Exchqchk.dat

Rebuild Exstkchk.dat Exchqchk.dat Stock.dat

Customer and Supplier lists records missing N.B There is no rebuild for Reports.dat, either use BUTIL or BCLEAN: if you are licensed to use them, or restore from a backup. N.B. Take a backup first - Everyone out of Exchequer - If rebuilding over a network, login as supervisor. If a rebuild has failed, check no one went into exchequer, or if errors are reported in the rebuild report concerning network rights, restore backup. Then log on from a fresh boot as supervisor and try the rebuild again. Also see problems rebuilding.

Release of v4.20b
Bulletin 29th September 1997 A few late changes which did not make the ENTREAD are as follows:-

V4.20 had problems restoring the correct colours when only 256 colours were available. This was caused by the introduction of the Euro logo, and has been fixed with v4.20b. In order to minimise the risk of mixing different currency upgrades, i.e.upgrading a single currency with a multi currency version etc., the Enterprise installation program,as of v4.20b now checks what type of installation is being upgraded, and compares it to the version on the CD. A suitable warning will be given if a mismatch is found. This should prevent the current problems associated with such a mistake.Please note this checking has not been extended to the Exchequer only disk based upgrades, so normal vigilance is required with Exchequer.

Reports
General Q: When producing Quarterly Management accounts, I really want to see a specific quarter trail balance and all the headings broken down. A: The Trial balance shows current period and YTD. Nominal history shows breakdown of each heading between periods. Q: What is the Stock reconciliation report ? A: This shows the stock movements (Eg from one Balance sheet to another.) Q: The nominal history report is suddenly going into condensed print seems to be caused by a sign in the description of one of the invoice lines. A: The computer is reading the # as a printer code. Try not to use # signs at all. If the invoice has been posted, the printer definition codes must be changed to IBM graphics. Aged Debtors and Aged Creditors Reports If you believe you may have a problem with your Ageing reports, first post all daybooks, and print a trial balance. Check your trial balance balances, and then as a first step prove, your current general ledger balance. To prove your current general ledger balance print the report with the following options Summary=yes, outstanding only=no, backdate to period=no. These reports are "live" - they show invoices outstanding at this moment. As long as all the invoices for the period selected are posted, the "posted total" is the total amount outstanding for each customer/supplier at that date. Backdating reports is possible (and the ageing by currency is retained from v4.20a) provided the matching information is correct. Print reports with options as follows summary=yes, outstanding only=no,backdate to period=yes. Q: Outstanding invoice not appearing on Aged Creditors Report, although it is definitely outstanding and appeared in the posting report and on supplier's ledger? A: Check that it is not on the daybook with Query against it; If not, it may be a corrupted transaction. To remedy: 1). reverse original invoice. 2). manually add an identical invoice. 3). allocate on ledger and post. 4). the invoice should now show on aged creditors report at time it was due. VAT will not be affected as PCR and PIN contra each other in same VAT period. You may also consider rebuilding details.dat document.dat and history.dat, contact the support department after taking a back-up if you require assistance to perform the rebuild.

Also check the matching information, if this appears corrupt, try re-matching the transaction. (Always match the payment first, then the invoice.) Q: Imbalance on Aged Debtors Report - total outstanding on Aged Debtors Report does not equal the posted balance (everything is posted); however the total posted balance does.? A: Check the customer ledgers - if a customer has an imbalanced ledger, press "check" and answer "no" to unallocate documents and re-print the report. If the report is still incorrect run check again, and unallocate, (you will then need to re-allocate the transactions and may choose to use the 'settle' function). The report should now be OK.
Reset Logged in Users If a user tries to log in to the system and it says no more logins available first try taking everyone out of the system login one user and straight back out again. If this does not reset the count correctly then make sure no users are in the system log in as SYSTEM with the password given by the help desk and go to Utilities\System Setup\License Options\Reset Logged Users and the screen below will show. When you login normally the first user should check in Help Session Information that the count is at 1.

Revaluation problems ?
Revaluation not working, after following the procedure outlined in the manual no nominal is created? Check transactions are posted (and the F6 period is set accordingly) Check that the Nominal Accounts via F4 (General ledger drill down) are set to revalue Check both the Daily and Company rate being altered during reval procedure. Check no currencies have a daily or company rate of zero via currency set-up. Check Nominal Control codes set-up (Firstly via F4, and secondly under Utilities / General Settings / Nominal Control Codes.). Example of control code and nominal structure layout for a limited Company is below;

Special Function 45 - Convert existing currency 0 auto bank rec matching lines to currency 1. This needs to be run after a single to multi currency conversion if items left o/s on the Auto bank if rebuild pre v4.24a. Check needs to be run afterwards on the bank rec screen. Special Function 1 - Repair damaged document Do not use on v1.19 of rebuild This is used in cases where transactions such as Invoices or Stock Adjustments can be found using the F8 find Document hot key but the same transactions cannot be found in any ledger, or are missing from Aged Debtor/Creditor Reports. This function also cures instances where transactions are appearing in the wrong ledger such as Sales Deliver Notes appearing in the Normal Sales Day book. No corruption can occur by running this function. All transactions which contain an Account Code are also checked to ensure :1. The Account Code exists 2. If it does exist it is checked to make sure it is the correct type for that transaction. If either of these checks fail the Account Code is replaced with the default Customer/Supplier Account Code as specified within System Setup. It is therefore essential valid Account Codes exist within these default fields before using this function. NOTE This Function also Validates Transaction Periods. If a system ever had more Periods per Year than is currently set in System Set-up then System Set-up must be set to this value before running this function. E.G.. on the first year of using Enterprise they had a 15 period year, this was subsequently changed to 12. Set System set-up to 15

period/year before running SF1. Do not Forget to change system set-up back to the correct number of periods afterwards. As of version 5.60 this function has been modified to fix corrupt header exchange rate fields as well as Account codes and date fields. See SF102 if corrupt transaction casing debtors/creditors or check account to hang. Special Function 10 - Remove unposted run to lines. During a posting run Exchequer generates several automatic lines for Debtor/Creditor/Cost of Sales calculations. If the posting run is interrupted these lines will remain in the pre-posting report indefinitely. This function removes any unposted automatic lines. Special Function 11 - Stock Code and Group clear up. Filters out invalid characters caused by incorrect import. Also strips out any leading spaces from stock description which can cause the price list report to print unnecessary blank lines. Special Function 12 - Returns O/S orders from History. Scans the Order History Day Books for any orders with lines still showing as outstanding and returns them to the normal Order Day Book. (Also see SF22) Special Function 13 - Set Customer pay terms and fix re order list. Routine developed for a specific user, set the Customer payment terms to 920 Days and Supplier to 30 Days. Also fixes a problem caused by stock import which prevented the interactive re order list from working correctly. Special Function 14 - Set all unposted transactions daily rate to Company rate MC only. Sets a blank daily rate to it's equivalent company rate on unposted transactions. Special Function 15 - Copy "Remit To" code into "Invoice To" code. Sets the Invoice To field the same as the Remit To field on the Customer/Supplier database. Special Function 16 - Reset lost transaction line Posting Run Numbers. Checks any posted transaction lines run number and sets them to the same run number as the transaction header. Can be used to correct transactions that are missing from the nominal drill down. Special Function 17 - Set Print Statement switch. Routine developed for a specific user and has been added to set the Print Statement switch on all Customer records to Yes. Special Function 18 - Set min reorder flag on all location records. Recalculates the minimum and maximum reorder flag for all location stock records and should only be used on beta systems of Multi Stock Locations prior to b320. Special Function 19 - Fix Multi currency revaluation when rate set to zero. Revaluation was done with exchange rate of 0, and then could not get any o/s transactions subsequently to show a base equivalent. SF19 runs through all unposted transactions and cancels any effect of revaluation. This will be shipped with v 4.20 Exchequer . Special Function 2 - Convert all unposted currency 0 documents to currency 1. Extreme danger of corruption if this is run incorrectly! This function is used to convert single currency transactions which have been added to a multi currency system. All transactions which need converting must be unposted. Designed originally to correct a situation where multi currency version was down graded to single currency in error. Also used when the import module has imported single currency data into multi currency system by not specifying the multi currency switch. Special Function 20 Clean up alloc sterling with amounts o/s Cleans up allocated sterling transactions where there is an amount o/s in sterling, but none in base. Customer specific request, to perform one off calculation to correct multi-currency problems. Special Function 21. Recode Suppliers Auto recodes all suppliers using the first 2 chars of company name followed by 4 digits. renames all notes and transactions, deletes all history files. Done by request for a customer. Special Function 22 - Scan Historical Orders. Special Function 22 has been added to scan all historical orders, and reset to 0 any which still register on the stock ledger. 1) Run SF12 first to make sure that all the orders in history, should be in history.

2) Run SF22. 3) Check all stock to recalculate correct balances. Special Function 23 - Checks and reports on any corrupted transactions. This function should be used to check on the extent of a suspected problem, it should only be used if all other methods have been tried (eg unpost/repost) and there is no uncorrupted backup available to revert to. This must always be run before attempting to run SF24. Special Function 24 - Checks and deletes any corrupted transactions. Before running this function you MUST have run and checked special function 23. If any of the transactions are financial and have been posted and allocated it. is advisable to unpost back to the period involving the corrupt transactions. If they are non financial transactions, run check all accounts/stock. This function will remove all transactions that have been reported in Special Function 23 . Special Function 25 - Deletes all notes from all Accounts Customer and Supplier. This function will remove all notes from the customers and suppliers records. This involves no financial transactions and can be run whenever required. Special Function 26 Sets up Alternative Database records from existing Alternate Codes on the Stock File. This special function has been provided to run through all the stock records and insert a record into the alternative code database, for any existing alternate codes. Special Function 3 - Remove all matching information. This function removes all matching information i.e. invoices matched to receipts. The routine is destructive and should be used only as a last resort, where the matching file has become heavily corrupted. Special Function 4 - Create missing Document header records. This function scans the details database and constructs a Document Header Record for any unposted details lines with no header. If a new header is created it will be allocated the next transaction number for that document type. The new document will be placed in the appropriate day book. It is important that the Error log is examined and that the transactions created are still required. Any that are not (because they were re entered for example) should be zeroed. Enhanced so it deletes corrupted lines which it cannot resurrect. Enhanced Rebuild v4.31 on so that floating ADJ lines with no headers are fixed, this will avoid having to go through using SetAFolio etc. Note: No totals are calculated for these transactions, it will therefore be necessary to edit the transactions via the day book in order for the total to be re calculated. Special Function 41 - Fix following SF39 problems Sets daily rate to 1.0 on all transactions, and forces the amount settled to be the same as the currency 0 amount settled. This routine should only be used in the event SF39 does not convert all o/s amounts correctly, which very early versions of SF 39 (rebuild v3.21a) were doing incorrectly. Later versions of SF39 (v3.22) onwards corrected this problem, and so running SF41 should not be necessary. Special Function 42 This is uses to fix a problem at sites like Fragrance Factory where they were using a 2 digit location code CP. The problem they were having was the inability to produce a picking list run. Once you removed the location filter the run would work. This was caused by the location code being set up as a default in the stock/customer record, when this default was copied into the transaction line it was not padded to 3 digits. This problem will be fixed in v4.23p of Enterprise, but sites with the problem now should follow these steps. 1. Backup! 2. Run SF42. 3. Change the location code in Enterprise from 1,2 digits to three digits ie CP to CP1. 4. Edit the location filter on the picking run to the new code i.e. CP1 5. It may be advisable to run check all stock if the location stock codes still contain references to the old location record. Special Functions 43 This will set all customer and supplier account records with EC set to Y and the default VAT code set to 3 or 4 to A & D. In addition any stock records with a 3 or 4 or Z vat code will be reset back to S, as the account record should determine whether it is an acquisition or dispatch, not the stock record.

Special Function 44 - Set all unposted transactions Control G/L Code to the one on Cust/Supp File Default. Used for anyone wanting to split debtors control codes. Do total unpost Add Multiple Debtor/Creditor General Ledger Codes Set Customer/Supplier Account to new default. Run SF44 Check footer of a few transactions to ensure they are set correctly to the default Debtors/Creditors Control GL before reposting all daybooks on month at a time to check TB and Debtors/Creditors in Balance. Special Function 5 - Sort transaction lines after re build. After a data rebuild it is possible for Stock Ledgers or Nominal Ledgers to be listed in a different order. This function re sorts them into folio number/ Line Position in Transaction order.This is negative for Non Financial Transactions (Orders and ADJs), this means that ADJs and orders will be sorted to the top of the list. This is not ideal but better that some/ many transaction showing in reverse order. Special Function 57. Scans all unposted sales daybook (Not orders) transactions, checks any lines containing a stock code, and if the line cost is zero, sets it to the cost in the stock record. Special Function 6 - Sort transactions after rebuild After a data rebuild it is possible for Customers/Supplier Ledgers to be listed in a different order. This function resorts them into folio number order, in other words the order they were entered in. From DOS rebuild v4.31.05 and Enterprise 4.32 This function promts for sort by Date or Folio Number Special Function 62 SF 62 sets all PIN's and PCR's to Authorised. This will apply to posted and unposted transactions. Any previous hold status other then Suspend and Notes will be overwritten by Authorised. Special Function 64 There was a problem with triangulation if Sales or Purchase orders are still outstanding at the time Triangulation is applied. Any subsequent documents generated from these orders cause corruption in the stock valuation, and VAT returns. Before you can run SF64, you need to do the following. * Partial unpost back to first transaction generated from one of these orders after triangulation has been applied. To make this period easier to find, locate the revaluation journal generated at the time of the triangulation and also make a note of its period and Nom Number, as this will be required by the SF64. This journal will give you a clue how far back to partially unpost. * Make a note of which currency number the euro is. Once these steps have been taken, run exchequer and choose special function 64.You will be asked to enter the number of the Triangulation revaluation journal. You will be asked to enter the number of the Euro currency. SF64 will search for SIN,PIN.SDN& PDN's generated after the date of the nominal, and correct the triangulation error. It will also search the FIFO & Serial number databases for these entries and correct those. Special Function 7 - Sort transactions and lines after rebuild. If transactions start appearing at the top of the ledger, rebuild and try SF7. This function performs SF5 & SF6 together. Special Function 8 - Set stock re order price same as cost price. This function sets the re order price within the stock record from last cost price within the stock record. Special Function 9 - Set cost price to 0 on all transaction lines. Sets the last cost price/uplift price to 0 on all transactions. Used in cases where corruption has caused the cost price to become meaningless and of no use. SQL Setup Items Missing from Setup Utility Issue: When using the Win32 Setup utility from Service Pack III with the Pervasive.SQL Workstation engine and connecting to a server running Pervasive.SQL, the option to edit the SQL configuration does not appear. Why? Resolution: Check the Remote Usage settings for Scalable SQL under Scalable SQL Requester/Access Control. If this requester is set to Off, a connection to a remote SQL engine is not possible. To fix the long time delay problem when connecting to a server that does not have a SQL engine running, the utilities were changed in Service Pack III to check the SQL Requester setting. If this setting is Off, then the Monitor and Setup utilities will not try (or show) the SQL settings.

Scalable SQL Engine Messages


This section lists the messages that the Scalable SQL engine generates. SSQL 0 SSQL 1 SSQL 2 SSQL 3 SSQL 4 SSQL 5 SSQL 6 SSQL 7 SSQL 8 SSQL 9 SSQL 10 SSQL 11 SSQL 12 SSQL 13 SSQL 14 SSQL 15 SSQL 16 SSQL 17 SSQL 18 SSQL 19 SSQL 20 SSQL 21 SSQL 23 SSQL 24 SSQL 25 SSQL 26 SSQL 28 SSQL 29 SSQL31 SSQL 32 SSQL 33 SSQL 34 SSQL 35 SSQL 36 SSQL 37 SSQL 38 SSQL 39 SSQL 40 SSQL 41 SSQL 42 SSQL 43 SSQL 44 SSQL 45 SSQL 46 SSQL DOS 19 SSQL DOS 27 SSQL DOS 28 SSQL NW 19 SSQL-0: An error occurred while filename was being loaded. Insufficient memory is available, or the executable file is corrupt. Under Windows, the operating system does not have enough memory to load the specified DLL for the Scalable SQL for Windows engine, or the DLL file on the disk is corrupt. For insufficient memory, try using a larger swap file or adding more memory. For a corrupt file, reinstall the engine files. SSQL-1: An error occurred while filename was being loaded. The file was not found. The Scalable SQL for Windows engine could not load the specified DLL or EXE file because the file or one of its dependent DLLs was not in the path. Ensure that the file or DLL is in the path. SSQL-2: An error occurred while filename was being loaded. The path was not found. The Scalable SQL for Windows engine could not load the specified file because the file or one of its dependent DLLs was not in the path. Ensure that the file or DLL is in the path. SSQL-3: An error occurred while filename was being loaded. A file sharing error occurred. The Scalable SQL for Windows engine encountered a file sharing error while trying to load the specified file. Try reloading the file. SSQL-4: An error occurred while filename was being loaded. Error 6. The specified file is corrupt. Reinstall the specified file. SSQL-5: An error occurred while filename was being loaded. Insufficient memory is available to load the DLL. Windows does not have enough memory to load the DLL for the Scalable SQL for Windows engine. Try using a larger swap file or adding more memory. SSQL-6: An error occurred while filename was being loaded. The incorrect MS Windows version is in use. The Scalable SQL for Windows engine requires Windows v3.1.

SSQL-7: An error occurred while filename was being loaded. The executable file is invalid. The Scalable SQL for Windows engine could not load the DLL or EXE file because the file on the disk is corrupt. Reinstall the engine files. SSQL-8: An error occurred while filename was being loaded. The incorrect operating system is in use. The Scalable SQL for Windows engine requires Windows v3.1. SSQL-9: An error occurred while filename was being loaded. The system is designed for use with MS-DOS v4.0. The version of MS DOS must be v4.0 or later. SSQL-10: An error occurred while filename was being loaded. The type of executable is unknown. The Scalable SQL for Windows engine encountered an error while trying to load the specified file. Try the operation again. SSQL-11: An error occurred while filename was being loaded. The real-mode executable cannot be loaded. The Scalable SQL for Windows engine encountered an error while trying to load the specified file. Try the operation again. SSQL-12: An error occurred while filename was being loaded. Error 16. The specified file is corrupt. Reinstall the specified file. SSQL-13: An error occurred while filename was being loaded. The executable is compressed. The Scalable SQL for Windows engine encountered an error while trying to load the specified file. Ensure that the file is not compressed and retry the operation. SSQL-14: An error occurred while filename was being loaded. The DLL is invalid. The Scalable SQL for Windows engine could not load the specified file because the file on the disk is corrupt. Reinstall the engine files. SSQL-15: An error occurred while filename was being loaded. MS Windows 32-bit extensions are required. The Scalable SQL for Windows engine encountered an error while trying to load the specified file. SSQL-16: An error occurred while filename was being loaded. An unknown load error occurred. The Scalable SQL for Windows engine encountered an error while trying to load the specified file. Try loading the file again. If necessary, stop and restart the Scalable SQL for Windows engine and try to load the file. SSQL-17: Scalable SQL cannot link to the needed module: filename. A Scalable SQL component tried to link to filename but filename does not export a needed symbol. A common problem is if Novell's NETAPI.DLL is being loaded instead of Microsoft's NETAPI.DLL. Ensure that you are using the latest version of filename.

SSQL-18: DefineEntryPoints failed. Scalable SQL v3.x has insufficient memory to complete process initialization. Try using a larger swap file or adding more memory. SSQL-19: The file filename is not loaded. This message appears after other error messages to inform you that the file is not loaded. SSQL-20: The process could not be initialized. Scalable SQL v3.x has insufficient memory to complete process initialization. Try using a larger swap file or adding more memory. SSQL-21: The MicroKernel Database Engine is not loaded. The Scalable SQL engine could not load or access the MicroKernel. Ensure that the following MicroKernel components are in your path: For NetWare, NWMKDE.NLM, which must be loaded before loading Scalable SQL. For Windows NT, NTMKDE.DLL, which is loaded by Scalable SQL. SSQL-23: Insufficient memory is available to load messages. The operating system does not have enough memory to load the messages from the resource DLL. Try using a larger swap file or adding more memory. SSQL-24: This Scalable SQL engine must be run with the fully-licensed MicroKernel Database Engine! The Scalable SQL engine is designed to run only with the fully-licensed and distributable MicroKernel for the corresponding platform. Make sure this version of the MicroKernel is loaded. The Scalable SQL engine includes a copy of the correct MicroKernel. Purchasing the Scalable SQL engine gives you the right to copy and distribute both engines with an application. SSQL-25: This Scalable SQL development engine must be run with the MicroKernel Database development engine! The Scalable SQL development engine is designed to run only with the MicroKernel development engine for the corresponding platform. Make sure the MicroKernel development engine is loaded. The Scalable SQL Developer Kit includes a copy of the Scalable SQL development engine and the MicroKernel development engine. These two engines are licensed to support five concurrent users in a development environment and are not licensed for distribution. SSQL-26: Unexpected MicroKernel Database Engine status nn during engine initialization! Scalable SQL failed to initialize because the MicroKernel Database Engine returned an unexpected status code indicating that it cannot be used. Refer to Chapter 1, "Status Codes," for a description of Status Code nn. SSQL-28: The trace file filename cannot be opened. Scalable SQL could not open the specified trace file. Ensure that the path and filename are valid. Also ensure that you have enough free disk space and that the file is not read-only.

SSQL-29: The Scalable SQL Engine cannot load configuration information. Scalable SQL returns this message for one of the following reasons: In Windows NT, the Registry key used to store settings cannot be created. Use RegEdit to determine if the following keys have been created. If they have not, try to create them. The keys are as follows: HKEY_LOCAL_MACHINE, SOFTWARE, Pervasive Software, Scalable SQL Server Engine, Version 4.00, Settings HKEY_LOCAL_MACHINE, SOFTWARE, Pervasive Software, Database Names, Version 4.00, Settings In NetWare and DOS, the BTI.CFG file cannot be opened or locked. Ensure that BTI.CFG is writable and that BTI.LCK is not present. SSQL-31: An error occurred while filename was being loaded. xxxx. A fatal error occurred while the Database Service Manager was loading the filename. Refer to the detailed message (xxxx) to resolve this error. SSQL-32: A Database Service Manager error occurred. xxxx. A fatal error has occurred in the Database Service Manager. A detailed description (xxxx) follows the error message. SSQL-33: The xx network protocol failed to initialize. Error code: nn. Ensure that the xx protocol has been configured correctly. Once you receive this message, the xxx network protocol is no longer available. The following are possible error codes: 1 Wsock32.dll is not available or could not be loaded. 2 Too many instances. This is an internal error and should not occur. 3 Out of memory. 4 Invalid Instance ID. This is an internal error and should not occur. 5 Not initialized. This is an internal error and should not occur. 6 Protocol Unavailable. The Scalable SQL engine is configured to use a protocol that is not available on this system. Use the Setup Utility to check the setting for the Scalable SQL Communications Manager, Server Communication Configuration and Supported Protocols. Available protocols are SPXII and TCP/IP. 7 Protocol not supported. The Scalable SQL engine is configured to use a protocol that is not available on this system. Use the Setup Utility to check the setting for the Scalable SQL Communications Manager, Server Communication Configuration and Supported Protocols. Available protocols are SPXII and TCP/IP. 8 Error opening socket. Windows NT system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. 9 Error Creating an I/O port. Windows NT system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. 10 Error Creating Thread. Windows NT system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. 11 Error Initializing Protocol. Possible causes are: Out of memory or error creating a thread. Windows NT system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. The Windows Sockets implementation may have detected that the network subsystem has failed. Verify that the network subsystem is operational.

This machine's name and address cannot be determined. Verify that your name services are configured correctly and are operational. Depending on the configuration of your computer, this could include DNS, WINS, DHCP, and a static HOSTS file. 12 Invalid Communications Buffer Size. Use the Setup Utility to check the setting for the Scalable SQL Communications Manager, Server Communication Configuration and Communications Buffer Size. It should not be 0. 13 Invalid Parameter. This is an internal error and should not occur. 14 Engine Callback not specified. This is an internal error and should not occur. 15 Error not listening. This is an internal error and should not occur. 16 Error not working. This is an internal error and should not occur. 17 Timeout on cleanup. This is an internal error and should not occur. 18 Insufficient Buffer. This is an internal error and should not occur. 19 Thread Initialization error. Windows NT system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. 20 Initialization is not reentrant. This is an internal error and should not occur. 21 Too many threads. This is an internal error and should not occur. 22 Error Creating Semaphore. Windows NT system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. 23 Error initializing protocol, retrying. This is an informative status that should cause Scalable SQL to display message SSQL-34.The xx network protocol failed to initialize. Error code: nn. Retrying... Ensure that the xx network protocol has been configured correctly. The Scalable SQL engine will continue to attempt initializing the xx network protocol. Refer to the text for SSQL-33 for a list of communications status codes. SSQL-35: The Scalable SQL Engine is running with no network protocol support. All selected network protocols failed to initialize or no network protocols have been configured. Remote access to the Scalable SQL engine is unavailable. Ensure that the selected network protocols have been configured correctly or use the Setup utility to select a different protocol. SSQL-36: The Scalable SQL Engine has not been configured to use network protocols. No network protocols have been selected to run with the Scalable SQL engine. Use the Setup utility to select one or more network protocols. SSQL-37: The Communications Server is not available. The Scalable SQL engine failed to load the Communications Server. Remote access is disabled. Ensure that the selected network protocols have been configured correctly. SSQL-38: The filename component is version n.n and must be version y.y or later. The filename module is an older version. Ensure you have the correct version of this module in your path. SSQL-39: An error occurred while using filename. Error code: nn. There was a problem using the filename module. Refer to error code nn for detailed information. SSQL-40: An error occurred while using filename. xxxx. There was a problem using the filename module. Refer to the message following the error message for detailed information.

SSQL-41: The Scalable SQL Engine is running with a user count of zero. A problem occurred while obtaining the user count because the user count is not configured correctly or it has not been incremented. Use the User Count utility to configure the user count. Because the user count is zero, you only have local access; remote access is disabled. SSQL-42: Unexpected status "nn" received creating system threads. During the Scalable SQL engine's initialization process, an error occurred in creating system threads. The system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. SSQL-43: Unexpected status "nn" received creating worker threads. During the Scalable SQL engine's initialization process, an error occurred in creating worker threads. The system resources may be low. Try rebooting the system on which you are loading the Scalable SQL engine. SSQL-44: Unable to access named database information. Scalable SQL engine can neither open nor create the DBNAMES.CFG file. SSQL-45: An error occurred while loading Database Services. A fatal error occurred while loading Database Services. SSQL-46: An error occurred while loading the Scalable SQL engine. Error code: xx. 1 This is an internal error and should not occur. 2 Out of memory. Windows NT system resources may be low. Try rebooting the System on which you are loading the Scalable SQL engine. 3 Error creating Semaphore. Windows NT system resources may be low or a previous copy of DBSvcMgr did not exit cleanly. Try rebooting the system on which you are loading the Scalable SQL engine. 4 DBSvcMgr has received a new request but it was already signaled to shutdown. Wait for the Scalable SQL engine or MicroKernel to shutdown before starting another engine. 5 This is an internal error and should not occur. 6 The Scalable SQL engine module is already loaded. This is an informative status that should cause Scalable SQL to display Message SSQL-WNT-27. 7 This is an internal error and should not occur. 8 This is an internal error and should not occur. 9 Invalid DBSvcMgr command sent to DBSvcMgr. This could be seen if a newer stub is loading an older DBSvcMgr. Verify that the correct versions of all components are being used and are on you path. If the problem persists reinstall the engine files. 10 This is an internal error and should not occur. 11 This is an internal error and should not occur. 12 Components out of sync. Verify that the correct versions of all components are being used and are on your path. If the problem persists, reinstall the engine files. 13 This is an internal error and should not occur. 14 This is an internal error and should not occur. 15 This is an internal error and should not occur. 16 The Scalable SQL engine could not be loaded because the DLL could not be found. Verify that the correct versions of all components are being used and are on your path. If the problem persists, reinstall the engine files. 17 This is an internal error and should not occur. 18 Scalable SQL engine files could be corrupted. Verify that the correct versions of all components are being used and are on your path. If the problem persists, reinstall the engine files.

19 Scalable SQL engine files could be corrupted. Verify that the correct versions of all components are being used and are on your path. If the problem persists, reinstall the engine files. SSQL-DOS-19: The file SSQL.EXE will be unloaded. This message appears after other error messages to inform you that the file is not loaded. SSQL-DOS-27: SSQL.EXE is already loaded. Scalable SQL returns this message if you try to load Scalable SQL when it is already loaded at the DOS workstation. SSQL-DOS-28: Use SQLSETUP to modify options in BTI.CFG. Scalable SQL returns this message if you try to set options at the command line. You should use the DOS SQLSETUP.EXE to configure the Scalable SQL for DOS engine. SSQL-NW-19: The Scalable SQL Engine, nn, has shutdown. While loading, the Scalable SQL engine received an error and cannot finish initializing. The error is displayed before message SSQL-NW-19. Correct the cause of the error, unload and then reload the Scalable SQL engine.

Schedule of Stock Take - Live Stock


Pre-stock-take
Ensure that you have a good BACKUP! . From Utilities/Data Rebuild (Recovery in Exchequer DOS)/ Check All Stock Levels. The above is precautionary rather than mandatory as it ensures that the Live and Posted stock levels shown are all correct. (This function is possibly better performed in Exchequer for DOS as it will be quicker as Windows will be Multi tasking Even if this is performed as a |STAND ALONE| operation). It will take a while and is probably best performed: overnight. Run the report in report writer to ensure there are no negative stocks, and sort out any problems. (Print a stock take report from Reports/stock/stocktake report, showing stock levels if you do not have Report Writer, highlighting any -ve items). Print out the stock take sheets in a useful way for the counting but also to help with easy data input. Again the above is a precaution, basically because people cannot read or count. (Sorry but this is a fact of life), 'to err is human' Any slow moving lines can be pre-counted. All stock on the premises MUST be delivered in and processed through into a PDN or PIN stage, the same also applies to any stock due to go out that is not being counted, it must be at SDN or SIN stage (IMPORTANT!). This is the stage at which you decide if you are going to FREEZE the stock using live or posted levels. Be very sure you know the difference. LIVE includes all PDN, PIN, SDN, and SIN transactions that are still on the Daybooks.

POSTED Excludes these transactions. Basically, if you have PDN, PIN, SDN, SIN transactions that are on the daybook and you elect to use LIVE levels, the stock for these transaction must have affected the stock in the bins. IE for sales they must NOT be in the stock bin and for Purchases they MUST!. Then you will be using LIVE levels and answer yes when asked; 'Do you want to use the current Live stock levels'. If the reverse is true then you MUST answer NO to this question.

Stock Take
As soon as the last transactions have been processed for the day, from the main menu : 1) Order Processing 2) On Screen Stock 3) Stock Take List 4) Freeze (Z) 5) Confirm you wish to start a new Stock Take (Y) 6) Use posted Stock (N) VERY IMPORTANT!!! (see above!). 7) Count ALL stock items. (During this process NO STOCK MOVEMENTS can be added) 8) Once all the stock has been agreed, processing can be continued. 9) Enter the quantities counted. It is not necessary to enter a qty for items where the count is the same as the 'in stock' and 'actual' are the same. 10) When the entire stock take has been entered Process the stock take screen. This then gives you an ADJ on the Issues and Adjustments Daybook, print this out for reference.

After Stock Take


The only remaining thing to do is to print out a Stock Valuation report from the Stock reports category. Product group Leave Empty Summary Yes Live Stock Yes (IMPORTANT!!!) (See If you Need live or posted as above) Valuation Type Leave Empty Administration. When the Stock take ADJ is posted, it will (on live stock) create a NOM. Verify that you are happy with this value. Be aware that as with all stock valuation NOMs generated from Stock adjustments (ADJ), these Journals are Currency 0 (Consolidated) in a Euro or Multi Currency system. All paperwork relating to stock included in the stock take should be entered in the period of the stock take irrespective of the invoice date. When all paperwork has been entered and the Balance Sheet & Profit& Loss Report Printed any differences between the Stock Valuation & the Balance Sheet should be adjusted via a nominal journal. Basically if you are happy with the stock costings, and therefore the stock valuation report, this is the value that the stock nominal account should agree to.

Security release codes


The Multi-Company Manager has been modified in 4.20 so that the Release Codes are only available under the system password. In order to login under the system password the 'Login menu option on the File Menu must be used.

There are three extra options available under Utilities\System Setup\License Modules that become available when you log in under SYSTEM with the appropriate password for the day obtainable by calling the Exchequer Helpdesk. These Three options are:Multi User License Reset Logged in Users License Modules. The other option available now is the Error Log
Server Specific Error 4083 on a Windows NT Server Issue: Rebooting Windows NT server after a Pervasive.SQL install causes a server specific error 4083 - The services failed to initialize. The original mappings exist, however the drives are disconnected from the server. The system also fails to generate PVSW.LOG since the services are inoperable at restart. Solution: Check the available protocols on the server and load either TCP/IP or SPX to resolve the problem. Pervasive.SQL supports TCP/IP and/or SPX with NetBIOS. Note: Pervasive.SQL does not support NetBEUI. Ensure this is not the only loaded protocol on the server. How To: Refer to Windows NT Operating System manuals for Protocols installation.

Title: Service Pack 4 and Win9x Connectivity Issues Issue: After the Service Pack 4 installation for Pervasive.SQL 7.0 on Windows 95/98, the system experiences delay in connecting to the engine. Solution: Stop the applications using the Registry editor, under HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Microkernel Router\Version 7.01\Settings\.Set Target Engine to 0. and Restart the system Warning you are editing the Windows registry and Exchequer Software accept no responsibility for you doing this.

Setafolo
When storing a non-financial document, if an error 5 is encountered the internal folio number may need to be moved on. Setafolo is the utility to do this, and can be downloaded via our Web site, instructions on how to use Setafolo are below; Setafolo is a utility to access and change Exchequer's internal folio number. This program is run from DOS, and btrieve needs to be running first. Run it from the command prompt and it will reveal the current internal folio number, this is negative. To move the folio number on run Setafolo again with the new folio number (this will be a negative number also, but closer to 0 than the current folio number). For Example running v6.15 of btrieve, copy Setafolo into the Exchequer directory, and at the command prompt type; btrieve (return) Setafolo (return) {Setafolo will display something like;

*** Ver 6.15 Type :D< Auto Folio currently set to -2140000000} Setafolo -2135000000 (return) {Setafolo will display something like; *** Ver 6.15 Type :D< Auto Folio currently set to -2140000000 Auto Folio now set to -2135000000} bstop (return) Should you have any queries contact Exchequer Helpfile support.

Setting up EURO
When setting up New Euro sites we recommend the following; Set-up currency consolidated as Euro, (therefore currency1 as Euro) and 2 as sterling. At present all transactions should be in currency 2 as they are in-fact sterling. later, they will be currency 1. So for the time being it would be best to set customers up to default to currency 2, and change this later when necessary. In addition VAT currency must be set to 2 in System Setup for reporting purposes. And all rates should be 1.0 at this point in time.
Special Function 65 Client specific to clean up SRC006081 Account POR857. This SRC contained corrupted data as can be seen within the user field at the top of the transaction. The variance and discount amounts had corrupted values which have been reset to zero. It is not anticipated that there will be any financial knock on effect. Special Function 66 Cleans up corrupted reconciliation flags on imported transactions lines in the nominal. Symptoms When Drilling into the GL code from the GL Tree, the View pops up and immediately closes. Special Function 67 Scans all unposted sales daybook (Not orders) transactions, checks any lines containing a stock code, sets it to the cost in the stock record translated to the currency on the transaction.

Special Functions
Also see a general note about rebuilding and special functions. These are functions written for various reasons to cure problems and put files back into sequence. Always ensure an up to date Backup is taken prior to running ANY Special Function. All functions highlighted in blue are one-off client specific fixes. Do not use on live data. Thoroughly test the effect on a copy of your clients data prior to using on a LIVE system. SF1 Repair damaged document Do not use on v1.19 of rebuild.

SF2 Convert all unposted currency 0 documents to currency 1. ( Caution!) SF3 Remove all matching information. SF4 Create missing Document header records. SF5 Sort transaction lines after re build. Folio Order(Stock/Nominal) SF6 Sort transactions after rebuild Folio/ Date Order Cust/Supp. SF7 Sort transactions and lines after rebuild. SF5 + SF6. SF8 Set stock re order price same as cost price. SF9 Set cost price to 0 on all transaction lines. SF10 Remove unposted run to lines. SF11 Stock Code and Group clear up. SF12 Returns O/S orders from History. SF13 Set Customer pay terms and fix re order list. SF14 Set all unposted transactions daily rate to Company rate MC only. SF15 Copy "Remit To" code into "Invoice To" code. SF16 Reset lost transaction line Posting Run Numbers. SF17 Set Print Statement switch. SF18 Set min re-order flag on all location records. SF19 Fix Multi Currency Revaluation when revaluation performed at zero rate. SF20 Clean up allocated transactions with amounts outstanding. SF21 Recode Suppliers with 2 char company + 4 digits. SF22 Scan Historical Orders. SF23 Checks and reports on any corrupted transactions. SF24 Checks and deletes any corrupted transactions. SF25 Deletes all notes from all Accounts Customer and Supplier. SF26 Sets up Alternative Database records from existing Alternate Codes on the Stock File. SF27 Set all unposted journals to have a period and year of 07/1997 - Client Specific one off. SF28 Sets all o/s SOR & POR's next delivery date index. Can sometimes cure situations when orders are not being picked. SF29-38 One off data fixes Client Specific. SF39 SC->MC conversion.. SF40 One off deletion of ALL unposted SJI's from SJI000001 to SJI014031. SF41 Fix following SF39 problems. SF42 Pad 1 or 2 digit location codes to 3 digits (SPOP only) SF43 Set A/C 3&4 Tax code to A&D. Set Stock 3&4 to S. SF44 Set all unposted transactions Control G/L Code to the one on Cust/Supp File Default. SF45 Convert existing currency 0 auto bank rec matching lines to currency 1. on SC to MC convert if rebuild pre v4.24a. SF46 Re-establishes the account code on job actuals from the original transaction line. SF48 Removes all Customer Matching. SF49 Removes all Supplier Matching. SF50 Unallocate all Sales Transactions and remove all Customer Matching. SF51 Unallocate all Purch Transactions and remove all Supplier Matching. SF52 Client Specific to move settlement discounts from the trading terms to the new correct fields. SF53 Client Specific to get rid of the failed protected mode posting warnings produced after a move failed. Would also remove failed Posting warning But NOT advised without a GL audit as the TB may not balance or Posting codes may not = headings. advise UNPOST/REPOST FIRST!! SF54 Function needs to be run prior to adopting triangulation rates. Flags all transactions as being pre triangulation. SF55 Sets customer settlement discount from system setup. SF56 Sets supplier settlement discount from system setup. SF57 Resets Costs on unposted Sales transactions (Not Orders). SF58 Reset the triangulation Flag on Serial/FIFO records. SF59 Cleans up PDNs & PINs created from 10 digit POR's. SF60 Fixes account ledger filter fault, where very little gets filtered out, caused by corruption. SF61 Is designed to delete any serial number notes with no effective parent. This is a blind fix.

SF62 Sets all PIN's and PCR's to Authorised. SF63 Resets the last debt chase letter level to 0 for escalating type debt chase letters. SF64 Fix for Sales or Purchase orders still outstanding at the time Triangulation is applied. SF65 Client Specific to clear up corrupt transactions. SF66 Cleans up corrupted reconciliation flags on imported transactions lines in the nominal. SF67 Client Specific. Set all Transaction Stock Cost to Stock Record Cost. SF68 Convert UK STD Telephone Codes for April 2000. SF69 Client Specific. Recalculate all Sales Invoice Cost values. SF70 Client Specific. Zeros uplift on all purchace transactions. SF71 Set ALL Blank Stk Loc Trans Lines. SF72 Client Specific. Deleted an unposted zero value transactions which have a period less than the last purge period. SF73 Fix Corrupt Import NOM + ADJ With Job Cost Codes. SF74 Clear hidden BOM lines from historical Orders. SF75 Client Specific. Set ADJ BOM Line Cost from Stock Record. SF76 Set Send Email Reader on all Customer records. SF77 Set Send Email Reader on all Supplier records. SF78 Reset Employee Certificate Expiry Date. SF79 Client Specific. Recalculate all O/S Sales Order Cost Values. SF80 Client Specific. Set Unposted Sales BOM Line Cost to zero. SF81 Sets the 'Include on Web' flag on all Customer records. SF82 Sets the 'Include on Web' flag on all Supplier records. SF83 Sets the 'Include on Web' flag on all Stock records. SF84 Repair matching on reversed SOP transactions. (Win Only) SF85 Client Specific. To remove stock lines on Corrupted SRC/PPY Transactions (Win Only) SF86 Pad all Alt YourRef fields to correct duplicate Your Ref Check.(Win Only) SF87 Client Specific. Reset corrupt Posting Run Number ob SIN001402 (Win Only) SF88 Remove Un Posted Job Costing Actuals if original transaction line is missing. (Win Only) SF89 v5.00 Exchequer index test, to support new allocation routines. SF90 Destroy Purged years History for Purged Customer/ Supplier Accounts. SF91 Destroy Purged years History for Purged Stock Accounts. SF92 Remove all Order matching information for Currencies 3&8 (For Exchequer Internal Use ONLY) SF93 Pad Account, Stock, and Transaction Line CC/Dept to 3 Digits. SF94 Reset Currency 0 settled Value Pro (SINGLE CURRENCY) Only. SF95 Reset Currency 1 or above settled Value Global (Multi Currency) Only. SF96 Remove JC Committed lines if original document line is missing or effect in JC is Nil. SF97 Remove Corrupt Account and Stock Discount Records. SF98 Remove Corrupted FIFO records. SF99 Reset sold Batch Records still marked as unsold. SF100 Delete Copy/Reverse Audit note from all Transactions. SF101 Reset allocated status on all settled Transactions. SF102 Client Specific. To allow corrupt transaction lines that cannot be edited to be deleted. SF103 Client Specific. Deletes all serial/batch records after incorrect import. SF104 Corrects the payment flag on PINs after corruption in Toolkit or Authoris-e plug in. SF105 Deletes all serial/batch records where the in document was a POR. Required following Import error. SF106 Client Specific. To reset corrupt SIN061869 line date SF107 Reset stock record notes counter to 1 on all stock records. All stock note records should be deleted before running this function. SF108 Client Specific. To reset corrupt SRC000001. SF109 Delete duplicate Master Location Records. SF110 Delete redundant Bin Child Usage Records. SF111 Delete Duplicate Job Category Lines Note: Check all jobs should be run following this Special Function. SF112 Delete redundant Bin Master Records.

SF113 Reset TeleSales Account Control Records. SF114 Client Specific. Clear corrupt POR lines from historical Purchase Orders.

Stock Reconciliation Fix


Differences on the reconciliation report (when it is operating correctly) are normally caused by ADJ's. When an ADJ is posted it generates a NOM for the G/L movement. If this NOM does not get posted, or it is amended to another value, it causes differences in the report. A decision must be made as to which figure is thought to be more accurate, the G/L balance or the report balance. If the G/L is thought to be wrong then a simple NOM will fix the problem. If the G/L figure is correct and the report is wrong then the following procedure will rectify the problem. If a difference occurs in any Stock Value G/L code. and the exact cause cannot be isolated to a particular stock item, then a dummy ADJ needs to be created as follows. 1. Add an ADJ for any stock item with the Stock value G/L code which is wrong with the In qty = 1.0 cost = value of difference for G/L code. 2. Add another line for same stock item Out qty = 1.0 cost = 0.0 When this posts it will generate a NOM. 3. Edit this nom and delete all the lines from it. The effect of this is to correct the report, but leave the G/L balance alone. Assuming the G/L balance is correct. 4 Repeat Steps 1 to 3 for a stock item belonging to any other stock G/L code which is out of balance.

Stock Valuation EOP to Live


Changing from End of period to live stock valuation. We suggest this is effected at the end of a period, and that you note your financial records accordingly; 1) Post all daybooks. 2) Perform a stock valuation and a stock-take. This is to validate that the stock records are correct at the time of the change in valuation method. 3) Check and amend the nominal codes for your stock records. With reference to the write off field, this will now be used purely for posting stock writeoffs when stock adjustments have been posted. A separate stock write-off account could be located with-in the expenses section of the nominal ledger, or the same as cost of sales and we suggest you seek your Accountants advice if unsure. You will also need to change the description of the Purchases nominals to Cost of Sales. 4) Change the question in system set-up Live stock / COS Valuation to yes. 5) Change the nominal codes in the transaction lines of any remaining Purchase Orders, Quotes and Delivery notes to the stock value nominal code. As purchases will now stock on the balance sheet.

Stock Valuation Methods


If you add a new stock record from starting Exch, it will pick up the default stock valuation method from System set-up,otherwise it picks it up from the last stock record edited. Changing the stock valuation method in System set-up will convert ALL stock records which had the Original stock valuation method to the new stock valuation method. It will not affect any stock records with

a different stock valuation method.

Stock Valuation from Live to EOP


Changing Stock Valuation from Live Method to End of Period Method. 1 Carry out stock check, post the Adjustments Day book and Nominal transfer that it produces. Print stock valuation report and agree stock value. 2. Create new Nominal Codes in Profit and Loss for Opening Stock and Closing Stock. 3. Change the description of Cost of Sales Nominal Codes to Purchases. 4. Enter a Nominal Transfer to move the value of Balance sheet Stock to Opening Stock 5. Change Live Stock/Cos Valuation in System Setup to NO 6. Make sure all stock records have the correct nominal code for Closing Stock 7. A new item Value Stock will appear on the Procedures Menu (stock menu in Excchequer), use this function to produce a Nominal transfer that will put the stock figure back into the balance sheet. Item 7 should be performed at the end of each period.
Stream error Printing forms, reports in Enterprise This could be lack of free disk space, disk space may be so low that there is not enough free memory to write to the temporary file

System Management
.SWP Files If .SWP files appear in Dir of Exch these should be deleted. .SWP or swap files can be formed if the system crashes, particularly when posting. They take up space and slow down backups. Return to DOS, cd Exch, dir *.swp, then del *.swp. .PRE Files Also, if everyone is out of Exchequer, pre files could indicate a crash. Check no one is in Exchequer, and look at the date of the pre files, then delete these as well. Installing Word Processor Q: Customer has not got word processor installed (Microstar) but I need to edit their forms. A: To add MS to their exchequer take a backup from any working exchequer with same directory name (i.e. c:\exch). Backup c:\exch\ms\*.* a: /s Then restore as normal on their machine: restore a: c:\ /s. If two systems on the same computer xcopy MS: xcopy \exch\ms\*.* \exch2\ms\ /s.

Tecnotes Release History


March 2007 Module Database List updated to include Scheduler, Importer and Nominal View databases

February 2006 New Customer Specific Special Functions 114 December 2005 Database Lists updated to include Module & Plug-In Databases September 2005 Updated Databases to include Return Line Reasons February 2005 New Special Function 109 and 110 New Customer Specific Special Function 108 September 2004 New Customer Specific Special Functions 107 August 2004 New Customer Specific Special Functions 106 July 2004 New Customer Specific Special Functions 103 and 105 New Special Function 104 System Password Options June 2004 New Customer Specific Special Function 102 May 2004 New Customer Specific Special Functions 100 and101 March 2004 New Customer Specific Special Functions October 2003 Updated notes for Error 94 May 2003 New Special Functions Added Setup for Exchequer Payroll September 2002 v5.xx Security Errors Updated Status 94 Re visited August2002 Microsoft QoS can Cause Error 2 on Win2000 & XP Index added to Document.dat to improve O/S Trans Searches - See Special Function 89 February 2002 Using Zeta Fax With Enterprise December 2001 New Command MCM line switch for v5.00 Windows XP Search stops working November 2001 Error Automating Word Outlook XP Asks me confirm Exch Email New Special Functions 78-88 Pervasive and Clustered Servers Running Enterprise and TAS Books Windows 2000 non Client-Server

Windows 2000 Lost Mapping April 2001 Command Line Switches Low Resources (re visited) Un Posting Stock February 2001 SF6 now prompts for sort Docs by Date or Folio December 2000 Error 88 Running the Enterprise FAX client or sender Pervasive.SQL 2000 and Windows 2000 Common instances of an application error October 2000 Error 4 running Exchequer (DOS) under Windows ME Updated Procedure for un-posting Multi-Currency August 2000 SF76-77 added. Includes set cust& Supp to Send reader with next email April 2000 Errors while Upgrading v4.30c and above. SF68-74 added (mostly client specific.) SF4 enhanced When I run Enterprise client server on a Novell server I get error 3103 Febuary 2000 Error list Updated Suggested Email Layout New sections added since January 1999 Special Function 67 Interpreting MKDE-1180 and MKDE-2039 System Errors ODC Error: SQL STATE = S0002 Error 'Cannot A Pervasive.SQL 7 License to a Pervasive.SQL 7 Server' User Count Administrator shows 0 users Converting 7x files back to 6x format WARNING: Data loss possible with Windows NT 4.0 SP6 and old Inoculan drivers Error "Cannot Load MSVCP60.DLL" when entering PCC Special Function 65 Special Function 66 Real-Time Data Compression and Data Compression File Flag Btrbox95 and DOS Applications Error when disconnecting first client in client list using DTI Workgroup Engine Runs at Default Settings only on NT with Non-Admin User GPF in MIF by Protected Mode DOS Program throughBTRBOX95 Cache memory allocation out of available memory Service Pack 4 and Win9x Connectivity Issues New Error 94 on Novell 4 Memory Leak in ODBC Error 5 on CS HP Jet Admin will cause Access Violation Correcting VAT Updating on Citrix Server Special Function 64 Special Function 63 Special Function 62 Special Function 61 Special Function 60 Server Specific Error 4083 on a Windows NT Server File Handles on NT Server

Hanging on NT with Pervasive SQL Scalable SQL Engine Messages Problems unloading Pervasive under Netware(4.x and 5.x) SQL setup items missing Mismatched ODBC Components GPF in Patch16 with Pervasive.SQL SP3 Using TCP/IP without DNS Status Code 22 Wnsock Error 10049 Printing Euro Equivalent figures in DOS DDF598 Failure Status 94 Status 95 on Token Ring Schedule of Stock Take Manuals in RTF Format Euro Symbol Special Functions (Additions) Special Function 54 Special Function 55 Special Function 56 Special Function 57 Special Function 58 Special Function 59 Special Function 60 Application Error First release of Tecnotes July 1997. Click Here to go to introduction.

Transactions
Settlement Discount offered after posting Q: How do I enter a settlement discount after an invoice has been posted? A: When the payment is received, enter the total amount of the invoice in the top of the receipt; in the bottom half enter the actual amount paid and code it to the bank, and the remainder to Settlement Discounts Given. Allocate the whole receipt to the invoice to clear the customer's account. (since v4.10, single currency systems will need to set up another nominal account for discounts, as they can no longer manually post to the default account). e.g. Invoice originally for 100. Posted. Settlement discount offered later of 5, therefore total due 95. Cheque received for 95. Add sales receipt Code 95 to bank a/c. Q: Although lines have been deleted from a payment/receipt, system shows amount required and will not allow exit. A: Enter a line with the amount required to bring the "amount required" back to zero. Then F9 and exit. Then edit the transaction, and with cursor in top part of document on any field except date, press "Alt + Z". This will zero any values still held in the bottom of the transaction. Q: One cheque received which pays two separate accounts. How do I show this? A: Enter two separate receipts, one for each customer, but enter the same cheque number on each receipt - this will clear each account and facilitate bank reconciliation NB also use paying-slip ref. Q: Is it possible to when converting a quote to an invoice to reverse it once converted? A: No - once converted to an invoice it has all invoice properties, therefore is an accounting document

and the number cannot be erased. Q: User stuck in a Receipt/Payment. A: If in the customer/supplier ledger card, allocate/unallocate as necessary to be able to return to receipt/payment. Then try deleting anything in "pay to/from" line. If all else fails go to top part of receipt/payment, place cursor on Cust Code and press "alt + z" - this will clear all amounts. Either save the document and then edit it, or if you feel it may be corrupted, post it with zero balances.

Transferring Data Files


Data files are transferable between Exchequers of the same version ( e.g. V3.02 - V3.02) The additional modules do not affect this. ( e.g. 3.02 Stock - 3.02 Spop) If you copy files from one Exchequer to another of same type, check folio numbers (including Stock Folio) and nominal control codes are also copied across.

But you cannot transfer multi-currency data files to a single currency version of Exchequer and vise versa.
(The only exception to this is nominal data and you could possibly use the import/export module to move transactions or records between different versions with careful use of the Multi Currency switch).

Unknown Form When printing Statements via the reports menu in Enterprise, the following error message may occur; The following error has occurred trying to print - 'Unknown Form -' This is because a default form has not been set-up in the Form Designer / Options / System Setup - Form Definition sets. Hint: Different default sets can be set-up for each customer.

So If this only happens for certain customers, check the customer record to see which set is applicable.

Unposting (General)
This Process can take a considerable amount of time! Always do a back-up before unposting, and make sure everyone else is out of Exchequer. If you are running in client server then you are already running as fast as you can so ignore the instruction on accelerated mode. To run in accelerator mode you need to do the following.use Rexacc6.bat which is detailed below @Echo off cls ECHO ************* ECHO * WARNING * ECHO ************* ECHO. ECHO ***** Ready to run EXCHEQUER in Accelerated mode *****

ECHO. ECHO This mode * MUST * only be used 'stand alone' ECHO With no other users in the Exchequer programs. ECHO. ECHO If the Workstation (PC) crashes during this opperation ECHO it may be necessary to Re-Build data or restore a back-up ECHO. ECHO Contact Exchequer Helpline for further help.. ECHO. ECHO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ECHO Press 'Ctrl + C' to ABORT or ...... ECHO PAUSE ECHO bstop CLS REN BTI.CFG bti.usr COPY btiacc6.cfg BTI.CFG btrieve excheqr /AC: Log on using the SYSTEM password. Select either total or partial unpost from the posting menu. Enter the last period that you do not want unposted. e.g. enter period 6 then from the first day of period 7 will return to the daybook. Answer no to any questions over VAT unless you are unposting to correct a problem with VAT. See Correcting VAT bstop del BTI.CFG ren bti.usr BTI.CFG If it crashes you should use BTIFIX.bat to restore the BTI.cfg. @ECHO off CLS ECHO. ECHO Report any error message !!! ECHO. ECHO. COPY bti.usr BTI.CFG If you do not have a copy of these batch files the basis is to take a copy of the BTI.CFG file to BTI.USR Edit the options line to say options=/L:20 /F:50 /H:60 /T:0:NUL /U:1 /W: /I: /B:1 /S:1 /M:1024 /G:500:5000 Then continue by runing Btrieve and Exchqr /AC as above not forgetting to copy BTI.USR back to BTI.CFG on completion. See Stock Unpost and Multi Currency Unpost

Unposting Multi Currency


Current Procedure for Unposting Multi-Currency - Updated 17/10/2000 - Company Rate --- AND --- Daily Rate. If an unpost is required on a multi-currency system using the company rate, it is important to follow the steps outlined below.

1. After the unpost several automatic nominal transfers will reappear on the nominal Daybook for any revaluations which have taken place. 2. As the revaluations are incremental they will need to be reposted with the exception of any adjustments affecting creditors and debtors. 3. Delete all adjustments lines affecting the debtor and creditor control accounts together with their corresponding double entry adjustment. 4. Re post.

Unposting Stock
Current procedure for unposting with Stock module; After unposting all the stock adjustments will be bought back onto the issues and adjustments daybook. The nominal transfers have already been created once, therefore; 1. Put a suspend at the top of the issues and adjustments daybook. 2. Re-post the nominal daybook. 3. Post issues and adjustments daybook which will create new nominal transfers. 4. Edit and zero the nominals (Alt-Z in the period field is a quick way)

v4.31
From V4.31 onwards Stock ADJ document are flagged when originally posted therefore they do not (should not) create another NOM transaction when re posting. From this version, follow the procedure outlined above, verifying that no NOM transactions are created by step 2. Any ADJs posted befor the upgrade to v4.31 will produce "blank" NOMs at this point.
Updating Enterprise on a Citrix Server Ensure you have a good backup. Login to Citrix and open a DOS prompt (File\run command) Type "Change user install" return Open file manager and run the set-up on the Enterprise CD, choose upgrade existing Enterprise, follow the prompts When the upgrade is complete, return to the DOS box and type "change user execute" See Citrix

Upgrading
Upgrading Exchequer can be a simple one disk upgrade, which replaces the executable and possibly some of the system files, or it can involve a data conversion. You need to run conversions first, and these need to be run in order ( e.g. 2.25 - 3.xx then 3.xx -4.xx) before running the final upgrade disk. The only conversion disk that has changed is 3.xx to 4.xx. Older versions did not include MLOCKSTK.DAT. If this is the case you will need a 4.xx - 4.10 conversion (check the stock sub directory

before upgrading). Conversions often alter some or all of the data files, and make them longer, or add new data files, so that new fields can be used by the executable programs.. If you have modules like Report Writer, you will need to upgrade these modules as well, after converting. (this is normally a separate upgrade disk) Make sure compatible versions of additional modules are running with the upgraded exchequer. you can add additional Modules when upgrading. NOTE : You cannot upgrade from a single currency version to a multi currency version and vice versa as the data files are not compatible. (If you need to do this, refer to Exchequer Software for the correct procedure). Also see release codes, upgrading from v4.10 - v4.20 and v3.00 - v4.00 Symptom: Upgrade Fails If you are running a one disk upgrade over a Novell network, check the attributes in the Exchequer directory. (read only files) SBSFLAG ATTRIB -R *.* or -R -A -S -H remember RASH! Other causes: Check upgrade didn't fail at SBSFLAG. More than 1 disk, restore backup and try again checking some of the following :If Novell Network, check logged on as system supervisor Check upgrade running in correct directory.(Shell out of Exchequer 'Utilities DOS' to find path). Check that V6.15 Btrieve is loading if convert is 3 - 4 by typing Bstop followed by Btrieve and check the version. Q Anything else that might have stopped upgrade, what if started with corrupt data files. A. If you suspect starting with corrupt data - Restore the backup & rebuild ALL files and try again. When restoring ( and this is a tricky one) it is possible that some backup/restore software has a switch to prevent copying of read only files, so check the options in the backup software. Report Writer Conversions Converting files for first use in Enterprise from Exchequer basically sets the font on the report header window and sets all the column widths on the report fields. If it was not converted properly you may have a weird font and the column widths would probably be 0. You can't see a lot when its zero millimeters wide, so correct these settings and enter through the report fields. If you suspect corruption in the Reports data file you could try cleaning the Reports.dat with BUTIL. Upgrading from v4.10 to v4.20 It is important to note that the conversion program from v4.10 - 4.20 looks at the information held by the multi-company manager, in Company.dat and converts all of the companies detailed there. Therefore, if you copy Enterprise from one directory into a test directory to test the upgrade, remember to edit the details held by the multi-company manager. If you want to run the conversion on one company only, you could disable the multi-company manager before running the conversion. (Which is fine so long as you keep track of which companies have been upgraded, and don't try to run a company until it has been upgraded.) There is no change in upgrade procedures to Exchequer DOS.

Upgrading v3.00 to v4.00


Btrieve v6.15 Upgrade
This version of Exchequer contains version 6.15 of the Btrieve database engine. In the majority of cases this version should result in much improved performance, especially during intensive routines such as posting. Several changes are needed inside 'REX.BAT' to make Exchequer work with the new Btrieve. For this reason, the upgrade disk will overwrite your current REX.BAT. Should you have any additional commands within your current REX.BAT, we advise you to take a copy of REX.BAT prior to the upgrade and apply the changes to the new REX.BAT. This also applies to any system which calls Exchequer directly from its own menus. It is possible for some configurations to conflict with Btrieve v6.15. The following list describes several common problems with possible solutions. Troubleshooting Q A When I run Exchequer I get the message: 'Not enough memory to load Btrieve'. Btrieve requires a minimum of 1Mb of free extended memory. The smallest machine with which Btrieve v6.15 will work is a 386 with 4Mb of memory. When I run Exchequer I get either an error 203 or the message 'Insufficient memory'. The new Exchequer requires more conventional memory to run than previous versions. You must ensure that you have a minimum of 550K conventional memory available. When I run Exchequer I get the message 'The transaction control file cannot be created'. Either you are attempting to run 2 copes of exchequer on the same machine, which Btrieve will not allow by default, or the path specified within the BTICFG file is not valid. Edit the file BTI/CFG using a conventional text editor. Check the line marked 'trnfile' is either blank or set to a valid path. If you do want to run multiple copies of Exchequer on the same computer, you must ensure that each copy of Btrieve points to a unique 'trnfile path. Q A Q A When I run Exchequer I get an error 200 reported. This problem was noted on faster Pentium P2 machines, and was fixed in V4.21 onwards of Exchequer. When I run Exchequer I get an error 88 reported. This error means 2 workstations attempted to use Exchequer with different versions of Btrieve. Exit all workstations and check which version of Btrieve each workstation is

Q A Q A

using, making sure they all use the same one. Q A When I run Exchequer I get an error 81. This error indicates 'SHARE.EXE is not running. You will need to amend your 'AUTOEXEC.BAT' batch file to load 'SHARE.EXE' each time your computer is restarted. Use the command 'SHARE.EXE./L:150' If all else fails : Should you encounter serious problems with the new Btrieve, and you are not running Exchequer on any other workstation, you can revert back to using the old Btrieve v5.10 by running 'RES510.BAT' instead of running REX.BAT. However, you cannot use the old Btrieve in conjunction with Enterprise.
User Count Administrator shows 0 users

Title: User Count Administrator Shows 0 Users And Displays Error - "The license key has already been used." Issue: The User Count Administrator shows 0 users, and when the User Count administrator is used to add the license, it displays the following error message - "The license key has already been used". Furthermore, running ntucinit or nwucinit -patch runs without error but doesn't increase the user count. Solution: On NetWare: 1. Issue a slqstop and a bstop from the server's console. 2. Rename nwucmgr.sys in sys:\system directory. 3. From the console, enter 'Load nwucinit -patch' (without the quotes) to recreate nwucmgr.sys. 4. Run the User Count Administrator from the Pervasive program group at a workstation. It will show Btrieve 6.30 and Scalable SQL 4.0 with 0 users. 5. From there add the license from the floppy disk. It will now show Pervasive Software 7.0 Alternately, from the NetWare console type 'Load Nwucutil -da:' (without the quotes) and use the server's floppy drive. 6. Restart Pervasive with a Bstart and/or Sqlstart. On Windows NT: 1. Stop the Btrieve and SQL services from Control Panel - Services. 2. Rename ntucmgr.sys in Winnt\system32. 3. Run ntucinit -patch from a DOS window command prompt to recreate ntucmgr.sys. 4. Run the User Count Administrator from the Pervasive program group. It will show Btrieve 6.30 and Scalable SQL 4.0 with 0 users. 5. From there add the license from the floppy disk. It will now show Pervasive Software 7.0. 6. Start the Btrieve and SQL services.
Using TCP/IP without DNS Issue: Using TCP/IP communication in Pervasive.SQL 7 on a NetWare server without a DNS Solution: Set up a HOSTS file, without any extension, on your workstation with an entry indicating the TCP/IP address and the server name. For example, the entry may look like: 100.100.100.1 MYSERVER

* *

On Windows 95 or Windows 98 workstations, the HOSTS file should be in the C:\WINDOWS directory. On Windows NT workstations, the HOSTS file should be in the C:\WINNT\SYSTEM32\DRIVERS\ETC directory.

Use the PING utility to PING MYSERVER and ensure the HOSTS file connects the server name to the correct TCP/IP address. If the set up accesses the server using the TCP/IP address specified in the HOSTS file, then TCP/IP should be able to access Pervasive.SQL on the server.

VAT Problems
VAT differences Q: The VAT calculated by Exchequer does not agree with my supplier's calculations. A: There are 4 methods of calculating VAT approved by Customs & Excise. Exchequer calculates VAT per item, rounds up the amount and multiplies it by the quantity. (Line method B) This method was chosen to enable the system to deal with different VAT rates on each line, and to enable settlement discounts to be calculated. Exchequer conforms to the strict requirements of the unit method of calculating VAT, and conforms to C&E regulations. With Sales invoices you should charge the VAT that Exchequer calculates. If sending out manual quotes check VAT on Exchequer first, or quote ex VAT. For Purchase invoices enter the amounts from the supplier's invoice. If Exchequer's VAT does not agree with the suppliers, press F9 to reveal the blue VAT/discount screen, Say yes to change VAT manually or press the upwards arrow to enter the VAT box. Enter the correct (supplier's) VAT charge. else if the body of the invoice is edited before being posted, the VAT will recalculate and you must change the amount in the blue VAT box again. Cash Accounting - VAT Cash accounting is dependent on allocation of payments - payments can be entered after the end of the VAT period but must not be allocated before VAT return done. Therefore suggest no payments/receipts allocated in the month after the VAT period has ended until all payments/receipts for the VAT period have been entered and allocated and the VAT period closed. Once VAT period closed all payments entered in next month must be manually allocated. VAT Set Up F5 Where Exch still has old rate/wages rate, reset as: 3:Acquisitions 4:Dispatches in case company starts/is trading with EC. A company must spend/turnover 140,000 with a customer/supplier before EC VAT regulations apply. VAT- INTRASTAT If Intrastat fields are enabled, in VAT set-up you have codes 3/A and 4/D, and in the transaction lines you can select 3 or A, or 4 or D. 3 & A, 4 & D, are the same. but you need to use A&D for EEC cust/Supp for VAT report to be ok, and then not use 3 or 4. From 1st January 1999 the way HMCE will accept intrastat reports will change. Due to de-regulation they will require less detail, but the format in which the information will change. We are aware of these changes and details concerning modifications to Exchequer and Enterprise will be found in the Readme document and Entread help file in future releases . VAT correction on unpost.

Vat 4.02b
There was a problem posting VAT, when the VAT period ended in period 2 (February). The first thing to do would be to upgrade to the latest version. Upgrading will not resolve any historical problems, but will stop future recurrences. To correct the historical data, partially unpost the records, to a period before this VAT period. Answer 'Yes' to the first VAT question, Reset VAT. Then repost See unposting or Vat correction
WARNING: Data loss possible with Windows NT 4.0 SP6 and old Inoculan drivers Installing NT 4.0 Service Pack 6 on a system running Computer Associates Inoculan can cause data files to be reset or deleted. Please read the information, provided by Microsoft, at the following location: http://support.microsoft.com/support/kb/articles/q244/6/52.asp The CE Partner List Server is a service of Pervasive Software <http://www.pervasive.com> Obtain a list of commands for this list: mailto:ce.partner@pervasive.com?subject=help

CLIENT SERVER (REQUESTER MODE)


One copy of Btrieve running on the server Therefore each workstation requests the information from the server, the file management and locking is all done by one copy of btrieve running on the server.

NON - CLIENT SERVER (LOCAL ENGINE)


Multiple copies of Btrieve working together All the workstations have a copy of Btrieve. Therefore, heavy network use, or larger amounts of users (over 12 normally) could slow things down. Example explanation of Client server on a non-indexed search (Eg Searching customer list) Client Server - You send a chap to the library, he goes looks at all the books until he finds the one you want, then he brings it back to you. Non-Client Server - You send the chap to the library, he looks at the title of a book, comes back tells you, if it is not the correct one, he goes back to the library and looks at the title of the next book, comes back etc until he finds the one you want, then retrieves it.
Workgroup Engine Runs at Default Settings only on NT with Non-Admin User Title: Workgroup Engine and Non-Admin User Issue: After changing the engine settings on a Windows NT 4.0 machine with the Configuration utility, restarting, and logging into the same machine as a non-administrative user, the engine still loads with the default settings. Solution: Include user as an Administrator of that machine to resolve the issue. This problem has been submitted as defect number 19398.

Workstation Installation
Enterprise Workstation Installation. If after going in from a fresh boot, various DLL files are already in use, such as OLECLI.DLL, OLE2.DLL,

STORAGE.DLL and COMPOBJ.DLL You should be safe to Ignore these files. From version 4.10 - 4.20 the installation program may have given problems with regards to DLLs. In mid-96 Microsoft split their MSVCRT40.DLL into three separate DLL's: MSVCRT40.DLL, MSVCRT.DLL and MSVCIRT.DLL. Beta releases of Enterprise had the new MSVCRT40.DLL However, because we didn't know about the splitting of the original DLL we didn't include the new DLL's in the installation program. This has been rectified in later releases. > > Old MSVCRT40.DLL - 319KB New MSVCRT40.DLL - 64KB

Year 2000
Exchequer has been year 2000 compliant since the release of version 4 in 1996. Which coincided with the release of Enterprise. Q: Will Exchequer work with hardware that has a bios that is not compliant.??? A: Providing the PC's own clock will support year 2000 then so will Exchequer. If his BIOS does not then no software running on it will either, as the program relies on the clock to get the date! We am led to believe that in some cases if the bios is not compatible then the machine will probably not even boot up in which case the question becomes academic! There are, I believe a number of utilities available which either intercept the BIOS or continually monitor the RTC, correcting the error. However we at Exchequer have not evaluated such software. It is possible that this type of software fix would behave in 'a virus like manor' and be reported as such by anti virus software. Either way, most PCs use a flash BIOS and would be upgradeable by contacting the motherboard manufacturer. Exchequer will support a date range from 1950 to 2049.

Zeroing a Transaction
If the transaction is posted, do a partial unpost to get it back on the daybook ( see Unposting) Go in and zero all of the lines, if it is a PPY, zero the header as well. If it will not zero, enter through the header to the period field and hold down the Alt Key, then press zero. This should force the transaction to zero, and then you can store it. If you don;t want it to clutter up the clients ledger you could set up a BIN customer, and Bin02 as a supplier, then change the account code to BIN or BIN02 NB If you have problems editing the transaction, make sure it is unallocated, and if it won't unallocate because it has been revalued you will need to follow the procedure below: Make sure everyone is out of the exchequer and go in under System Password. Edit the company/daily rate back to what it was at the time of entering the transaction. Unallocate the transaction. Change company/daily rate back again.

Missing Configuration Utility after Pervasive.SQL 2000 Install

Issue: During a Pervasive.SQL 2000 install, DCOM98 can have an error accessing some DLLs. This can cause the Configuration Utility to not display inside the Pervasive Control Center after a seemingly successful installation. Solution: Register the program with pvconfig.dll. How To: 1) Choose Start-> Programs -> Pervasive -> Pervasive Control Center 2) Click the + symbol. 3) Click View -> Options 4) Click Tools. 5) Click Add. 6) Select pvconfig.dll. 7) Click open. It should automatically select the "on" option for the Configuration Utility. 8) Click Apply and Ok. The pvconfig.dll should appear (3rd) in the list above SQL Data Manager.

v4.20
We have now produced a dual currency version of Exchequer and Enterprise called Euro. Basically this is a cut down version of multi-currency and only allows two currencies to be entered. All other multi-currency features are present in the Euro version, such as revaluations and translate, which allows you to effectively report in dual base currencies. This is likely to be a requirement when the single currency is introduced in 1999. As new customers set systems up, we suggest that their base currency be EURO, to aid reporting.(Existing customers that have multi-currency systems will need to add the Euro in as a currency and will be able to benefit from the 'translate' functions.') Module release codes It has become evident that greater control is required over additional modules purchased after the initial system. To this end a module deployment system has been developed which allows individual modules to be enabled separately from the main security release. In addition, a module may be released for 30 days or fully released. At present, Full Multi-Currency (as opposed to the new Euro), Job Costing, Report Writer and DLL Toolkit have been implemented. This will be extended in the short term to include the forthcoming Telesales and Goods Returns modules. Stock Control and Order Processing are longer-term projects and will not be implemented into the release code system until the end of 1998. Each module is numbered, and the corresponding module number must be given together with the security code as each security code is bound to the module it is releasing. This means a security code for module 1 cannot be used to release a different numbered module. The deployment screen is accessed via system setup, and is only available with the daily password. The release codes can be printed out for ease of faxing. Each Enterprise will be shipped with all additional modules disabled initially, and will require releasing immediately after installation. In the case of Multi Currency, this will mean every v4.20 Multi Currency System will initially run as an Enterprise Euro until the Multi Currency module is released. The Module deployment system is also available within v4.20 of Exchequer. It should be noted that the DLL Toolkit will also require releasing as of v4.20 to ensure that genuine licensed versions are in use. Also see release of v4.20b.

Special Function 48/49 Achieves the same as "Check account balance" + "Unallocate transactions" but for all customer/supplier accounts. Except that all Financial transactions ONLY are effected. Special Function 68 Converts all telephone/ fax and Mobile phone numbers in accordance to the BT changes effective from 4/2000 This function should only be run once. Special Function 71 When run this function asks for a stock location. It then enters this location into any transaction lines that have a blank location record. Use when "Move" to location stock has been run twice and the total stock levels in all locations does not equal the consolidated stock level. Check all stock levels will need to be performed after this function has been run. Special Function 69 Fix for transactions imported incorrect transaction total Cost. Recalculates the correct total cost for all sales transactions so that the visual GP looks correct. This function does not update customer sales profitability history so "Check all Accounts" will need to be run, afterwards. Special Function 73 Fixes corrupt imported NOM's and ADJ's which did not create proper job costing actuals. After this is run Reset Job actuals will also need to be run Special Function 74 Deletes hidden BOM lines which still remain owing to users editing either the SDN or SIN of an ordered BOM line with Deduct Component Stk if no BOM switch on. This SF assumes that all the BOMs in history belong there SF12 must be run prior to running this function

When I run Enterprise client server on a Novell server I get error 3103 This error can be caused by mapping a drive letter to a Novell server using a NDS context rather than a UNC. The mapped drive to Enterprise should be mapped with a UNC, A typical example of a UNC drive mapping would be MAP X:= \\server_01\sys\apps\exch: When using Novell 4.x and 5.x it is important to map drives using a login script rather than an windows explorer.

Error Messages during Upgrade v4.30c and above


v4.30c and above
Before running the conversion to v4.31 rebuild EXCHSQQ.DAT first See Changing File Versions {..} Denotes the sections within the Set-up Program {Company 1000 1001 1002 1003 1004 1005 1006 ------------1100..1199 1200..1299 1300..1399 1500..1599 Initialisation, ESN and Release Codes} Unknown Exception Incorrect security parameter Btrieve Not Running Missing Licence File Failed to read Licence File Error Writing Licence File Error Reading Licence File Btrieve Error Opening Exchqss.dat Btrieve Error Opening ExchqChk.Dat Btrieve Error locking ModRR Btrieve Error updating ModRR

1600..1699 1700..1799 1800..1899 1900..1999 2000..2099 2100..2199 2200..2299 2300..2399 2400..2499 2500..2599 2600..2699 2700..2799 10000+

Btrieve Error getting ModR Record Position Btrieve Error getting SysR Record Position Btrieve Error locking SysR Btrieve Error reading SysR Btrieve Error reading ModR Btrieve Error updating SysR Btrieve Error rereading ModRR Btrieve Error reading EDI2R Btrieve Error locking EDI2R Btrieve Error getting EDI2R Record Position Btrieve Error rereading EDI2R Btrieve Error updating ModRR Error in SCD_SecWarnWizard

Where the Btrieve error is the last two digits {SCD_SecWarnWizard - Display the Single-CD Security Warning Wizard} Mode: 1=SCuD Install, 2=SCud Upgrade, 3=MCM, 4=Ent SetRelCode: 0=Nothing, 1=Release Code Set 11000 11001 Unknown Error Unknown Exception

{Replicating the licencing details around the various companies in the MCM } 1000 1001 1002 1003 1004 1005 1100..1199 1200..1299 1300..1399 1400..1499 1500..1599 1600..1699 Unknown Error Unknown Exception Incorrect security parameter Btrieve Not Running Unknown Error reading SysR Unknown Error reading ModR Error Opening Exchqss.dat Error opening Company.Dat Error Opening SysF in Company Error Opening PwrdF in Company Error Locking SysR in company Error Locking ModR in company

{ v4.31 - Single-CD: Replicates any files necessary to all companies } function SCD_ReplicateFiles(var DLLParams: ParamRec): LongBool; // // 1000 - Unknown Error // 1001 - Unknown Exception // 1002 - Invalid Main Directory // 10000 - Unknown Error // 10001 - Unknown Exception // 10100-10199 - Btrieve Error opening Company.Dat * 10120 Btrieve not Running. Check the following Registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Btrieve Technologies\Microkernel Engine\Version 6.15\Microkernel Interface\Settings Valid values are 0 and 1. This should be set to 0 for all Workstations and 1 on the Server. --

Duplicated Debtor/Creditor Posting Control Lines


Q. When I look at the GL drilldown for Debtors and Creditors I can see 2 identical Control lines.

A With normal transaction lines there is one line which we express in its own currency or base. With Control codes we generate one for the currency of the transaction and one for base. The reason for this is the fact that the control codes are not related to a single transaction generally, but a summation of many and a single transaction line equivalent could introduce rounding errors.
Special Function 76/77 Ticks the "Send Reader with next Email" box on Customer (SF76) & Supplier (SF77) Records. This box is automatically unticked on the next Email is sent to each customer/Supplier) Error 51

The Owner Name is invalid.


You are attempting to open Version 4.31 datafiles with an Exchequer/Enterprise system or component that is earlier than v4.31

Error 217 Can be caused when trying to run Enterprise v4.31 and above on the original unpatched version of Win95. Apply the Serveice pack for this OS or upgrade to a later version. Often re-installing MS Office cures this problem. Suspected cause is another application has installed an earlier version of a Windows DLL.

BOM Cost Update


Problem:- The cost of by Bills Of Materials does not equal the total of the components. Solution. In Exchequer (DOS) And Enterprise there is "Update build costings" in the on screen stock list. This is a "Quick Check" in that it identifies stock record cost prices that have changed and updates all BOM costs that contain them. It only updates the BOM cost by the difference between the component 's new cost and the value stored in the BOM. If for what ever reason the cost stored in the BOM is wrong, the total will still be wrong. This procedure corrects the situation in the vast majority of cases. In the event that this does not correct all the cost prices there is a more rigorous check inside Exchequer(DOS) under utilities/Data recovery/ BOM cost Prices. This check updates all BOM costs regardless. This routine will take longer that the one above because it is looking at ALL BOMs and not just those that the system is changed. Neither of the above routines should be needed where the valuation method of the BOM is FIFO/ LIFO or Serial/Batch.

Error 088 When trying to run the Enterprise Fax client / Fax Server I get a Btrieve error 88, This is usually found on multi user Enterprise installs and situations where no Workstation set-up has been run on the PC in question. for example, running the Fax Sender on the File Server. The recommended approach would be to ensure that the Pervasive Engine is set-up as per the instructions in ENTREAD.HLP. Either Do not run the Fax Sender on the Server(prefered) or run a Workstation install. If the problem is occurring on a Workstation, perform a Workstation install on that PC.

Adding SRC/PPY does not correctly show all O/S Transactions


Check the Btrieve configuration and ensure that they "extended buffer operation size" is set to 16. If version is pre v4.30c and the above does not cure, upgrading to the latest version, should.

Pervasive.SQL 2000 and Windows 2000


If you are running Pervasive.SQL 2000 on Microsoft Windows 2000, please be aware of the following issue: Issue: Microsoft has changed its implementation of "user" and "guest" accounts, and the rights of those users on all Windows 2000 platforms. Thus, when a user is logged in as a "user" or "guest" and attempts to run applications on a Pervasive.SQL 2000 Server, Pervasive.SQL 2000 does not function correctly. NOTE: The changes DO NOT impact Pervasive.SQL 2000 applications on a local machine. Solution: To run applications on Windows 2000 accessing a Pervasive.SQL 2000 Server, ensure that the user account has at least "Power user" privileges. NOTE: Pervasive Software is investigating other options to address this issue. Please check our Knowledge Base at regular intervals for updated information. The Microsoft web site has the following description for Power Users: Power Users Members of the Power Users group have more permissions than members of the Users group and fewer than members of the Administrators group. Power Users can perform any operating system task except tasks reserved for the Administrators group. The default Windows 2000 security settings for Power Users are very similar to the default security settings for Users in Windows NT 4.0. Any program that a User can run in Windows NT 4.0, a Power User can run in Windows 2000. Power Users can: Run legacy applications in addition to Windows 2000 certified applications. Install programs that do not modify operating system files or install system services. Customize system-wide resources including Printers, Date/Time, Power Options, and other Control Panel resources. Create and manage local user accounts and groups. Stop and start system services which are not started by default. Power Users do not have permission to add themselves to the Administrators group. Power Users do not have access to the data of other users on an NTFS volume, unless those users grant them permission. Warning Running legacy programs on Windows 2000 often requires modify access to certain system settings. The same default permissions that allow Power Users to run legacy programs also make it possible for a Power User to gain additional privileges on the system, even complete administrative control. Therefore, it is important to deploy certified Windows 2000 programs in order

to achieve maximal security without sacrificing program functionality. Programs that are certified for Windows 2000 can run successfully under the secure configuration provided by the Users group. For more information, see Securing Windows 2000 Installations at the Microsoft Security Advisor Web site. Since Power Users can install or modify programs, running as a Power User when connected to the Internet could make the system vulnerable to Trojan horse programs and other security risks. For more information, see "Why you should not run your computer as an administrator" in Related Topics. NOTE: Windows 2000 Users cannot: Install programs that can be run by other Users to prevent Trojan horse programs. You can run certified Windows 2000 programs that have been installed or deployed by administrators. You cannot access other Users' private data or desktop settings. You cannot modify system-wide registry settings, operating system files, or program files. You have full control over all of your own data files (%userprofile%) and your own portion of the registry (HKEY_CURRENT_USER). You can shut down workstations, but not servers. You can create local groups, but can manage only the local groups that you created. 1998-1999

Duplicate lines in GL drill down


With normal transaction lines there is one line which we express in its own currency or base. With Control codes we generate one for the currency of the transaction and one for base. The reason for this is the fact that the control codes are not related to a single transaction generally, but a summation of many and a single transaction line equivalent could introduce rounding errors. Change the GL view from Currency 0 (consolidated) to the currency number of the transaction line/s that you see as dulplicates. If one of the lines disapears, then the above is what you are seeing. This is normal.

Installing the Fax client


When installing the Enterprise fax driver in v4.31 it looks for some files starting with apf and ending as either a .dll or a .drv. The installation automatically drops you into the correct folder, however if you do not have 'Show all files' set in Explorer you will not see any of the above files. The folder will appear blank. To get around this, open an explore window and go to view, options and select show all files. This varies slightly depending on the operating system you are running. You can then go back to the install, refresh the screen and the required file will be displayed.

Command Line Switches


Entrprse.exe and Enter1.exe accept the following command line switches. They must be typed in upper case, exactly as shown.

/NL:
Disables the bitmaps on the splash and login screens. Improves load speed for Citrix and Terminal Server connections.

We further suggest that you turn the background bitmap off in System Set up.

/MUDELAY2:
This may help, where the splash screen is displayed then disappears and you are left with Exch1 in the task bar but Enterprise fails to load. generally a problem with some Novell Clients See Entread for further details.

/MUNOCHECK:
This option stops Enterprise from attempting to reset the user count See Entread as above for further information.

/NOMC /NOMCM: /DIR:

(Pre Version 5.00) (v5.00 and above)

No Multi-Company Manager

No Multi-Company Manager

Form-- /DIR: {full Enterprise path} EG /DIR: x:\exch\entrprse\

/CMPDIR: xxx
Path of main company (only needed if running Enter1.Exe directly)

/CODIR: xxx
As /CMPDIR:

Use to pass the Data Path To EXCHWEQR.EXE and ENTER1.EXE ONLY use when you cannot use the MCM. or to Run DOS re-builds when you cannot run the rebuild through Exchequer (DOS).

/USE_JFIELDS:
Exposes all Transaction header Jobs costing fields in a system that does not have Job costing. Thus allowing additional User fields similar to the User defined fields. The field labels cannot be changed The user will not be able to write or maintain any Report Writer reports that use these fields. This will need to be done by the Reseller off site using a reseller copy of Enterprise that includes a Job Costing Release, then Exported and re imported by the client on site. Report Writer can use these fields if they exist in a report but is a user edits a report that uses them, the fields will appear blank. and not allow any modification to be made until a valid code is entered.

/NOCUSTOM
Disable ALL Customisation

/NOCOMCUSTOM
Disable COM Customisation only

If you find problems with the graph, or OLE links, this may be due to the installation not completing successfully. You can run ENTREG from inside the Enterprise directory to manually install the graph and OLE server.

COM Error While Printing


This applies to Enterprise v4.31 - v4.32.002

The following Error can occur if printing forms when a COM customisation plugin is executed.

In the above Example the COM Cumomisation CC/Dept Validation Plug in is installed. The User was Printing a range of Documents, then Added a New document and tabbed out of the CC field on a Transaction line. This will be addressed in Enterprise v5.00. There is no imtermediate fix. Our only advise until then would be to avoid the above scenario if possible.

Clustered Servers
PSQL 2000 SP3 offers very little in cluster support. You may install in the environment, but that's about it. Pervasive SQL 2000i will install on a cluster server, but will not operate with the fallback software, i.e. it cannot switch servers. SP4 may offer a little functionality when it is released later this year, but I don't think fallback will be there, just the ability to use virtual servers. PSQL 8, listed for next spring, has listed further support for clustering, but no details are listed at this time. Note If a cluster node fails, a Pervasive.SQL client does not automatically reconnect to the Pervasive.SQL engine on the surviving node. Your application must reconnect the client to the Pervasive.SQL database or you must restart the application. This applies even if Enable Auto Reconnect is turned on in the PCC. Pervasive.SQL does not maintain the transaction state when a cluster node fails. The transaction states does not transfer to a surviving node. Transactions are automatically rolled back to the state before the transaction began.

Running Enterprise and TAS Books


We have encountered problem with sites running Enterprise and Tas Books on the Same machine. Tas have provided us with the following registry entries that should address this issue. [HKEY_LOCAL_MACHINE\SOFTWARE\Btrieve Technologies\Microkernel Workstation Engine\Version 6.15\Settings] "Compression Buffer Size"=dword:00002000 For simplicity this is also provided in a file on the Exchequer Technotes CD \UTILS\TASREG\tasreg.txt Alternative solution Running a Workstation Installation from the TAS Setup will resolve this issue.

Windows 2000 non Client-Server


Because Non Client Server sites use the older Btrieve v6.15 local Workstation Engine there is a Registry permissions issue with Windows 2000. In this version of Windows all the default user privileges were effectively 'demoted' . As far as Enterprise is concerned this manifests itself ad a blank Multi Company Manager screen when a User only has Standard USER Privileges. The solution is to give users a power user login or:1) Move the log file for the v6.15 engine from the C:\WINNT to a new position.( a local folder with full access). 2) Change the "user group" access to the registry to allow full access. Regedt32 needs to be used so the permissions can be changed. This Issue does not effect a full P2000 Client - Server installation.

Windows 2000 Lost Mapping


From Microsoft

Drive Mapping May Time Out on a Windows 2000-Based Computer


The information in this article applies to: Microsoft Windows 2000 Professional Microsoft Windows 2000 Server

SYMPTOMS
When you perform drive mapping from a Windows 2000-based client computer to either a Microsoft Windows NT or Windows 2000 network share, the drive mapping may be disconnected after 15 minutes of inactivity and Windows Explorer may display a red "X" on the icon of the mapped drive. However, if you attempt to access or browse the mapped drive, it reconnects quickly.

CAUSE
This behavior can occur because both Windows NT Server version 4.0 and Windows 2000 Server can drop idle connections after a specified time-out period, which by default is 15 minutes, so that server resources are not wasted on unused sessions. The connection can be re-established very quickly at a later time, if required.

RESOLUTION
To resolve this behavior, use a command to change the default time-out period on the Windows NT Server 4.0 or Windows 2000 Server: At a command prompt, type: net config server /autodisconnect:30. The valid value range to configure this setting from a command line is from -1 through 65,535 minutes. To disable Autodisconnect, set it to -1.

NOTE: This step must not be confused with the remote access Autodisconnect parameter that is turned off if you set it to a value of zero (0). If you set Autodisconnect to zero (0), this setting is not turned off and after a few seconds of idle time very fast disconnections can occur. For additional information about increasing the default time-out period, click the article numbers below to view the articles in the Microsoft Knowledge Base: Q138365 How the Autodisconnect Works in Windows NT Q128167 Server Service Configuration and Tuning NOTE: The default time-out period cannot be changed in Microsoft Windows 95-based and Microsoft Windows 98-based clients that have shared resources.

Outlook XP Asks me confirm Exch Email


When Running Batch payments Out look asks me to confirm before it sends Each Transactiom. The following is an extract from a Microsoft support document.

The information in this article applies to: Microsoft Outlook 2002

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SUMMARY
Outlook 2002 includes a new security feature that blocks attachments considered unsafe. If you receive an e-mail message that contains one of the blocked file types, you may see the following warning message: Outlook blocked access to the following potentially unsafe attachments: [...] Although access to the attachment has been blocked, the attachment still exists in the message. This article summarizes what to do if you need to access the attachment.

MORE INFORMATION
This security feature provides an additional level of protection against malicious e-mail messages. Updates were available for earlier versions of Microsoft Outlook, but in Outlook 2002 this security feature is implemented by default.

Use one of the following recommended methods to obtain access to the attached file: Request that the sender post or save the attachment to a file share and send you the link to it. Request that the sender use a file compression utility that changes the file extension. For a list of third-party compression products, please see the following Microsoft Knowledge Base article:

Q291637 OL2002: Attachments Are Not Compressed by Outlook Request that the sender rename the file extension and send it to you. Once you receive the renamed attachment, you can rename the file with the original extension.

If the previously recommended methods do not meet your needs, you may use one of the following alternate methods: If you are in a Microsoft Exchange Server environment and your administrator has configured the Outlook Security settings, ask the administrator to modify the security settings for your mailbox. If you are not in an Exchange Server environment, modify the registry to customize the attachment security settings (see the How to "Customize Attachment Security Behavior" section of this article for details).

How to Customize Attachment Security Behavior


You can modify the attachment security behavior in Outlook 2002 if you are using Outlook in one of the following scenarios: Outlook is run outside of an Exchange Server environment. In an Exchange Server environment, the administrator has not configured the Outlook Security settings to disallow changes to the attachment security behavior.

In these scenarios, modify the attachment security behavior by making a modification to the registry. Use the following steps to modify the registry. WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the

Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD). 1. Exit Outlook 2002, if running. 2. Click the Windows Start button, and then click Run. 3. In the Open box, type regedit, and then click OK. 4. Check to see if the following key exists. If it does, skip to step 5. HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Securi ty If the key path does not exist, create the key path. To create the key path, navigate to and select the key: HKEY_CURRENT_USER\Software\Microsoft a.a. b.b. Click the Edit menu, click New, and then click Key. Type Office and press ENTER.

c.c.Click the Edit menu, click New, and then click Key. d.d. e.e. f.f. g.g. h.h. Type 10.0 and press ENTER. Click the Edit menu, click New, and then click Key. Type Outlook and press ENTER. Click the Edit menu, click New, and then click Key. Type Security and press ENTER.

5. Click the Edit menu, click New, and then click String Value. 6. Type the following name for the new value: 7. Level1Remove 8. Press ENTER. 9. Right-click the new string value name, and then click Modify. 10. Type the extension of the file type that you would like to access with Outlook 2002 as follows: 11. exe 12.To specify multiple file types, use the following format: 13. .exe;.com 14. When finished, click OK.

15. Exit the Registry Editor program. 16. Restart the computer. When you start Outlook 2002, the file types specified in the Windows Registry are accessible. NOTE: Microsoft recommends that only the necessary file types be enabled for access. If a particular file type is received rarely, it is recommended that Outlook 2002 be given temporary access to the file type in question and then reconfigured to the blocked state by undoing the changes made to the Windows Registry.

This can be caused by trying to add a link document to a transaction while another user is editing the Master Document.

Windows XP Search stops working


Applies Only to Sites with the Ebusiness Module. Enterprise versions from v4.31 to v4.32.00x Workstation Set-up Installs and registers a Microsoft COM object for Parsing XML files. This COM object Is now distributed as part of Windows XP. When a workstation is run, it overrides the XML object installed by the operating system. The Solution is to re register the original Components as follows. Run a DOS Box (cmd.exe) Type the following at the prompt. cd windows\system32 regsvr32 msxml.dll regsvr32 msxml2.dll regsvr32 msxml3.dll This has been addressed from Enterprise v5.00 onwards

Using Zeta Fax With Enterprise


Enterprise Setup
1. Go into Utilities, System Setup, General Settings, and click on the Fax/Email Tab 1. Set the fax Printer Driver to "Zetafax Printer" 2. Set the "Fax Using" to "Third Party Fax" 3. The Fax Interface path should be empty.

Forms Setup
2. You must first add three new formulas onto the form which will be the first page of your fax. If you are using a Fax Cover page, then these 3 fomulas will need to be on this form, otherwise you will have to add these 3 formulas onto each form that you wish to be able to fax. These three formulas are as follows :""%%[FAX:_" + DBF[FAXTONO] + "]" ""%%[NAME:_" + DBF[FAXTO] + "]" ""%%[ORGANISATION:_" + DBF[FAXTO] + "]"

Obviously you do not want these fields to actually be seen on the page (they must be put on the printable area of the page, or it will not work), so set the colour of the font to White, so they dont print out. Another important thing to Note, is that you must make these fields wide enough to fit all the information that will go into them. If the Fields are not wide enough, they will word-wrap onto the next line, and this will prevent them from working correctly. Our advise it to make them as wide as the page, if possible. Also Note, if you are putting these 3 fields on the form, rather than a cover sheet, you will need to make sure that they are only printed on the first page of the form. This is done by putting the following in the "Print If" condition: PAGENO = 1 This deals with all the necessary addressing fields. 1. To actually get Zetafax to send the document you must add a formula onto each form that you wish to fax. The formula is as follows :""%%[SEND]" You also need to make sure that this formula is the last thing printed in the print job, so do a "Bring to front" on it to make sure of this. As you only want to send the fax when all pages have been processed you need to make sure that this formula is only printed on the last page. This is done by entering the following into the "Print If" condition of the formula DBF[SYSPGBRK] = "NO" Again you dont want this formula to be seen, but it must be on the page, so colour the font as white, to make it invisible. Note: if you are using continuation forms, then the "Send" formula need to be put on the last form of the continuation set. 2. Repeat this process for all forms that you wish to send via fax. 1. When you go to print the forms that you have setup, you should find that there will be a fax tab available. Select this tab, and click on OK to send the documents to Zetafax. Zetafax should then send the documents for you in the normal way.

Barclays Business Master

Configuring BBM to opperate with Enterprise. This fix will only work with the standalone version as the server version uses the 'workgroup' engine and you get error 116. Where the different version of the engines are trying to access the DAT files. With the local version the 'workstation' engine needs to be started at the windows boot. Create a shortcut in the start-up group for w32dbsmgr.exe, which will be in the BBM folder. Add to the end of the shortcut target -btrv, this solves the initialisation error. This fix allows the user to switch between the 2 applications without error but we would not advise that they are both run together.

Errors in MCM / v5.00 Security.


// 0 OK // 1000 Unknown Error // 1001 Error Reading Enterprise Licence (Entrprse.Dat) // 1002 ESN in Enterprise.Dat not set // 1003 ESN in Company.Dat not set // 1004 ESN in Company.Dat and Entrprse.Dat don't match // 1005 ESN in Entrprse.Dat and ExchQss.Dat don't match // 2000- Btrieve Error opening SysF in main directory // 2999 Error reading System Setup Record containing ESN 32767 = Unable to Read or Lock the main system setup record in order to reduce the user count by 1.
Special Function 89 - v5.00 Exchequer index test, to support new allocation routines An improved index for finding outstanding transactions has been added to Enterprise v5.00 and becomes effective once document.dat is rebuilt. Special Function 89 reports on the status of the document.dat file index showing whether it requires rebuilding or not.

NOTE: In Exchequer (DOS) Rebuild Mopdule SF84 is :'Set Zero Co rate to daily rate on posted transaction lines' One off client specific fix, see Warning not at the top of the special functions Page. This function will pick up any posted transaction line with a zero exchange rate and attempt to use the lines daily rate to repair it. If then lines daily rate is also zero it will use the transaction's original exchange rates. A report is produced for all changes made. If any transactions have been revalued the report also indicates this.

Status 94 is occurring on client machines even though user has appropriate rights Status 94: "The application encountered a permission error" Problem Environment: Pervasive.SQL v7 Pervasive.SQL 2000 Microsoft Windows NT Microsoft Windows 9.x

Solution: Run regedit. Under HKEY_CURRENT_USER\Software\Pervasive


Software\Communications Requester\Version 7\Settings. Delete SAT entries (ie SatEntry0, SatEntry1, etc) and set value for NumSatEntries to 0.

Note: With Pervasive.SQL 7 and Pervasive.SQL 2000 pre-Service Pack 2 the keys are located under HKEY_LOCAL_MACHINE. If you are not using NetBIOS be sure to remove it from Configuration Utility under Communication Protocols\Supported Protocols at both the server and client machines. To find out more about SAT entries visit the following Web Page:What is the purpose of the SAT entries

American Date Settings


UK Settings for All: Before installing any software, including printer drivers, the regional settings for the default user has to be set to UK. Simply changing the settings within control panel will not have the desired effect, it will only change the Hkey_Current_User portion of the registry. It does need to be changed in control panel so that the required language files are loaded onto the system. To change the default user portion of the registry, you need to use regedt32. Select Hkey_users, highlight the HKEY_USERS key and then choose Registry, load hive and open %PROFILES%\default user\ntuser.dat. The part of the registry that needs changing is in \control panel\international. The screen shot below shows the registry as it should be. The entries are case sensitive.

On Citrix Systems, further reading can be found by opening the following Link:http://ctxex10.citrix.com/index.jsp and Searching the Forums for US Date.
The file has reached it's phyical size limit. Currently Enterprise uses Btrieve version 6 format files with have a maximum size of 4Gb. You must Purge some data to clear space inside the file.

Exchequer Payroll
Installation Insert Exchequer Enterprise CD, open Windows Explorer, select Payroll Directory and select SETUP.EXE to start the installation. Follow the on-screen instructions changing the Destination Directory if required. You should find that the Typical Installation option should be sufficient. Upon completion of the installation run Exchequer Payroll from the option added to your start menu. You will then be prompted for a password, leave this blank, press Enter and you will then be requested to select whether this is a demonstration installation or registered installation.

If this is a registered installation select 'Yes' to enter your registration details. Ensure that the Licence Number, Company Name and the PIN are entered exactly as shown on the Licence Certificate. Once registered the program will close to allow registration of Exchequer Payroll to be completed. When you next start Exchequer Payroll it will ask for a default User Name and Password.

User Name: INTEX Password: (leave blank) Setting Up and Configuring the Exchequer Enterprise Accounts Link Select 'Accounts Link'- 'Configure Accounts Link' from the Company Menu.

Once selected you will be presented with the Configure Accounts Screen

Select the Accounts Package as Enterprise and you will be presented with the following screen.

Select OK to Continue. This will activate the live link to Enterprise and the 'Other' tab will be automatically selected for you. If the link fails with the message Enterprise Engine Not Started check to ensure the PATH statement includes the Main Enterprise Directory and then retry. Location of PATH Statement Windows 95/98 - C:\AUTOEXEC.BAT Windows 2000/XP - Control Panel, System, Advanced tab, Environment Variables, System Variables Upgrading to a Newer Version of Exchequer Payroll If a new version of Exchequer Payroll is available it is automatically sent out to all Insert Exchequer Payroll Upgrade CD and allow it to Auto-Start to start the installation. Follow the on-screen instructions changing the Destination Directory if required. You should find that the Typical Update option should be sufficient. Upgrading an Existing Payroll Licence When starting Exchequer Payroll enter SYSTEM for the User Name and ADMIN as the password. Select Licence and enter the new licence details. Support All support for Exchequer Payroll, other then PATH statement problem above, is through Intex Software. Telephone: 01642 672233 Email: support@intex.co.uk
Special Function 90 - Destroy Purged years History for Purged Customer/Supplier Accounts When Purging accounting data you can optionally delete Customer / Supplier Accounts that have a zero balance and no transactions would remain on the Ledger after the purge has Completed. Adding a new account with the same Account Code as one that had previously been Purged, the History Balances from the Old 'Purged' Account could be viewed. Because the balance at the Purge year is Zero this does not actually cause any problems. This special function asks for an account code and deletes all balances for this account prior to the last purged year. Special Function 91 - Destroy Purged years History for Purged Stock Accounts When Purging accounting data you can optionally delete Stock Records that have a zero balance and no transactions would remain on the Ledger after the purge has Completed. Adding a new Stock Record with the same Code as one that had previously been Purged, the History Balances from the Old 'Purged' Stock Record could be viewed. Because the balance at the Purge year is Zero this does not actually cause any problems. This special function asks for an Stock Record and deletes all balances for this Stock Record prior to the last purged year.

Transaction Values Differ on Some Reports


Why can a transaction show Correct value on the following reports on some reports but not others.

The following reports use the original exchange rate +/- any revaluations :Job Costing Customers ledger General ledger codes (Drill Down) On Vat Report On general ledger based posting report. Where as:Document based posting report Sales Daybook Report. Use the transaction's Original exchange Rate. From Entread helpfile- Trouble shooting Btrieve:Generall Applies to Win9x Version of the Windows O/S (Inc. Me) This error indicates that there is insufficient free conventional memory. Contrary to popular belief Windows applications do require a certain amount of free conventional memory. Try freeing up more memory by loading any device drivers within your CONFIG.SYS and AUTOEXEC.BAT files into high memory. Ideally a minimum of 540k of conventional memory is required.

Emails are sent without Priority Flag


Enterprise MAPI Email does not support Email Priority but Sending Via SMTP Does. This is a limitation of te MAPI component used by Enterprise.

Thunk Connect
If Windows reports the following error :"The procedure entry point Thunk Connect 32 could not be located in the dynamic link library Kernel32.dll" when loading Enterprise. Try renaming the following component in {sysRoot}/System and System32 directories:Rsrc32.dll This is a Windows Component described as "Resource Meter 32-bit Thunks". the PC will need to be rebooted to DOS for Win9x technology and Console for NT and above. This is achieved by pressing f8 when the PC is booting. This is generally caused by PCs that are upgraded from Win9x to NT technology. While this should not cause any problems running other applications, Exchequer Software cannot be sure that it will not and therefore accept not responsibility for renaming this file.

Procedure entry point cannot be found.


If the Following message is diplayed when loading Enterprise. :"The procedure entry point SUnMapLS_IP_EBP_40 could not be located in the dynamic link library

KERNEL32.DLL." The fix is to manually delete CALWIN32.DLL and CLNWINTH.DLL from the System32. These are Novell components that are not required for Nt technology Networks. If you do experience this on a Netware Network, Unistall the Novell Client and install the latest version available.

Status Code 22 Erroneous Status Code 22 when Using the ActiveX Interface Issue: Status Code 22 (The data buffer parameter is too short) generally results from there being a difference in the physical record size and the defined record size in a table definition. In some cases, the ActiveX Interface can generate a Status Code 22 for no apparent reason. This behavior can occur when there are more than 50 fields in a DDF's table definition, even when the record size in the table definition and the physical record size match. Resolution: This issue will be addressed in the next service pack for the Pervasive.SQL SDK. Apply The latest Pervasive Service Packs. Currently they are:SP6 for Pervage v7 If current SP level is 2 or lower you should apply SP3,4 and then 6 SP4 for Pervasive 2000 All 4 Service packs must be installed in Sequence. Error 95 - Status 95 on a Netware server with Token Ring (The session is no longer valid) was returned by the application and SmartScout. The -R parameter (Receive Packet Size) was set to 4096 (for Token Ring). SmartScout failed on packet size 1536. Solution: In STARTUP.NCF, the Set Maximum Physical Receive Packet Sized was set to 1514. This was set to the correct value (4202) for Token Ring, which solved the problem. If problem persists, increase this setting to 4540.
Special Function 99 - Reset sold Batch Records still marked as unsold Compares the rounded up quantity available on all unsold batches (using the system set-up qty no. of decimals) and will reset any showing as zero to sold.

Partially recoverable VAT


Option1 For customers who may not know what is recoverable but want to go ahead and add PINS into Ent. Set up a spare VAT code but with the full 17.5% rate. At the end of the VAT quarter, hopefully they will know how much is recoverable, e'g 40%. The VAT report can then be printed to view how much VAT has gone to the

special VAT code. Then it's a simple matter of calculating 40% of the VAT value. Then raise a PJI to this VAT code for the amount NOT recoverable, use a 'Irecoverable VAT' P&L GL, and then amend VAT to the same amount but negative. The PJI should be a 0.00 total but NET Goods and VAT will be adjusted correctly. Print VAT report again to se if VAT and Net goods now corrected for the special VAT code. ----------------------------------------------------------------------------Option 2 e.g. Normal SIN with standard VAT as 17.5 % Net 100 VAt at 17.5% = 17.50 Total incl VAT 117.50 VAT is partially recoverable so: 41% of 17.50 = 7.17 Normal VAT amount 17.50 less 7.17 = 10.33 which is added to Net End result is therefore: Net 110.33 (100 + 10.33) VAT = 7.17 Total = 117.50 Solution. Set up a spare VAT code with %6.50355 (The VAT Table does accept more than 2 decimal places) Raise SIN, putting the full VAT inclusive amount into line unit price, e.g.117.50 and use VAT rate (I) inclusive based on VAT rate 6. VAT and net will be worked out for you if you only have the total value of SIN incl.of VAT.

System Password Options


All of the options available under the system password should only be run after reading the Almanac and under the supervision of your Enterprise provider. These options are described briefly below giving an overview of their use and where to find them.

Rebuilds
From the Utilities Menu under Rebuild the extra options below are available by use of the System Password.

Check All Accounts This is available without the use of the system password and can be run to correct balances after a system failure. This can be used to recalculate all customer and supplier accounts. Before continuing with the option a confirmation of the check is displayed to allow exit if chosen by mistake.

The account balances will be updated from the transactions held on the account. This option should be run after adding a new company and copying customers and/or suppliers from another company. Check All Stock Levels This is available without the use of the system password and can be run to correct balances after a system failure. This can be used to recalculate the stock at all locations from the transactions held on the ledger. It

should be always be run after adding a new company and copying stock records from another company. This option also recalculates the FIFO/LIFO database. An option is given to confirm the check which can take a considerable amount of time if you have a large database.

Check Every GL Actual Totals This option will recalculate all the General Ledger Account totals from the Transaction Details File. The entire General Ledger tree will be cleared and the figures re applied from the underlying details file. The need for this can be an unexpected interruption during a posting run causing the General Ledger to become corrupted. Check All Cost Centre/Department balances This routine will reset all the Cost Centre/Department balances to zero and scan all posted transaction lines containing Cost Centre/Department codes and recalculate the General Ledger Cost Centre/Department combination balances again based on the underlying data for all periods and all currencies. Depending on how many Cost Centres and Departments there are and the size of the details.dat file this may take a considerable amount of time. It is should always be run after a complete backup and with any automated backup procedures disabled. Note: When first switching on Budgeting by Cost Centre and Department in System Setup this will need to be run if the previously entered data is required for full analysis. Check all Job Totals This will recalculate all the job totals from the job actual records. This is only available with the system password and will recalculate all job totals. When running this it is advisable to say NO to the question recalculate Analysis codes unless there have been significant changes to the analysis types. This should only be run after a complete backup and with no users entering transactions that may affect Job Costing. Note: Following this option it is adviseable to run Recalc all Job contracts to ensure the update of all higher levels. Verify All Job Actuals This is a much less aggressive version of 'Reset Job Actuals' that attempts to resynchronise job actual lines with the detail lines rather than recreating them. It will create new job actual lines if they are missing. All existing job actual lines will have their invoiced, posted and WIP flags intact so a repost should not be necessary unless new lines were created. When running this it is advisable to say NO to the question recalculate Analysis codes unless there have been significant changes to the analysis types. Note: Following this option it is adviseable to run Recalc all Job contracts to ensure the update of all higher levels. Reset All Job Actuals This is equivalent to a total unpost of Job Costing. This should only be run after a complete backup and with no users entering transactions that may affect Job Costing. When running this it is advisable to say NO to the question recalculate Analysis codes unless there have been significant changes to the analysis types. This will remove the job actuals records and recreate them from the original transactions. The newly created records will appear on the Job Daybook. These will need to be reposted. Check all Job Totals will need to be run to reset the totals. This can be done either before or after the repost has been done. Note: All previously tagged items invoiced through Job Costing will be returned untagged. If the CIS/RCT module is in operation and uplift costs have been edited these uplifts will need to be reentered before the repost.

Individual Job Options

There are now options within the View Job Check button.

Check Job Totals This will recalculate the job totals from the job actual records for the highlighted job. When running this it is advisable to say NO to the question 'Recalculate Analysis Codes' unless there have been significant changes to the analysis types. This should only be run after a complete backup and with no users entering transactions that may affect the Job being checked. Note: Following this option it is adviseable to run 'Recalc all Job Contract Totals' to ensure the update of all higher levels. Verify Job Actuals This is a much less aggressive version of 'Reset Job Actuals' that attempts to resynchronise job actual lines with the detail lines rather than recreating them. It will create new job actual lines if they are missing. All existing job actual lines will have their invoiced, posted and WIP flags intact so a repost should not be necessary unless new lines were created. When running this it is advisable to say NO to the question 'Recalculate Analysis Codes' unless there have been significant changes to the analysis types. Note: Following this option it is adviseable to run 'Recalc all Job Contract Totals' to ensure the update of all higher levels. Reset Job Actuals This will unpost all the transactions for the highlighted job and will recalculate the job totals to remove the figures from the job. Note: All previously tagged items invoiced through Job Costing will be returned untagged. If CIS/RCT module is in operation and uplift costs have been edited these uplifts will need to be reentered before the repost.

Procedures/Unposting
Note Before any of the unpost routines are run it is essential that a complete backup of the system is taken. This may be required in the event of a system failure during the routine.

Total Unpost The Total Unpost routine is a blunt instrument that will return all transactions entered into Enterprise back to their respective daybooks and removes all the General Ledger balances. There is no subtlety about this procedure other than an implicit assumption that the underlying transaction data is correct, and that a repost following the unpost will correct whatever problem there is. The basis of the Total Unpost is that a full post will be required after the unpost has finished. This could be a very lengthy process depending on the size of the Enterprise datafiles. Partial Unpost The Partial Unpost by Period is a more precise version of the Total Unpost, in that it allows you to specify to which period you wish to 'unwind' the General Ledger back to. This is on the assumption that although the General Ledger no longer balances in the current period, it does in a prior period. By unposting everything after the 'balancing' period and reposting we can correct the imbalance. Unpost by Run Number This facility to roll back a previous posting run is incorporated from Enterprise version v5.52 onwards. This facility will attempt to reverse the effect of one or more posting runs from the last posting run backwards. It achieves this by reverse posting all the values stored for a previous posting run. For example, when posting run 5 is requested all posting runs from the current posting run back to and including run 5 will be reversed out.

It is unlikely that this facility will recover from a failed posting run or where the Trial Balance does not balance. It is designed to circumvent the need to run a partial unpost by period where a user has posted transactions that they now realise need amending.

General Ledger
From the General Ledger Tree - Options - Check All GL Totals Occasionally the General Ledger header totals do not add up to the figures contained within them. (For example, a failed move of a General ledger code or a situation where the simplified Trial Balance balances, but the standard Trial Balance does not.) In Enterprise versions prior to v5.51, the only way to re-establish the header totals was to do a Total or Partial Unpost. From version 5.51 onwards it is possible for Enterprise to scan all the General ledger actual posting codes (those General Ledger codes used on the transaction lines) and recalculate all the parent totals from them.

Job Tree
From the Job Tree - Options there are two new options available from version 5.60.001.

Check all Highlighted Job Totals. This does the same as Check Job Totals on a single job but is extended to allow checking of all jobs within that contract. Note: Following this option it is adviseable to run 'Recalc all Job Contract Totals' to ensure the update of all contract totals. Recalc all Job Contract Totals. This takes all the job totals and ripples them up through all the contract levels throughout the job tree. This needs to be run following a reset or verify actuals on a single job to correct the upper levels.
Special Function 102 This is used where corrupt detail lines exist and cannot be manually deleted off a transaction. Symptoms: Corrupt transaction(s) causing aged reports to display incorrect figures and Check Account routine to hang. SF1 should be run prior to running SF102 Special Function 103/Special Function 105 One off customer specific following incorrect import. Special Function 104 The payment flag on PINs were being corrupted by the toolkit so lines were being posted to the wrong side in the General Ledger and causing corresponding reverse items in the suspense account. This error in the toolkit also affected authorise plugin when a transaction was authorised. SF98 Remove Corrupted FIFO records. Searches througfh the FIFO database and deletes any corrupted records. A report is produced that list the records that were delete, the in Document Number and the Stock Cost. Running check on the reported Stock records will be required to complete the process. This Function can be used where the FIFO tab on a stock record/s are blank but unused 'IN' Documents Exist and running check on the Item does not fix.

Databases - Additional Modules


The Exchequer Databases - Where the data is. EBUS\EBUSDETL.DAT eBusiness - Transaction Details

EBUS\EBUSDOC.DAT EBUS\EBUSLKUP.DAT EBUS\EBUSNOTE.DAT FAXSRV\FAXES.DAT IMPORT\EXSETUP.DAT IMPORT\THEADER.DAT IMPORT\TLINES.DAT IMPORT\TRANS.DAT IMPORT\IMPORTER.DAT SCHEDULE\SCHEDULE.DAT SMAIL\SENT.DAT SMAIL\SENTLINE.DAT TRADE\LBIN.DAT TRADE\LHEADER.DAT TRADE\LLINES.DAT TRADE\LSERIAL.DAT TRADE\TILLNAME.DAT TRADE\TRADE.DAT EBUS.DAT SENTSYS.DAT SCHEDCFG.DAT SMAIL.DAT

eBusiness - Transaction Headers eBusiness - Lookup Table eBusiness - Notes Faxes Database Import - Setup Import - Used as temporary transaction header store during conversion from CSV to IMP and check routine Import - Used as temporary transaction line store during conversion from CSV to IMP and check routine Import - Transactions Importer - Database Layouts, Field information, Default Settings Scheduler - Scheduled Tasks Sentimail - Sentinels Sentimail - Sentinel Details Trade Counter - Layaway Transaction Bin Details Trade Counter - Layaway Transaction Transaction Headers Trade Counter - Layaway Transaction Transaction Details Trade Counter - Layaway Transaction Serial/Batch Details Trade Counter - Till List Trade Counter - Settings eBusiness - Settings Sentimail - System Settings Scheduler - System Settings Sentimail - SMS Account/Licence File

Databases - Plug-Ins
The Exchequer Databases - Where the data is. JC\ACGROUPS.DAT JC\EMPPAY.DAT JC\GROUPS.DAT JC\MCPAY.DAT PROMPAY\PPCUST.DAT PROMPAY\PPDEBT.DAT PROMPAY\PPSETUP.DAT Job Card - Account Groups Job Card - Employee Records Job Card - Groups Job Card - Company Records Prompt Payment Plug-In - Customers configured for the Plug-In Prompt Payment Plug-In - Debt collection charge scale details Prompt Payment Plug-In - Setup

SALESCOM\COMMSSN.DAT SALESCOM\SALECODE.DAT SALESCOM\SCTYPE.DAT WORKFLOW\PAAUTH.DAT WORKFLOW\PACOMP.DAT WORKFLOW\PAEAR.DAT WORKFLOW\PAGLOBAL.DA T WORKFLOW\PAUSER.DAT ALLOC.DAT CCDEPT.DAT CH.DAT CONTACT.DAT ENPORSEC.DAT UDENTITY.DAT UDFIELD.DAT UDITEM.DAT

Sales Commission Plug-In - Commission Information Sales Commission Plug-In - Sales Codes Sales Commission Plug-In - Sales Code Types Authoris-e - Authorisers Authoris-e - Companies Authoris-e - Authorisation Transactions Authoris-e - Global Settings Authoris-e - Users CC/Dept Cost Allocation Plug-In - Settings CC/Dept Validation Plug-In - GL/CC/Dept combinations Custom Hold Plug-In - Settings Contacts Plug-In - Contacts Purchase Order Daybook Security Plug-In - Settings User Defined Field Plug-In - Tree Structure of Available Fields User Defined Field Plug-In - Field Information User Defined Field Plug-In - List items for fields with lists