Version 9.19 September 2004

SQL (Pervasive or MSSQL)
All previous versions of FactoryMaster used the Transactional Pervasive database (also known as Btrieve). This version has been re-written to use SQL based databases, specifically the Relational Pervasive databases (P.SQL 2000i and P.SQL 8) and MSSQL/MSDE.
All customers who do not specifically own an MSSQL database will be converted to Pervasive SQL which will have already been installed with the previous Btrieve database.

Program Locks
FactoryMaster no longer uses terminal numbers to determine who is locking which item (for example sales orders). Instead the user name is used, this means that if a user crashes out then going back in as that user will clear the locks. In addition a new mechanism has been implimented that should be able to tell if a user has crashed out of the system. This means that if a program lock (for example sales order lock) if encountered then if is VERY likely to be a genuine lock rather than being due to a user who has crashed.

User Access
It is now possible to view the members of an access group from the 'Assign Programs' option within user access.

Delivery Notes
Delivery note style 21 has been added.

Invoice Layouts
Invoice layout 16 has been added.

Nominal Codes, Invoices & Exporting To Accounting Packages
Nominal codes were previously only applied to Sales Invoices at the point when those invoices were exported to an external accounting package. Nominal codes were allocated according to defaults set up in 'Export Control' and through overrides keyed at part, product group and/or customer level.

The system has been amended so that nominal codes (and departments) are now allocated at the time the invoice is produced. Codes are allocated according to the same rules as previously, but the user can now view, and in most cases amend, the allocated codes prior to printing / exporting. The rules governing the allocation of nominal codes are now contained in a new option ('Nominal Code Control') on the Invoice Menu. (Note: new nominal codes will have been generated for Quickbooks users, together with cross-references to the full Quickbooks code which will be applied at the time of export.)

Once an export batch has been produced it is no longer possible to directly edit any of the information before exporting the batch to your accounting package. This is to ensure greater data integrity between FactoryMaster and the accounting package. The 'export history' screens have been redesigned however to make it easier to set up 'cross reference' tables for cases where the codes set up in FactoryMaster do not match those in use in your accounting package. If completely the wrong code has been entered on the invoice you will need to remove the invoice from the batch, correct the invoice and re-add it to a later batch. This change of behaviour is common to all the sales, purchasing, stock and factoring exports.

The choice of accounting package, and the options & defaults associated with it are now set in the 'Company Details' option of the 'System Maintenance' menu. Most export styles now allow the user to select a different file location to the default specified, and also to view the generated file in 'Windows Notepad'.

Import Purchase Prices
A new option has been added to the 'Import Data' option under 'System Maintenance' to allow stocked part supplier prices to be imported from a CSV file. Note that this option can only import prices for a batch quantity of '1'.

Purchase Invoice Matching
The receipt (or reject) date has been be added to the main 'Invoice Matching' screen. This is colour coded to highlight items which were received (or rejected) AFTER the invoice date entered.

'Where Used' Screen
This screen now shows the LOP or # number for each component. In addition the user can see where each assembly the part is used in is itself used by pressing F5 or using the button at the bottom of the window.