 | A new option Edit | Other | Add/Edit
Labour has been added. This screen should be self
explanatory and is used to manually input labour units in
the employee database. Please note that all entries will
be applied to the current system period as follows: If the
month is greater than the current month, data is applied
to the previous calendar year. If the month is less than
or equal to the current month, data is applied to the
current year. |
 | Labour units were not being added to
the Employee database from Transaction | Inventory |
Assemblies. This has been corrected. This problem only
existed for those users who installed a 02/18/2003 Beta
update. |
 | The labour units for December were not
always zeroed properly. In some cases values from the
previous year were carried forward to the following year.
This has been corrected. |
 | Invoice Reprint routines have been
improved to provide better data compression. This should
eliminate issues where only part of an invoice prints when
the 'Reprint' feature is used. This does not correct any
existing data that was affected by previous routines. |
 | The option Setup | Forms | Payables |
Cheques has been redesigned. You will need to reconfigure
this option for your cheque forms. Several new Tech Tip
bulletins have been issued that deal with this new feature
and they are available
here.
This new feature will allow greater control over how your
payment cheques are printed. If your cheques
were printing just fine prior to this update, the
parameters you need to obtain the same results are
available here. |
 | Some issues with Package Quantities in
the vendor area of Edit | Inventory | Add/Edit have been
addressed. Problems with the 'Vendor Part Number' have
also been corrected ... again! |
 | The change to having 'Abort' the
default option on most screens has as expected caused some
'training' issues. An additional "Are you sure" prompt has
been added to some areas where considerable data can be
lost by using the 'Abort' option. |
 | Shop Trac now supports the Canadian HST
(Harmonized Sales Tax) for users outside of the HST area
(Maritimes), but who make sales into the HST area. A new
field in Setup | Defaults called 'HST Rate' needs to be
completed. Shop Trac knows who are HST customers by their
postal code prefix, so correct postal codes are important.
This tax will print on the invoice GST line. You may wish
to edit the invoice form and change this line to
'GST/HST'. HST customers are always considered PST exempt.
For users within the HST area of Canada, this new feature
can be ignored, and the rate set to zero. Shop Trac users
within the HST zone will continue to process HST (using
the GST fields) as they always have. In this case, the HST
rate field should be left at zero. |
 | The Edit | Inventory | Add/Edit now
processes superseded parts numbers in a more consistent
manner. The change with the Edit and Abort options
caused some problems, and this has been modified to
eliminate the 'Ok' option from this SED. This will never
cause a lock issue. |
 | The Transaction | Inventory | Count
option has been modified. The 'User2' field (normally used
for Bin Location) can now also be changed when using this
option. |
 | The unused "Rate' field on the Edit |
Receivable | Customers screen has been changed to 'Tax 2 -
Taxable'. This allows Canadian users to indicate zero
rated GST customers. This field will default to 'No'.
A
new option located at Utility | Supervisor | Reset Tax 2
will allow you to change this field for all accounts to
'Yes'. |
 | The GL Account fields on the Edit |
Inventory | Add/Edit screen are now protected. These
fields are assigned via the 'Manufacture Code', or via a
user with SUPERVISOR access. This should eliminate these
fields being modified by mistake. |
 | Several of the data export routines
have been improved to export data that is easier to import
into other Windows programs. |
 | Hopefully, a final Y2K bug. 2004
being the first leap year of the century caused some
problems with Date addition routines. This was most
noticeable on the 'Invoice Due Date'. This has been
fixed. |