| How can I avoid 7040 and 7041 errors when printing forms and reports? |
A number of network users have complained about receiving 7040 and 7041 errors when printing GDI forms, client activity reports, and state/local wage reports. What each of these users had in common was that their shortcut to Account Ability referenced a network share containing periods (dots). IDMS researched such network shares and realized that share names containing periods resulted in a 7040 error or 7041 error whenever Account Ability attempted to print GDI forms or write to its TEMP folder.
Remedy: Modify your shortcut to use a UNC name.
Illustration
You installed the 2006 version of Account Ability in the folder
\\SERVER.ACCOUNTING.MAIN\APPS\ACCOUNTABILITY\2006
and decided to use the share name
F:=\\SERVER.ACCOUNTING.MAIN\APPS\ACCOUNTABILITY
on each user's workstation. Although the shortcut
F:\2006\AA2006.EXE
successfully launches the application, you are not able to print GDI forms, client activity reports, and state/local wage reports.
Solution
Modify the shortcut's target to the fully qualified UNC name,
\\SERVER.ACCOUNTING.MAIN\APPS\ACCOUNTABILITY\2006\AA2006.EXE |
 |
| Can I use Account Ability with a thin client and Microsoft Terminal Server? |
|
Yes. |
|
| I set up a local group for users of Account Ability. How do I grant this group administrative rights to the Account Ability installation folder? |
(a) Login as the Administrator on the PC that will do the sharing
(b) Browse to Account Ability's installation folder
(c) Right-click and select 'Properties' from the popup menu
(d) Click on the 'Security' tab
(e) Add the group to the 'Groups and user names'
(f) Assign 'Full Control' to the 'Permissions' for the group
NOTE: If the 'Security' tab is not displayed, you can display it as follows:
a) Open your system's 'Control Panel'
b) Switch to 'Classic View'
c) Select 'Folder Options'
d) Click on the 'View' tab
e) Under 'Advanced settings', clear Use simple file sharing |
|
| How do I set up a Local Group under Windows XP Professional? |
a) Open your system's 'Control Panel'
b) Switch to 'Classic View'
c) Select 'Administrative Tools'
d) Select 'Computer Management'
e) Open 'System Tools'
f) Open 'Local Users and Groups'
g) Click once on 'Groups'
h) From the 'Action' menu, select 'New Group'
Assign a group name (e.g. ACCOUNT ABILITY), Description, and 'Add' any members to the group. When done, click the 'Create' button.
NOTE: Once a group has been created, you can always return to this group to add or delete users. |
|
| How should I install Account Ability to a dedicated server? |
Server Installation
(a) Login to the server as the Administrator
(b) Install Account Ability to a path off of the root (e.g. \AA)
(c) Create a Local Group for users of Account Ability
(d) Add users to the Local Group created in (c) above
(e) Share the installation folder
(f) Assign the Local Group Administrative rights to the shared folder.
Concurrent User Installation
(a) Have each user browse to the installation folder on your server
(b) Open the client folder located within the installation folder
(c) Run the setup.exe command to install the concurrent user license
(d) This will create a shortcut to Account Ability on each user's desktop. |
|
| How should I install Account Ability on a Peer-To-Peer network? |
(a) Login as the Administrator on the PC that will do the sharing
(b) Install Account Ability to a path off of the root (e.g. \AA)
(c) Create a Local Group for users of Account Ability
(d) Add users to the Local Group created in (c) above
(e) Share the installation folder
(f) Assign the Local Group Administrative rights to the shared folder
(g) Install the Concurrent User Licenses on the remaining workstations. |
|
| Is there a way to use a mapped drived rather than a UNC path for Account Ability's database? |
The answer is yes, provided you are using version 15 or later. Although Account Ability automatically references the database by UNC path, you can change the path to a mapped drive. The following procedure should be followed by your network administrator.
Procedure:
a) Have all users exit Account Ability
b) Move the database to the desired shared folder on your mapped drive
c) Launch Account Ability
d) From the 'Module' menu, select 'Reallocate -> Account Ability's YYYY Database'
e) Browse to the database on the mapped drive and select 'Open'
f) Exit Account Ability
g) Locate the file ADS.INI in Account Ability's installation folder
h) Double-click ADS.INI and open it with NOTEPAD
i) Notice that Account Ability changed the mapped drive to a UNC path
j) Manually change the UNC path to the desired mapped drive
k) Save the ADS.INI file and restart Account Ability
l) From the 'Help' menu, select 'About Account Ability's Database'
m) Verify that the folder now uses a mapped drive.
IMPORTANT: It is essential that all users use the same mapped drive! Failure to do so can result in database conflicts, possibly database corruption. This is the primary reason Account Ability uses a unique UNC path rather than a mapped drive. |
|
