The multi-user (or network) version of ABC6 allows up to 26 users to access ABC Accounts at the same time.
Upgrading from the single-user ABC is simple, quick, and does not affect any existing data.
Some of our larger clients have used multi-user ABC6 for years, producing hundreds of invoices a week. It has proven to be robust and reliable.
It works with any standard PCs running Windows (7,8,10), and does not require a dedicated server computer (ie. the server can also be used as a normal workstation).
It is supplied with a Network User Manual which you can read here.
ABC uses the Microsoft JET database engine to save and retrieve data. The data is stored in the .MDB file located on the computer we call the "server". This is not a true server because the .MDB is not an active database controller; it is simply a file of data. Sometimes called a File Server database.
The work of selecting and processing data is done locally on each PC by its own copy of the JET database engine controlled by ABC. If ABC requests even a single record from a file, the JET engine may have to bring the entire file across the network to the local PC in order to work on it to select the one record. If the file is large this could be slow (it depends on the speed of the network connection).
It might seem that using a proper active server is a much better system (and it can be -- for LARGE databases with thousands of users), but it isn't a simple comparison. For various reasons this can actually be slower than the simple File Server used by ABC (eg. JET is very efficient at caching data so often only the first request needs to use the network; also an active server may be busy dealing with other requests or internal housekeeping leading to delays in processing your request).
Conclusion. We keep checking, but at present the system used by ABC is still regarded as the best solution for up to 200 users, and databases less than 2GB in size. With fast network connections, there should be little speed difference between a single-user ABC and a multi-user system.
To investigate factors influencing network speed we used 3 computers, Windows 10 , Windows 7, and XP. Connected together first with WiFi, and then cable. Tried each PC in turn as the "server". Testing done with a large ABC database (150Mb, approx 200,000 Sales Transactions).
Summary of Results
There was not much difference between any of the computers (ie. using XP as server or Win10).
Workstation PC's connected by cable run ABC faster and more reliably than those connected by WiFi (although WiFi worked well for us. But in areas suffering radio interference, cable is much better).
Here are some suggestions from people who had slow network response using MS ACCESS (based on JET engine) and who said one or other of these speeded it up for them.
NOTE: TRY THESE AT YOUR OWN RISK. We tried them all and did not notice a dramatic speed increase.
1. Increase buffer size for database connections by changing Registry settings. For both the following, change MaxBufferSize to 50000 (decimal). (on your PC, some numbers may be slightly different, eg Office 12 instead of 14)
32 bit Windows
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Access Connectivity Engine\Engines\ACE]
64 bit Windows
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Jet 4.0] [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Access Connectivity Engine\Engines\ACE]
2. Possible conflict between IPv6 and IPv4 in the TCP settings of the network card using Win7. Go into the properties of your NIC card and untick the box Internet Protocol Version 6 (tcp/IPv6)
3. Temporarily disable antivirus or firewalls from actively protecting the network location where the database file is. If it makes a difference, you can look at configuring the security software to avoid the delays.