We recommend a dedicated file server. That is, a file server on which only the server software is run. There is extra cost involved in having a dedicated server but, if you are able to afford one, it is the best way to go.
For a dedicated file server you can choose between a Windows Server and Novell Netware (IntraNetware).
Note: QuickFill contains its own database management and does not require a database server such as Oracle or SQL Server. Read-only access to the database is available through a supplied ODBC driver.
If you have a large database (more than 100,000 customer records) a Windows Server has an advantage over Novell Netware—you can run QuickFill itself on the server. This allows you to run the updates on the server, with direct access to the database files, without having to transfer the data over the network. This is the only exception to the recommendation for a dedicated file server. Do not use the server for daily data entry.
If you are not able to afford a dedicated file server, then you will need to use a peer-to-peer network. The built-in networking software contained in Windows will work fine.
With a peer-to-peer network you need to be careful. If the computer on which the database resides crashes, you risk getting a corrupted database. Therefore, we recommend trying to minimize the amount of daily work (by other programs) that is done on the computer that holds the QuickFill database while QuickFill is being run.
For workstations, if you are buying new ones you will probably end up with Windows Vista or XP. Any of the various editions (Home, Business, Professional, etc.) are okay. If you use a Windows Server you should probably get the Business edition of Windows Vista or the Professional edition of Windows XP since the Home editions cannot join a domain (although they can still access all of the files on the server). If you use a Novell Server you should install Novell's client software. If you are using existing workstations, you may use Windows 98, Windows ME, Windows NT, Windows 2000, Windows XP or Windows Vista.
Note: using QuickFill on non-supported versions of the Windows operating system
Windows 95 is not supported. Windows 98, Windows ME and Windows NT will not be supported after June 2007.
If you are buying a new server buy as much memory as you can and the biggest, fastest hard disk(s) for the server that you can afford. When used in a server environment, SCSI disks are faster than IDE disks.
Note: Initially, your QuickFill database will need approximately 2.0 megabytes per 1,000 subscribers. Your needs will grow over time, depending on how much of the historical data you choose to purge.
To coordinate multiuser access to the database QuickFill uses a separate "lock manager" module that may be run on a Windows server (not a Novell server) or on any workstation on the network. The lock manager requires Netbios support, which is built in to the TCP/IP protocol and is readily installed for the IPX/SPX protocol. The computer running the lock manager must have protocols installed that match the protocols used by each workstation.
If you are buying new workstations, you should have a minimum of 128 megabytes to run Windows XP. Any new computer in current production will have more than adequate speed, although you might want to get one "souped up" workstation for the purpose of running the reports and updates.
QuickFill has been designed with a minimum screen resolution of 800x600. Your monitor must be capable of at least this resolution.
For backup hardware, we like Zip drives. CD and DVD recorders are also good, but QuickFill does not have the ability to write directly to a CD-R drive. QuickFill does contain a built-in database backup feature that works with removable random-access disk media, such as Zip disks. The backup files that QuickFill creates are standard PKZip files.
A backup system that runs automatically every night and backs up the entire server is all well and good, but you should also be able to backup just the QuickFill database during the day, on demand.