Cadzow Knowledgebase

Contact Us

Site Search

Remote Support

Print Friendly

Cadzow 2000 System Requirements

Note: these are draft specifications for the Access 2007-based version of Cadzow 2000 which will be released in 2008.

Executive Summary

  • Cadzow 2000 requires a server and a number of workstations. However, one machine could be both a server and a workstation.

  • The server needs to be Windows NT 4.0 (or better) running Microsoft SQL Server 7.0 (or better) — or — Windows 2000 (or better) with SQL Server 2005 Express Edition and Microsoft .NET Framework 2.0.

  • Workstations need to be Windows XP Service Pack 2 or better.

  • If you have an existing machine, check “Minimum Configuration” below to ensure it is capable of running Cadzow 2000.

  • If you plan to buy a new machine, check “Recommended Configuration” below to ensure your machine is suitable for Cadzow 2000 and its successors.

Database Technology

Although Cadzow 2000 supports both Jet (.MDB) and SQL Server databases, we no longer deploy new Cadzow 2000 databases using Jet. Sites which do not have a licence for Microsoft SQL Server can use SQL Server 2005 Express Edition, which is free and vastly superior to Jet .MDB files.

(NB. There is an enhanced version of SQL Server 2005 Express Edition called SQL Server 2005 Express Edition with Advanced Services; this version is not required for Cadzow 2000.)

Note that at least one user will need to be granted dbOwner privileges on the database as data updates (field/table changes) are performed by Cadzow 2000 when updates are loaded. This could be a special user account created for this purpose. Day-to-day operations do not require dbOwner rights.


Minimum Configuration

The following is the bare minimum specification. This configuration is only practical for users with a low volume:

  • Windows XP SP2/2003 SP1/Vista or later;
    (Windows XP Home and Windows Vista Home editions are not recommended except in standalone environments as they do not support Remote Desktop or domain networking.)

  • An Intel Pentium-based computer with 256Mb RAM;

  • 1Gb of available hard disk drive space;

  • Display adaptor and monitor capable of 800×600 (SuperVGA) and 256 colours;

  • 100Mbit network interface card (if networked); and

The following could be attached locally or shared over a network:

  • A printer capable of A4;

  • CD-ROM drive or Internet access to obtain installation files and updates;

  • Large capacity removable storage for backups (eg. external hard disk drive, ZIP drive, CD/DVD-writer or tape drives).

Recommended Configuration

As above except:

  • Windows XP SP2/2003/Vista or greater with latest service packs and security updates.

  • 32-bit Dual Core CPU.
    (Cadzow 2000 seems to run correctly on 64-bit Windows XP, but please consult us before embarking an any rollout of 64-bit hardware.)

  • Gigabit ethernet network adaptor.

    If using Windows Vista:

  • 2Gb RAM;

  • AGP graphics with 256Mb RAM;

  • 17″ TFT Display at 1024×768 or better;

  • 20Gb of available local hard disk space.

    If using Windows XP:

  • 512Mb RAM;

  • AGP graphics with 32Mb RAM;

  • 17″ TFT Display at 1024×768 or better;

  • 2Gb of available local hard disk space.

Email Requirements

  • MAPI-compliant email client (such as Microsoft Outlook 97 or greater); or

  • Microsoft Outlook Express/Windows Mail.

See Cadzow 2000 Email Support for full description of features and email systems supported.


Required server capacity varies greatly with usage.

If you are using Cadzow 2000 attached to a Microsoft Access database (.MDB) in a small workgroup LAN of 5 or so users, the server is simply the machine storing the data and typically you would choose the fastest machine with the most RAM, the most recent operating system and the most advanced file system. (For example, you would favour a Windows 2000 machine over a Windows 98 machine and choose NTFS over FAT.) From this point of view a machine as shown under Recommended Configuration is suitable.

If you are using Cadzow 2000 attached to an .MDB in a larger LAN, with dedicated file and print servers, most likely the capacity you have chosen to suit your other file serving will adequately handle the requests on the .MDB file also.

If you are using Cadzow 2000 attached to SQL Server, the system should start at 512Mb RAM with 1-2 processors. Larger systems will benefit from 1-2Gb RAM and 2-4 processors. Sizing SQL Server systems is quite complex and cannot be described simply.

Cadzow 2000 supports:

  • Microsoft SQL Server 7.0,

  • Microsoft SQL Server 2000, and

  • Microsoft SQL Server 2005.

All editions and service pack levels are supported, although using the latest service packs is recommended.

SQL Server 2000 requires at least Service Pack 3 on Windows Server 2003.

Remote Support

Cadzow provides remote support services for Cadzow 2000 users. Technologies supported are:

  • Windows XP Professional/Vista and later Remote Desktop and Windows 2000 (and later) Terminal Services;

  • VNC (Virtual Network Computing) implementations such as TightVNC or RealVNC.

Cadzow recommends that only Terminal Services be exposed over the Internet. pcAnywhere and VNC should not be exposed over the Internet. pcAnywhere is a good dial-in product (requiring a modem and a phone line) and VNC is a reasonable technology for workstations on the LAN behind the firewall. In all cases, these products should be used with the latest service packs and security patches installed, and should only be accessible with authentication.

What Cadzow 2000 Does Not Support

  • Microsoft SQL Server 6.5 or earlier.

  • Microsoft Data Engine (MSDE).

  • Pre-release (beta or release candidate) operating systems, service packs or SQL Server.

    In the event you experience a problem with Cadzow 2000 with a pre-release operating system, service pack or SQL Server, we are interested to hear about it so we can investigate in time for the final release of that product. However, the likelihood is that the problem will be fixed in the final release and there will be little we can do about it in the interim. Most likely we will advise you to uninstall the pre-release code or use released code.

  • Wireless LAN connections.

    Wireless connections are highly functional but nowhere near reliable enough for mission-critical database applications (such as Cadzow 2000). Database applications assume constant connections to the data source, and dropouts are not handled elegantly. This is a common trait of all database applications, not just Cadzow 2000. Wireless connections are excellent for email and web browsing.

    However, if you are using a wireless connection to access a Terminal Services or pcAnywhere session running Cadzow 2000, this is fine, because the database is local to the host and not being transmitted over the wireless connection.

  • Non-Microsoft Windows storage/file servers.

Copyright © 1996-2023 Cadzow TECH Pty. Ltd. All rights reserved.
Information and prices contained in this website may change without notice. Terms of use.

Question/comment about this page? Please email