I have 2 user system, and a large datafile (50 meg+) that as histories for gas customers. The updates and customer view is slow on the second system. The data sgets corrupted quit aften and I must rebuild. Any sugestions or fixex?
John
We had a similar problem and found the defragging the hard drive of the host computer stopped it. I also deleted a lot of unnecessary files from the host PC, then defragged the rest of the computers that are on the network. The problem has now all but disappeared.
Greg
But is the keyword. As long as you run QB on a peer to peer network you will have corruption problems. If you don't want to say But you have to run it in client server mode, and that means another computer running windows terminal services and a five user license pack.
The best you can do in peer to peer is get two matched fast computers, buy the highest quality network cable you can find, put them on their own high quality hub so as to minimize the data path between the machines. It's the best you can do for the problem, but [there is that word] you will be rebuilding the file from time to time, no matter what.
Terminal Server is definitely the way to go to solve both your corruption and performance problems. If you don't want to do that, at the very least, make sure that you have UPSs on all of your computers and networking gear.
Mike Schumann
So in the words of a famous Australian, "please explain"? We have five computers all using qb 2005/2006. One holds the data file and all the rest link to that data file. Could you either point me to a link to set it up for windows terminal server or explain gently on whats required.
Greg
Okay. This is an overview of what we are talking about.
Your users open a terminal service session on the server and run QB. As the only data going between them and the server is the keyboard, mouse and screen, it is incredibly faster that the multi megabytes that QB sends in a peer to peer configuration.
If you have a resonably smart IT type, he sould be able to tune the disc cache and system parameters to speed up QB even further on the server system.
Terminal Server is also standard in Windows 2003 Server (regular edition, not Small Business).
Mike Schumann
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.