INTRODUCTION:
Solutions Construction Inc. can provide various configuration options for Compufleet. Compufleet is written using Microsoft Accessâ. It is written in a client-server architecture. This paradigm involves separating the data from the application. Since we do this it is possible to upsize the database engine and keep the existing front end. An example is that if you already have a SQL Server database and want to use the power of it we could upsize the Compufleet database and still use the existing front end, thus keeping the same look and feel of the application. Compufleet can also integrate with an Oracle database.
Our recommendation for small, medium and even some larger fleets is to use Compufleet with the Access backend. Then upsize if you find that performance is a problem. Access can handle up to 64 simultaneous users and table sizes up to 1 million rows. (Actual number varies based on machine). Compufleet was written with design flexibility in mind. We created a software package that is affordable as well as scalable. Solutions Construction will help you design and configure a Compufleet solution that will meet your needs but performance and financial. Below are some possible configurations.
Simple Mobile Configuration (FIGURE 1)
Hardware needed:
1 PC (for in the shop)
1 or more Laptops
Networking Cables
Network Hub or switch
Configuration:
Both the Laptop and the PC would be installed with a customized version of Compufleet. This version would be using Microsoft Access’sâ Replication. Replication will allow the synchronization between the two databases. Each computer will have to have network cards and be configured to have peer to peer communication (networking software is included in all Windows versions). The PC will be configured as the Master and the laptop will be a replica. Before going out to a jobsite The Laptop would be synchronized with the Master (utility included in the software makes this a simple process). After the two are synchronized data can be entered and updated in both systems, both at the jobsite and at the shop. When the laptop is returned to the shop it will be plugged back into the network and re-synced with the Master PC. This can be done with more than one laptop. But the more laptops the more the chances for conflicts arise (See below)
Complications with replication:
If the same data is changed on both machines between being synced there will arise a conflict when syncing the two applications. Where this would come into play the most would be in updating the inventory. If you are the same part out of inventory while at the site as well as at the shop there will be a discrepancy. The replication wizard will guide you through steps to reconcile the data. Synchronization must occur regularly. The longer time between synchronization the more likely there will be conflicts.
If this is going to be a
major problem or you may not have the staff available to resolve the conflicts
Solutions Construction can work with you to come up with a solution that will
minimize the need for conflict resolution.
Mobile Configuration with Dialup(FIGURE 2)
Hardware needed:
1 Server PC (for in the shop)
1 or more Laptops
Networking Cables (Optional)
Network Hub or switch (Optional)
Dedicated Phone line
Configuration:
Both the Laptop and the PC would be installed with a customized version of Compufleet. This version would be using Microsoft Access’sâ Replication. Replication will allow the synchronization between the databases. The PC will be configured as the Master and each laptop will be a replica. The PC will also need to be running some type of RAS (Remote Access Service) software. This is included in Windows 2000 server, Windows NT Server, or Windows XP Server. The Laptop would be synchronized with the Master (utility included in the software makes this a simple process). Then the laptops will have the same data as the server. When synchronization is required the laptop will dial back to the server. Then using the same utility as before you would synchronize the laptop with the server. This can be done with multiple laptops at multiple locations. But the more laptops the more the chances for conflicts arise (See below)
Complications with replication:
If the same data is changed on both machines between being synced there will arise a conflict when syncing the two applications. Where this would come into play the most would be in updating the inventory. If you are the same part out of inventory while at the site as well as at the shop there will be a discrepancy. The replication wizard will guide you through steps to reconcile the data. Synchronization must occur regularly. The longer time between synchronization the more likely there will be conflicts.
In the dialup scenario the whole issue of Conflicts can be resolved. If you dial up then synchronize before you make any changes then synchronize after you enter the data the chance of any conflict will be greatly reduced.
Client Server Model (Figure 3)
Hardware needed:
1 Server PC (for in the shop)
Network PC’s
Network Cables
Network Hub or switch
Configuration:
This would be the case in which you have one or more PC’s in the shop and or office. You will have a main file server that all of the PC’s would connect to. This server would be required to have Server software . This is included in Windows 2000 server, Windows NT Server, or Windows XP Server. The PC’s would need to have Windows software with networking software installed. This is included any Windows 95 and above. The PC’s would all be loaded with a custom version of Compufleet. This version would use the server for all data. Users would be able to work on Compufleet as if it were on their PC. There would be no need for synchronization. As all of the data would be residing on the server.