Also, CDA versions 8.5 or higher  will no longer offer full support for Windows98.  There are some new communications features that require Windows 2000 or higher.

Another possible cause for slow response could be your Anti-Virus software.  Some AV software, such as Norton's, have an Auto Protect feature that remains resident checking all files that are being open on the computer.  We recommend disabling this feature.  You are still fully protected through email control and if you are on a broadband connection, you will have additional firewall protection as well.

Under proper installation and configuration, the CDA Service Manager software will perform as expected.  Please contact our Technical Support team if you need help to correct this problem.

The first approach to working with data corruption would be as follows . . .

1.  Make sure everyone is completely logged out of CDA.

2.  Make a current backup of your CDASERV folder on your server.

3.  Open CDA on one computer and select to RE-Build Database Structures from the Utility Menu.

4.  When the Re-Build is completed, Re-Index All Files from the Utility Menu.

Next, check for unwanted Index files as follows . . .

Index files should ONLY be located in your CDASERV folder on your server.  When data base files become corrupt, it is possible that some index files were written to the local C:\CDAWIN folder if the RE-Index procedure was run from a workstation.  Check each of your workstation's C:\CDAWIN folder for files having an .NTX extension.  For CDA versions 8.5c and older, there should not be any files with an NTX extension so please remove any found.  For CDA versions 8.5d and newer, there should only be two files and they are "JOBSLOG.NTX" and "JOBSDATE.NTX".  Please remove any other files found with an NTX extension..

Finally, if you have History files,  look in your History Default folder for files having an .NTX extension.  There should be less than 10 all beginning with "HIS".  Example: HISNAME.NTX  

Be sure you have a Current and Valid  Backup of your History Files before proceeding

Remove any file with an .NTX extension that does not begin with "HIS"

If unwanted NTX files were found and removed, please run the re-indexing utility again.

If the problem still exists, contact our support team for assistance.

If for some reason you did not install the CDA Work Station in the default C:\CDAWIN folder or if you have installed multiple work stations on a Terminal Server using different folder names for each login account, please contact our technical support for instructions on adjusting the environment to support this.   

     1.  Open the Communications Menu.

     2.  Click on "CDA FTP SITE"

     3.  Click on the "CONNECT" button

     4.  Scroll down the "Remote File" list and locate "WOASSN.DBF"

     5.  Right Click on the file and Click "RECEIVE"

This will replace the damaged file.  Re-indexing is not necessary.

The following Technical Support link will address the proper installation of  CDA Service Manager workstation clients Version 8.6 or later using  MS Terminal Server.  The CDA Server software must be installed on the Terminal Server prior to installing the workstation software.

Technical Support Release 03 

This installation only supports CDA Service Manager version 8.6 or later.  If you are using MS Terminal Server Client and an older version of CDA, you must upgrade.  Please Contact Us for upgrade information.

 If you need additional help setting up environment variables on your TS server, please consult your network administrator. 

The CDA server computer shares the data files with all of the clients.  Therefore network traffic can be extremely high with a lot of CDA work stations requesting data.  The speed of your network cards, hubs, and other network related hardware is also very important. 

Regular maintenance is also required to keep the performance maximized.   Your CDA Data files should be re-indexed every day.  We suggest setting up a scheduled task to handle this using the CDAINDEX.EXE file located in your server's CDASERV folder.  It is also very important to make sure that all users are out of CDA while re-indexing.  If CDA data files are open, the indexing will not complete.  CDA support will be happy to help you set this up.

As time passes, your CDA data files are growing in size. Oversized data files will have an effect on performance as well.  There are various methods provided in the CDA software to help you manage this.  First, the work order file should be archived at the end of each fiscal year.  This moves all of the PAID-IN-FULL work orders from the main data file into an archived data file.  Once archived, the work orders can be located through the HISTORY menu.  The archived records are only available to view.  You will not be able to include these records in reports.  However, you will  be able to restore a record back to the active data file if needed.

Another file that should be purged on a regular basis is the Purchase Order data file.  There is a selection in the Purchase Order menu to handle this.  This procedure will only remove purchase orders that have been completely filled and no longer need to be in this file.

Also, the CDA Scheduler should be purged on a regular basis.  After the scheduled day has passed, the system no longer needs to track the data.  Old data will slow the Scheduler down quickly, so keep it purged.

If you have a large service center with 20+ work stations we recommend moving to a TS server using remote desktop work stations.  This environment removes the excessive network traffic because all the processing is done on the server.  With a powerful server and the proper configuration, you will not experience any performance issues.

The CDA Service Manager software is a very large and powerful data base management program developed to provide all the functions to handle a demanding service business.  Your hardware and network must be good enough to take advantage of all the CDA's capabilities.

Please contact CDA technical support if you need assistance with this feature.

CDA doesn't know where scanners are or how they're connected, it just enumerates the TWAIN drivers it finds on the local computer.  To make any scanner appear in the TWAIN device list, there has to be a locally installed TWAIN driver for that scanner.  Most network scanners have a remote TWAIN driver that you can install on a client PC.  For example, Canon has a driver called Network ScanGear that works with their ImageRunner models.  Xerox, Fujitsu, Ricoh also have something like this.  There are also 3rd Party products available that makes any TWAIN scanner sharable across a network.  Search the web for "Remote Scanning Software".