Now depending on what the Sales Data covers the answer varies. For pure performance having the data on each workstation will be faster with no network traffic involved, [b]But[/b] there is a down side with this.
If you are actually selling items and the DBase actually contains a listing of what is physically available you'll soon find yourself in a position of salespeople attempting to sell things that are not in stock even though it may say that they are on that particular workstation at the time there are several other salespeople who will be seeing exactly the same thing until their Local DBase get updated by which time the damage could have been done.
As an example lets say that you are selling swimming pools and you have a special on one type and you guarantee a completed install within 3 weeks. With a team of 12 sales people you could easily sell enough of these swimming pools that your installation staff could not possibly install the number sold within the specified time frame because each sales person is incentive driven they will make promises that appear to be capable of being kept according to their display but when you have 12 people doing exactly the same thing with the same data that isn't updated as they go along you could have the situation of needing enough staff to install 12 swimming pools within 3 weeks when your total install staff is only 8 people who can install 3 swimming pools in a 3 week period. That is only taking into account the sale of 1 swimming pool by each of the sales people per day. At the end of that day/time between updating the workstations the problem would be recognised and then someone would have to address it.
