AccountMate 7.3 for SQL Release Notes
July 13, 2007
Installation File Contents
The AccountMate 7.3 for SQL CD contains the following components:
·
AccountMate 7.3 for SQL Program Files
·
Microsoft Visual FoxPro 9.0 (Service Pack 1) Runtime Files
·
Seagate Crystal Reports XI (Service Pack 1) Runtime Files
Bug Fixes
Refer
to the AccountMate 7.3 for SQL/Express Maintenance Release Summary under the
Maintenance and Technical Support section of the AccountMate Business Partner
Home Page.
Important Changes
Support Windows
This
AccountMate version supports workstations that run on a Windows Vista operating
system. Several changes have been made in the system to meet the new Windows
Vista security requirements. Users who are running AccountMate 7.3 in Windows
Vista must set their computers to use the “Windows Standard” theme.
DSN-Less Connection to the SQL Server
Users are no longer required to set up an ODBC System Data Source to connect
AccountMate workstations and file servers to the SQL Server. The user is
prompted for the SQL Server instance name the first time that AccountMate or
the Administrator program is launched from a workstation or file server. This
information is saved in the system and will be used to establish connection to
the database server. This enhancement simplifies the implementation process for
those who run AccountMate from a file server as they no longer need to create
an ODBC DSN connection on each workstation.
Support Foreign Keys to Help Enforce Data Integrity
There
are different ways to enforce data integrity. AccountMate uses the default,
check constraint, trigger, and/or stored procedures.
In this version release, we support the creation of foreign keys to help
enforce data integrity. The Create Table file (Amtbl.DBF) is changed to
include the mFKStmt field that stores the SQL statement that will create
the foreign keys for each table. Foreign keys are added using the ALTER TABLE –
SQL Statement after all the indexes are created.
A foreign key does not accept a blank value; which means that if the foreign
key field is not mandatory and the value does not exist in the primary table,
the foreign key field value will be set to NULL. A foreign key field that is
used as a primary key in the table does not accept NULL value; its value must
exist in the primary table.
This
feature helps to address such issues as out of balance caused by missing account
IDs, orphaned allocation accounts, and the like. Currently, foreign key is
implemented only for the GL Account ID field.
Tighter Integration for Inventory, Customer and Vendor Item
Records
AccountMate
users have the ability to maintain records of their customers’ item numbers
and/or vendors’ part numbers with which they can enter customer/vendor orders.
In previous versions, the system item numbers are kept separate from the
customer/vendor item records and the item # search function focuses solely on
the system item numbers. When the system is set up to use customer item
numbers/vendor part numbers during order entry, users cannot enter orders for
inventory items that do not have customer item number/vendor part number
records in the system.
These
limitations have all been addressed in version 7.3:
Item # Lookup to Include Customer Item Numbers
Note: The following enhancement only applies to AccountMate
installations that have the Customer
Inventory Manager (CI) module.
Although
the system and customer item numbers are still stored in separate tables in
version 7.3, users can now set the system to include the customer item number
records when searching for an item. This is made possible through the “Item #
Search in Inventory Maintenance” feature in IC Module Setup. Users who maintain customer item number records
and wish to include these records during an item # search must mark the
“Include Customer Inventory File” checkbox. When this is activated, the system
will display the Customer Item # Search
window in addition to the Item # Search
window. This facilitates identification of the correct inventory record
especially when processing customer returns where the return document only
shows the customer item number.
Item # Lookup to Include Vendor Part Numbers
While
the system item numbers and vendor part numbers are still stored in separate
tables in version 7.3, users can now set the system to include the vendor part
number records when searching for an item. This is made possible through the
“Item # Search in Inventory Maintenance” feature in IC Module Setup. Users who maintain vendor part number records and
wish to include these records during an item # search must mark the “Include
Inventory Vendor File” checkbox. When this is activated, the system will
display the Vendor Part # Search
window in addition to the Item # Search
window. This facilitates identification of the correct inventory record
especially when following up on a vendor communication that only identifies the
vendor part number.
Input Inventory Item # for Customers/Vendors Set Up to Use Their
Own Part Numbers
Note: The customer item number feature enhancement only
applies to AccountMate installations that have the Customer Inventory Manager (CI) module.
Users
now have the choice to enter orders for inventory items that do not have
customer item numbers or vendor part numbers for those customers/vendors set up
to use their own part numbers during data entry. A new option to “Allow
Inventory Item #” is added to the available settings in the Customer Maintenance and Vendor Maintenance functions. This
feature is only available when the “Use Customer Item #” checkbox is marked in
Customer Maintenance or when the “Use Vendor Part # for PO Entry” checkbox is
marked in Vendor Maintenance. When entering orders for customers or vendors set
up to use their own part numbers, users can enter an item number that matches
an internal item record but is not a customer item number or vendor part number
provided that this new feature is activated.
Allow Shipment of Regular Inventory Items from Multiple Bins
In
previous versions, the Ship Sales Order function allows shipment from
multiple bins for special items only. Special items are ones that are
serialized, lot-controlled and/or kit items. Regular inventory items could be
shipped from one bin only. This required users to record multiple shipment
transactions for an item that is stocked in several bins, making the process
more time consuming and vulnerable to data-entry mistakes.
In
this version release, the system is enhanced to support shipment of regular
inventory items from multiple bins. When the shipment quantity exceeds the
on-hand quantity in the designated bin, the Select Ship Qty function
window appears which lists the current on-hand quantities in each bin assigned
to the item. This makes it easier for users to view alternative locations in
the same warehouse where they can get the items and prepare them for shipment.
In this same window, users can enter the quantities to be shipped out of each
bin. For each selected bin, a separate entry is created in the Line Item grid
showing the relevant shipment quantity. The primary line item-bin record is
identified by a non-zero Open Qty while the subsequent bin entries for the same
line item will have a zero Open Qty. Adjustments to the shipment quantity must
be entered through the Select Ship Qty function window once an item is
set for shipment from multiple bins. The Select
Ship Qty function window can also be accessed by double-clicking the Ship
Qty field.
Allow Negative Quantities of Serialized Items in AR Invoice
Users
on previous AccountMate versions cannot enter a negative quantity for a
serialized item when recording a sales invoice. This is because the “Allow
Negative Qty on Invoice” feature is disabled for items assigned either a
Specific ID or Average with S/N cost method. This complicates processing of
sale transactions that involve returns or trade-ins of serialized items since
users must record the return transaction separate from the regular sale.
Version
7.3 has addressed this limitation. Users can now mark the “Allow Negative Qty
on Invoice” checkbox in the Inventory Maintenance function even if the item is
serialized. This allows users to record returns or trade-ins of serialized
items along with the regular sale in a single invoice transaction. Not only
does this save data-entry time, it also simplifies the invoicing and billing
process as users and their customers need only look at a single sales transaction
document. Unless the “Allow Duplicate Serial # checkbox is marked in IC Module
Setup, the system will validate the serial number assigned to the returned or
trade-in unit against the ones that are on-hand to ensure that there are no
duplicate serial number records for the same item.
New "Mark All" Checkbox on the Grid Header of the Post
JE Batch to GL Function
In
previous versions, the user has to manually mark each checkbox that corresponds
to the journal entry batch that is to be posted. Depending on how many batches
are up for posting, this process may be too tedious for the user.
In this version release, the system is enhanced to allow users to quickly
select all journal entry batches that are available for posting. A checkbox is
placed at the top of the grid for easy access. Mark this checkbox to select all
JE batches for posting; unmark to deselect all records.
Various Enhancements to the Post AP Invoice Function
There
are a few changes to the Post AP Invoice function in this version
release. They are as follows:
Allow Copy and Paste from Excel into the GL Distribution Grid
The
system supports pasting of data copied from an Excel file. For users who deal
with payable invoices that have multiple distributions, this provides a quicker
way to record invoices and minimize data-entry mistakes.
The
paste action expects data for the GL Distribution Accounts and Amount columns.
When preparing data in Excel, users must put the two columns side-by-side in
the same order as they are displayed in the GL Distribution grid. Open the
Excel file and select the lines of data to be copied. Press CTRL + C on the
keyboard or access the Copy function from the Edit menu. In
the AccountMate screen, right-click anywhere on the GL Distribution grid and
select "Paste from Excel" in the pop-up menu. The following
message will appear:
“Do you want to
overwrite the existing GL distribution entries?”
Choose
"Yes" to replace the default distribution with the records copied
from Excel; choose "No" to keep the default distribution and add the
records copied from Excel. Each copied record is subject to the same data
validation that the system performs when users manually enter the distribution
accounts and amounts. When a problem is detected, the record will not be pasted
onto the grid. To successfully copy data, the following rules must be met:
·
The GL Account ID must be an active record.
·
The GL Account ID must be a posting account; it cannot be an
allocation account.
·
The distribution amount must not be zero.
"New" Command Button Becomes the Default Choice after
Saving an Invoice
To
help speed up data entry in this new version, the cursor now falls by default
on the “New” command button in the Save window. This will allow users to initiate recording
of a new AP Invoice immediately after saving another by simply pressing the
Enter key.
Journal Entries for GST/PST Claim Back
Note: The following enhancement only applies to companies
assigned the country tax for
In
previous versions, the default journal entry for GST/PST claim back is combined
with the regular AP invoice distribution as follows:
DB: AP Invoice Distribution Accounts
DB: Sales Tax Costs
CR: Accounts Payable
In
this version release, the default journal entry for GST/PST claim back is
segregated from the AP invoice distribution and is changed to:
DB: Sales Taxes Payable
CR: Tax Claim Distribution Accounts
The
actual Tax Claim Distribution Accounts that will be credited are based on the
GL Distribution assigned to the AP invoice. If there are multiple distribution
accounts assigned to the AP invoice, the GST/PST claim amount will be prorated
among these accounts. If the invoice’s distribution includes a reversal of PO
receipt accruals or PO landed cost accruals, the system will use the Sales Tax
Costs account in lieu of the Accrued Received Goods account to ensure the
proper matching of outstanding
When
the user marks the "Claim" checkbox, the system displays the
following message:
“You must verify the
tax claim distribution before saving the invoice.”
In
the GL Distribution page tab, the "Tax Claim Dist..." command button
is enabled. When clicked, the Tax Claim Distribution function window is
displayed for users to review the default journal entries that will be
generated for the tax claim back. GST claim back will have journal entries
separate from that of the PST. Users can change the Sales Taxes Payable and/or
GL Distribution accounts when necessary.
Support Electronic Payments in AP
The
AP module now supports the generation of Automated Clearing House (ACH)
electronic payment files. Users can activate this feature for each company by
marking the "Electronic Payment" checkbox in the AP Module Setup
function. To set up ACH direct deposit for each vendor, mark the
"Electronic Payment" checkbox in Vendor Maintenance. The
system will display the Electronic Payment Setup window where users can
enter information that will be used during electronic payment file generation.
This
version also provides the means to override a vendor’s electronic payment
setting during a particular check run. Simply mark the "Use Check"
checkbox when running the Print Computer Check function to print regular
checks for vendors set up for ACH direct deposit. This checkbox is disabled and
marked if payments to a vendor are always made by check. It is enabled and
un-marked if payments to a vendor are to be processed electronically. Users
need not change or lose the electronic payment information set up for a vendor
whenever a regular check has to be printed.
Option to Print Regular Check for Employees Set Up for Electronic
Payment
In
previous versions, the Print Payroll Check function always generates an
electronic payment file for employees set up for payroll direct deposit. If a
check has to be cut for these employees, the user has to deactivate the
"Electronic Payment" feature in the employee record thereby losing
the employee’s direct deposit account information.
In
this version release, the Print Payroll Check function comes with an
override option in the form of a "Use Check" checkbox. This checkbox
is disabled and marked for employees who are paid by regular check. It is
enabled and un-marked for employees set up for direct deposit. Mark the
checkbox to print a regular check and ignore the employee’s electronic payment
setting. Users need not change or lose the electronic payment information set
up for an employee whenever a regular payroll check has to be printed.
Support Wachovia and Fifth Third Bank Positive Pay File Formats
The
system is enhanced to support positive pay file layout for Wachovia and Fifth
Third Bank. This brings the supported format count to six, namely:
·
Bank of
·
CNB
·
Fifth Third Bank
·
HSBC
·
LaSalle Bank
·
Wachovia
Default AP Deduction Settings in Deduction Code Maintenance
In
version 7.1, we introduced the AP Link feature in Payroll. This feature allows users
to associate an AP vendor with the deduction code assigned to an employee
record, and generate a report that can be used as a basis for remitting
deductions to the appropriate parties.
In
our latest version release, the system is enhanced to allow users to assign a
default AP vendor to deduction codes set up for AP Link thereby reducing the
steps required to use this feature. In the Deduction Code Maintenance
function, when the "Link to AP" checkbox is marked the system will
require users to complete the AP Deduction Setup. The information thus
entered serves as the default setting when the deduction record is assigned to
employee records. This saves data-entry time as users need not enter the same
information each time a deduction code (e.g. 401K, medical insurance, etc.) is
assigned to an employee record while still giving them the flexibility to
customize this setting for certain employees when the nature of the deduction
(e.g. garnishment) makes it necessary.
New Option to Match Unapplied Deduction when Applying Payroll
When
we introduced the Employer Matching/Contribution feature in version 7.1, the
original design did not give users the ability to choose whether the system is
to calculate the employer’s contribution to the deduction when no deduction is
applied against the employee’s payroll. Even when the user has opted not to
apply certain deductions during a payroll run the deduction code will still be
listed in the Deductions grid of the Apply Payroll/Payment function
window and the employer’s share is calculated as long as the deduction code is
set up for "Employer Matching/Contribution" and its assigned
"Matching/Contribution Method" is Fixed Amount, Rate/Hour, Percentage
of Gross, or Percentage of Net.
In
this version release, the system is enhanced to allow users to choose whether
they want the employer to match the unapplied deductions during a particular
payroll run. In the Apply Payment Options page tab of the Apply Payroll/Payment
function, mark the "Match Unapplied Deduction" checkbox if employer
matching/contribution must be computed even for the deduction codes that are
not to be applied against the employee’s payroll. Unmark the checkbox to
exclude those deductions that will not be applied against the employee’s
payroll from calculation of the employer match.
Ability to Suppress or Include Credits Applied from Sales Returns
in the Payment Distribution Report
In
previous versions, the Payment Distribution Report always lists the
credits applied from sales returns and regular payments. Users could not
generate this report showing just the amounts applied from regular customer
payments. Also, they must manually add the amounts to determine the total
credits applied solely from regular payments.
In
this version release, users have the option to suppress credits applied from
sales returns when generating this report. Mark the "Include App Credits
from Sales Returns" checkbox to generate a report that shows both the
applied payments and credits applied from sales returns. Unmark this checkbox
to suppress the applied sales return details. With the ability to suppress
applied credits from sales returns, users now have a report with which to
validate distribution of regular payments.
Credits
applied from sales returns are listed in this report with "APP CR"
for their Receipt #. Regular payments are listed with the Receipt # assigned
during the Apply Payment process.
View Customer Transactions Listing in Summary or Detail Format
Note: The following enhancement is only available in the Accounts
Receivable (AR) and Contact Manager (CM) modules.
Users
can view a list of transactions recorded for their customers through the
Customer Transactions Listing. In previous versions, the information contained in
this report is detailed down to the line items, discounts, freight, taxes and
adjustments which are displayed as individual transaction items. For an
organization that issues a large number of invoices with each one composed of
multiple line items, this report may provide more detail than the user actually
needs.
In
this version release, a new report called Customer Transactions Summary
Listing has been added. This
report is similar to the original Customer Transactions Listing with one major
exception: each AR invoice is listed as one transaction record. Meanwhile, the
original Customer Transactions Listing has been renamed Customer
Transactions Detail Listing.
Ability to Track Upsell Transactions
Previous
versions did not come with reports that showed which inventory items were sold
as upsell items.
In
this version release, the system is enhanced to allow users to distinguish
regular line item sales from upsell item sales. Simply mark the "Identify
Upsell Line Items" checkbox in the report criteria selection window to
display the "Upsell" column in the report. A "Yes"
indicates that the line item was sold as an upsell item; a "No"
indicates a regular line item sale. This enhancement is available in the Invoice
Line Item Report and the Sales Order Line Item Report.
The
Commissionable Sales Report is also enhanced to allow users to view only
the commissionable sales of upsell items. Mark the "Show Upsell Line Items
Only" checkbox to generate a report for line items sold as upsell items;
unmark to view all line items. This enhancement helps simplify the commission
process for those companies that implement a different commission scheme for
upsell item sales.
Show "Total Hours" and "Total Amount" by
Earning Code in the Time Card Entry Report
The
Time Card Entry Report has been enhanced to show total hours and amounts
per earning code. This information is available with the sorting options “Dept
# + Employee #” and “Dept # + Last Name”. Total hours and amounts are shown for
the entire report as well as for each department. With this enhancement, users
are better able to validate and monitor the distribution of employees’ payroll
hours.
New Option to Include GL Distribution in Bank Transaction Reports
Starting
with version 7.1, transaction functions such as Record Deposits/Other
Receipts, Record Checks/Other Disbursements, and Record Bank
Transfers allow users to set up GL distributions that may involve multiple
reference accounts per transaction. Moreover, each transaction’s GL
distribution may differ from the default defined in the transaction code. To
facilitate validation of journal entries generated for bank transactions,
version 7.3 is enhanced to give users the option to view the GL distribution
alongside the bank transaction details in certain reports. Mark the
"Include GL Distribution" checkbox in the report criteria selection
screen to show the GL Accounts used in transactions. Leave it unmarked to
suppress this information. This enhancement is available in the following Bank Transaction Reports: Unverified
Receipt Report, Verified Receipt Report, Outstanding Disbursement Report, and
Cancelled Disbursement Report.
Ability to Filter Records by Warehouse when Performing Inventory
Reorder Qty Update
In
version 7.3, the Inventory Reorder Qty Update function is enhanced to
use the warehouse as one of the ways by which users can select inventory
records to be updated. Mark the checkbox for the "Warehouse" filter
to include items in all warehouses that meet the other selection criteria. To
select one or a range of warehouses, unmark the checkbox to enable the
warehouse range fields. Enter the range of warehouse values to further filter
the inventory records that are to be updated.
Build Kit Item Function Optimized
The
Build Kit Item function is further optimized in this version release to
help improve the system’s performance and increase user productivity.
Inventory Maintenance
There
are a few changes to the Inventory Maintenance function in this version
release:
"Use Specification" and "Used in Work Order"
Settings are Mutually Exclusive
The
Inventory Specification (SP) and Manufacturing (MI) modules are
incompatible. In previous versions, however, the system allows users to mark
the "Use Specification" checkbox even when the inventory item is
already marked as "Used in Work Order". To prevent confusion and
avoid potential data problems, version 7.3 is designed to ensure that only one
of these settings is assigned to an inventory item. This change does not affect
inventory item records that were set up in previous versions until the next
time the items are accessed through the Inventory Maintenance function.
Deletion of an Inventory Item Used as Component for a Build-On-The-Fly
Kit Item is Not Allowed
In
previous versions, inventory items used as components for build-on-the-fly kit
items can be deleted from the system even if the kit item is used in current
transactions. Regular items, on the other hand, must not be used for the system
to allow their deletion. Inventory items may be archived only when their
on-hand quantity is zero and they have no outstanding un-posted transactions.
Deleting kit components used in un-posted transactions will cause an out-of-balance
when the user runs either the Transfer to GL or Period-End Closing
functions. This is because the system cannot find the GL Account IDs that it
needs to generate journal entries for these inventory items.
In
this version release, the system is enhanced to check for kit components used
in current, un-posted transactions when the user attempts to delete an
inventory item record. The inventory item must not be used in these
transactions before they can be deleted from the system. This change is designed
to help keep the General Ledger accounts in balance.
Ability to Turn Off the "Top N
Records" Feature of the Leading Search Function
In
previous versions, the system will display the first 50 records when the
"Display top N records for leading search with blank search value" is
set to zero (0). Consequently, there was no way to turn off the “Top N records”
feature.
In this version release, users can turn off this feature. Simply enter a zero
(0) value in the "Display top N records for leading search with blank
search value" field of the Advance
Search function window for the system to display in the search grid ALL
records that match the search value. By default, the system is set up to
display the first 50 records for a blank leading search.
CAUTION: Turning off this feature may slow down the search process especially
when huge data sets are involved.
File Attachments
There
are a few enhancements to the File Attachment function in this version
release. They are as follows:
New “Added By” Column Tracks Who Added the File Attachment
A
new column is added to the File Attachment function window. The
"Added By" column identifies the user who attached the file to the
transaction or master record. As with existing columns, this new one can also
be used to sort the records displayed on the screen. Click the column header to
sort records in ascending order; click again to sort in descending order.
Files
attached in previous versions will show "System" for the user name.
Support User-Defined Validation Routines for File Attachments
Some
users may want to restrict file attachments to a specific file format and/or
size. While AccountMate does not perform such validation out of the box, it
does allow users to define their own validation. Users must create a record in Amaddon.DBF
using the function name VALIDATTACHMENT and a cOwner field value that is
not "AM". The available information is as follows:
·
gxParm1 = Attachment Type (Amattach.cType)
·
gxParm2 = Key Value 1 (e.g. Customer # if cType = cCustNo, SO #
if cType = cSONO, etc.)
·
gxParm3 = Key Value 2 (e.g. Customer # if cType = cCustNo, SO #
if cType = cSONO, etc.)
·
gxParm4 = Path and File Name
The
function must be evaluated TRUE (.t.) for the system to accept the file
attachment; otherwise, the attachment action will be cancelled. The VALIDATTACHMENT
function is executed when the user clicks the Attach command button provided
that AccountMate’s validation does not detect any error. AccountMate’s
validation includes:
·
Mandatory remark
·
Mandatory filename
·
Checking of duplicate file names
·
Checking of duplicate file attachment records
New Report Setup Function
Report-related
settings are consolidated into one function in this version to simplify the
setup process. Access the Report Setup
Options beside the printer icon on the Power Toolbar. Expand the function
list and select Report Setup. The Report Setup function window
has three (3) page tabs, namely: Paper Size, Color, and Preview Magnification.
In
the Paper Size page tab, choose between Letter and A4 for previewing or
printing reports. In the Color page tab, choose the default color for
Drill-Down fields and the Form Label Background. In the Preview Magnification
page tab, choose the magnification factor that will be used in the display
during a report preview.
New Option to Change Default "Form Label Background
Color"
The
"Form Label Background Color" setting is a new option with which
users can change the background color for special report forms. The default is
set to aqua. To save printer ink, a lighter background color may be
selected.
New System Setup Function
System-wide
settings are consolidated into a single function called System Setup.
This function includes the settings that used to be defined through the
Module/Menu Display Setup, Error-Log E-mail Setup, Century Setup, and
Multilingual Setup functions. By combining all these features into one
function, users get a more streamlined setup process.
Save Shortcut Pane and User Grid Settings into the Database
Server
In
previous versions, Shortcut Pane and user grid settings are stored in the
USERS\ directory of the AccountMate (e.g. c:\amsql\) folder. Shortcut Pane
settings are saved into UserShtp.DBF files while the user grid settings are
stored in UserGrid.DBF. If AccountMate is installed and run locally on each
workstation instead of a file server, the settings will only apply to the
specific workstation. Users must define shortcuts and grid settings on each
workstation where they expect to run AccountMate or copy the setting files
across computers, making the setup process tedious and time-consuming.
In this version release, users are given the choice of saving the Shortcut Pane
and user grid settings into either the database server or the application
folder.
Users whose application files are installed in individual workstations and
those who are running AccountMate via remote connection (e.g. through terminal
servers) will benefit from storing their preferences in the database server as
this allows them to see the same shortcut and grid settings no matter where
they run AccountMate. For users who are running AccountMate from a file server
(mapped drive over the network), the application will be more efficient if user
preferences are stored locally in the application folder.
View Function Access Rights and Function Access Rights Listing
Display Payroll Module Functions
In
previous versions, Payroll module functions are not displayed when users
run the View Function Access Rights and the Function Access Rights
Listing functions. This makes it difficult for administrators to review all
the access rights assigned to groups and users.
Version
7.3 now displays all menu options in the list as long as access rights are
assigned to the group or user.
New User Security Setting to "Enable Office Applications in
Toolbar"
Version
7.3 includes a new user security setting that controls access to the shortcut
buttons for Windows Explorer, Internet Explorer, Microsoft Word, Excel, and
Outlook in the Power Toolbar. The applications must be installed and “Enable
Office Applications in Toolbar” must be marked in the Edit User function window for the shortcut buttons to be accessible
to the user. By default, the “Enable Office Applications in Toolbar” is marked
in User Setup. Those who do not have the requisite access rights will not be
able to click on these shortcut buttons; instead, they will see “No access
rights in…” when they move the mouse over these shortcut buttons. This security
setting also controls the user’s ability to change the AccountMate system date.
Compatibility with Office 2007
This
version release is also compatible with Office 2007. Recently accessed document
files can now be detected and correctly displayed in the Power Toolbar and
Shortcut Pane.
Notepad (Eedt Visual Class) Limitation Set to 65,000 Characters
In
previous versions, the Notepad (Eedt visual class) limits data entry to
a maximum of 15,000 characters only.
In
this version release, the system is enhanced to allow input of up to 65,000
characters. This gives users more room to enter important, non-financial
information that they need in their operations. This limitation is based on
Visual FoxPro’s limitation on SQL updates.
Updates for Payroll Tax Subscription Not Included
In
earlier versions, updates to certain functions (i.e. transactions, reports, and
maintenance) for Payroll Tax changes were sometimes released with the
AccountMate CD.
Starting with version 7.3, updates for Payroll Tax Subscription-related
functions are no longer included in the CD. Any changes to these functions will
be included in the downloadable Payroll Tax Subscription program. This is to
ensure that all Payroll Tax updates are compatible with the version installed
in AccountMate. This also simplifies the maintenance and implementation of
Payroll Tax Updates as the same update program can now be run with the
AccountMate SQL, Express and LAN (i.e. Upgraded PR in build LN603 or higher)
versions. Since the Payroll Tax Subscription files are updated more frequently
than builds are released, this change also helps ensure that users receive updated
tax tables much sooner.
A Payroll Tax Subscription Build # field is added to AccountMate’s system
information to keep track of the version of the Payroll Tax file installed.
This information can be found in the About AccountMate function accessed
from the Help menu. When the system detects that a newer version is
installed, the database server is instantly updated with the changes.
Report
files are also installed in the TaxSub folder. The system will look for
Payroll Tax report files in the following AccountMate folders in this order:
RptMod, TaxSub, Patches, and Crystal.
NPC.EXE is No Longer Distributed with the AccountMate CD
Starting
with version 7.3, the NPC.EXE file is no longer distributed with the
AccountMate CD. Users who process electronic payment through National
Payment Corporation will be prompted with the following message:
“Missing the Transmission Manager
provided by National Payment Corporation. Please download at http://www.nationalpayment.com/support/csdownloads.html“
Rename of Setup Configuration File
The
optional AccountMate Setup Configuration File AMSETUP.ACF (located in the
application folder) has been renamed to AMSETUP.AM in this version release to
avoid confusion with the Microsoft Agent Character File, which also has the
.ACF file extension and is associated with a special icon in Windows Explorer.
Until
version 7.2, only very few installations have used this Setup Configuration
File to simplify the initial configuration process. In version 7.3, AccountMate
has been enhanced to utilize the settings specified in this configuration file
each time the application is accessed.
Hardware/Software Requirements
|
Before
installing a demo or live copy of AccountMate 7 for SQL, verify that the
servers and workstations meet the hardware and software requirements for
installing and running AccountMate. Note: Actual requirements may vary based on the operating system and database
used in each installation. Provisions must also be made for any additional
applications and files installed with AccountMate. |
|||||||||||||||||
|
Recommended Hardware Configurations
|
|||||||||||||||||
|
Database Server Requirements: |
|||||||||||||||||
|
The database server should meet the following minimum requirements: |
|||||||||||||||||
|
CPU: |
Pentium III |
||||||||||||||||
|
Memory: |
512 MB |
||||||||||||||||
|
Hard Drive: |
5.0 GB Free Space |
||||||||||||||||
|
Operating System: |
Windows Server 2003 Standard Edition (SP1) or |
||||||||||||||||
|
|
Windows Server 2003 |
||||||||||||||||
|
|
Windows 2000 Server (SP4) or |
||||||||||||||||
|
|
Windows 2000 Advanced Server (SP4) or |
||||||||||||||||
|
|
Windows Small Business Server 2003 (SP1) |
||||||||||||||||
|
Database: |
Microsoft SQL Server 2005 Standard Edition (SP1) or |
||||||||||||||||
|
|
Microsoft SQL Server 2005 |
||||||||||||||||
|
|
Microsoft SQL Server 2005 Workgroup Edition (SP1) or |
||||||||||||||||
|
|
Microsoft SQL Server 2005 Express Edition (SP1)* or |
||||||||||||||||
|
|
Microsoft SQL Server 2000 Standard Edition (SP4) or |
||||||||||||||||
|
|
Microsoft SQL Server 2000 |
||||||||||||||||
|
|
|||||||||||||||||
|
*For Microsoft SQL Server 2005 Express Edition users only:
Before you install SQL Server 2005 Express Edition, you must install the .NET
Framework 2.0. To download .NET Framework 2.0 and view information on other
system requirements for SQL Server 2005 Express Edition, visit http://msdn.microsoft.com/vstudio/express/sql/download/. |
|||||||||||||||||
|
File Server Requirements (Optional): |
|
|
A File Server is optional but recommended to enhance
performance. You can install the AccountMate 7 for SQL application on a file
server and map all workstations to it, freeing up resources on the database
server to obtain optimum performance on its data processing duties. Note: Under this setup, you do not need to
install the AccountMate 7 for SQL application on each workstation. You only
need to install the run-time library on each workstation. To do this, select
the "Compact" installation type when running the program installer
(AccountMate CD). Each
application server must meet the following minimum requirements: |
|
|
CPU: |
Pentium III |
|
Memory: |
512 MB |
|
Hard Drive: |
1.0 GB Free Space |
|
Operating System: |
Windows Server 2003 Standard Edition (SP1) or |
|
Windows Server 2003 |
|
|
Windows 2000 Server (SP4) or |
|
|
Windows 2000 Advanced Server (SP4) or |
|
|
Windows Small Business Server 2003 (SP1) |
|
|
|
|
|
Workstation Requirements: |
|
|
Each workstation that will be connected to the database server
must meet the following minimum requirements: |
|
|
CPU: |
Pentium III |
|
Memory: |
256 MB |
|
Hard Drive: |
1.0 GB Free Space |
|
Operating System: |
Windows XP Professional (SP2)** or |
|
Windows 2000 Professional (SP4) |
|
|
|
Windows |
|
**For XP SP2 users only: If you have enabled Windows Firewall,
contact your IT administrator for proper configuration to enable incoming
network connections. |
|
|
|
|
|
Note: Please consult your AccountMate Reseller
or System Administrator to confirm the optimal configuration to suit your
specific needs. |
|
|
|
|
Additional Software Requirements for Modification (Optional)
·
Visual FoxPro 9.0 (SP1)
·
·
Microsoft SQL Server 2005 or 2000 Utilities
Installation Guide
Pre-installation Checklist
Use
the following checklist as a guide when installing a live copy of AccountMate 7
for SQL:
1.
Verify compliance with the System Requirements.
2. Install Microsoft SQL
Server if you have not previously done so. Be sure to select the Mixed
Mode setting in order to support both SQL and NT Authentication. After
installing Microsoft SQL Server, be sure to reboot the database server to start
the SQL Server Service.
3.
Verify that you have administrative rights to the computer where
you are installing a live copy of AccountMate 7; otherwise, the VFP run-time
libraries and Crystal Report drivers in the Windows folder will not be properly
registered.
4. Exit all Windows
programs before starting the installation.
Quick Install Guide
1.
Insert the AccountMate CD into your CD-ROM drive to
automatically start the installation. If the installer program does not start
automatically, double-click Setup.exe in the AccountMate CD to display the
AccountMate Setup window.
2. Click Next to display
the License Agreement window. Read and accept the License Agreement; then,
click Next to proceed.
3. View the AccountMate
7 for SQL ReadMe in the Information window; then, click Next to proceed.
4. In the Choose
Destination Location window, perform either one of these steps:
|
4.1. |
|
Accept the default destination folder; or |
|
4.2. |
|
Select a different destination folder by clicking the Browse
button to open a Choose Folder window; then, select the folder where you want
to install the AccountMate program. |
5. Click Next to proceed
to the Setup Type window. Select from the following installation types:
|
5.1. |
|
Typical - installs AccountMate program files (application)
into the destination folder and the run-time library in your local workstation;
recommended for Client installations that run the AccountMate program locally
on each computer |
|
5.2. |
|
Compact - installs run-time files in your local workstation;
recommended for Workstation installations that run the AccountMate program
from a mapped folder to a file server |
|
5.3. |
|
Custom - gives users the option to enter the AccountMate
product key and select the components to be installed; recommended for File
Server installations |
6. If you chose Custom
Setup, the installer will display the Product Key window; otherwise, proceed to
step 10.
7. In the Product Key
window, enter the 25-character AccountMate Product Key that was supplied to you
upon purchase of the software. If the product key you enter is invalid, the
software will not be installed. If you have problems with your Product Key,
contact your AccountMate Reseller or AccountMate Customer Service.
8. Click Next to proceed
to the Select Components window.
9. In the Select
Components window, choose from among the following components to install:
|
9.1. |
|
Program Files - includes all AccountMate executable files that
allow you to run the main AccountMate program and all its functions and
reports |
|
9.2. |
|
Administrator Program - installs the Administrator program
needed to activate the AccountMate modules, install license file, create
companies in AccountMate, and manage group and user access rights among other
functions |
|
9.3. |
|
Run-time Files - installs the Visual FoxPro, Crystal Reports
and other run-time libraries necessary to run AccountMate functions and
reports |
|
9.4. |
|
Source Code - includes all source code modules purchased. The
installer will list the modules for which you purchased source code; mark the
checkbox beside each module listed to install the source code files into the
specified destination folder. Access to this option and the selection of
modules shown will depend on the AccountMate Product Key you entered. |
|
|
||
10.
Click Next to proceed to the Select Program Folder window.
Accept the default or define your own program folder name.
11. Click Next to start
the installation. When the installation is complete, click Finish to exit the
AccountMate Setup.
12. To create the system
and sample company databases, you must first launch the AccountMate
Administrator program either from your desktop or from the AccountMate program
folder.
|
12.1. |
|
Specify the name of the SQL server instance to which
AccountMate will connect. |
|
12.2. |
|
When prompted for the supervisor password, enter the default
password “go.” |
|
12.3. |
|
In the Select Country Tax for Sample Company window select
from the drop down list the desired country tax for the sample company. |
|
12.4. |
|
Specify the SQL Server data directory where you want to store
the AccountMate databases. Accept the default or select a different SQL data
directory. |
|
12.5. |
|
If the SQL server is installed in another computer, specify in
the Mapped as Directory field the drive letter and the shared network folder
to which you mapped the physical location on the database server where the
AccountMate databases will be stored. If you are physically running
AccountMate at the same computer where the SQL server data directory is
located, the Mapped as directory should be the same as the SQL server data
directory. |
|
12.6. |
|
Click the Install button; when you see a message asking you to
confirm whether you are ready to proceed with the installation, click Yes to
start the creation of the system and sample company databases. |
|
12.7. |
|
When shown a message stating that the installation of the
system and sample company databases is complete, click OK. |
13. In the AccountMate
Administrator program, perform the following:
|
13.1. |
|
Verify or enter the AccountMate Product Key and activate the
modules you want to use. |
|
13.2. |
|
Install the License File, input the Maintenance Key and, if
applicable, the PR Tax Subscription Key. |
|
13.3. |
|
Create the live company database(s). |
|
13.4. |
|
Define password policy. |
|
13.5. |
|
Set up groups and users, and assign access rights. |
14.
Launch the AccountMate application and log in with the user name
and password that you set up through the AccountMate Administrator program.
© Copyright 2007 AccountMate Software
Corporation. All rights reserved.
AccountMate® is a registered trademark of AccountMate Software Corporation.
Site
Map • Legal
Notices and Terms of Use • Privacy Statement • Website Feedback