Hi Richard:

VFP is not dual proc aware, so VFP will not see a second processor.

First, I want to suggest some VFP specific ideas:

1.    Optimize the code using the Coverage Profiler:
191953 How To Use Coverage Profiler to Optimize App Performance
http://support.microsoft.com/?id=191953

2. Optimized an SELECT-SQL commands using the SYS(3054) function:
248608 INFO: SQL SELECT Optimization Levels and Performance
http://support.microsoft.com/?id=248608
156551 How To Use SYS(3054) to Optimize a Query
http://support.microsoft.com/?id=156551

3. Optimize VFP internal memory usage when handling data with the SYS(3050)
function:
176483 PRB: Large Amounts of RAM Seem to Process Data Slowly
http://support.microsoft.com/?id=176483

Remember, VFP is running in the workstation memory and not the server
unless you are using Terminal Services.  Adding a lot of RAM to the server
helps little. On the other hand, adding RAM to the workstations might help
depending on how much is currently installed. However, I would make sure
the VFP code is fully optimized before investing in additional hardware
upgrades.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/   

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
  http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
  http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
  - VFP5 Mainstream Support retired June 30th, 2003
  - VFP6 Mainstream Support retired Sept. 30th, 2003

I assume the program will run on the workstations, and the server is
only used as a fileserver. Then your task is first to find out whether
the bottleneck is your current server or the network.
If the program is not developed with a network in mind it may shift
HUGE amounts of data over the network, making any optimisation of
either the server or the workstations a complete waste of money.

Therefore you first have to check the performance on the old server,
like how much CPU is used, how much network traffic is generated, how
much disk reads/writes does it do, etc
Windows sbs has some nice performance measure programs built in, so
you can use these to get a base figure.

Richard -
take a look at
http://fox.wikis.com/wc.dll?Wiki~TuneFox~VFP
and see if you can apply any of the techniques there on your 'current'
server.
make some benchmarks ...
SBS takes a LOT MORE O/S TWEAKING for file-based DB's such as VFP.
hth - mondo regards [Bill]
--
William Sanders / Electronic Filing Group  Remove the DOT BOB to reply via
email.
Mondo Cool TeleCom -> http://www.efgroup.net/efgcog.html
Mondo Cool WebHosting -> http://www.efgroup.net/efglunar.html
Mondo Cool Satellites -> http://www.efgroup.net/sat
VFP Webhosting? You BET! -> http://efgroup.net/vfpwebhosting
mySql / VFP / MS-SQL

If you are using workstations, and loading the application from the server,
and running the application on the workstations, storing the data on the
server - then the CPU in the server isn't going to help much.

Because it's a SBS server, there are likely to be other processes running,
and configuration options set, such that it is a compromise between the
speed of serving up the file access used by the workstations and everything
else that the server is expected to do.
So I think in your case having more than one CPU and more memory in the
server is going to benefit the applications it's running (but not your VFP
app directly) and the services it's providing - which includes the file
server functions that do affect your VFP app performance.

Disk is a bottleneck, as is LAN speed, and in your case the other processes
hte server is running. Because VFP isn't a client-server system, when you
access a table from the workstation you will open the table and index across
the network.
There are various techniques to speed up an application written in VFP, but
I'd suggest first you try to find out why it's not performing as fast as
you'd like.

BUT in all this I've made a lot of assumptions about how your application
works, and how you use it.