In the newsgroups, Jon Goldberg noticed a number of people having similar Peachtree network problems to his own, problems that could not be solved by Peachtree tech support's standard answers. This includes “lock table full” errors that persist after reboots and deleting the .lck files, “*.dat” file errors in the middle of a session, Error Number 35 in the middle of a session, and so forth. A Peachtree tech confirmed for him what he believed all along regarding Peachtree – it is designed for a single user, not a network, and any sort of network congestion will cause it to quit ungracefully, possibly resulting in database corruption. Moreover, Peachtree appears to have some sort of broadcasting mechanism that causes certain network configurations to create artificial network congestion, slowing down Peachtree and occasionally causing the above mentioned errors. In his case, the solution is to buy a network switch for about $100 to replace his hub. This eliminated his network problems, but also provided a significant speed boost to Peachtree over the network as well.