See my inline comments
>We're getting ready to do a major upgrade here (from NT 4.0 Server to 2000 Server and Win 95 Clients to XP Prof. clients).
>
>We, of course, use a VFP app that requires a lot of data entry/retrieval throughout the day - as always - speed is essential. The app resides on the client while the data is on the server. We're not using SQL server - just plain old VFP. We're approaching 1 GB of data (861 MB to be exact).
>
>It would be great if some of you would offer suggestions as to how our network should be setup to acheive the best performance possible. Things like:
>
>How much benefit will we see (from VFP) with a two-processor server compared to a single processor?
The server
may benefit from multiple processors, but VFP doesn't use anything on the server unless you have COM components running there.
>How much RAM in the server?
I'm not qualified to answer that. It depends on a number of variables. An MCSE should be able to answer this.
>Would a seperate machine that would share the VFP data provide any benefit?
That depends. You should not use the same server for data and a Primary Domain Controller.
>Most of the activity is on the third floor, would placing an additional server there help?
Yup. Distance makes a difference.
>If we could have a seperate server to handle MS Exchange - would that help?
Absolutely. Exchange should be on its own server.
>
>Any other ideas would be appreciated. Thanks for your help!
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer