>
>>Is this for the webserver piece, the appserver, the database server, or some combination?
>>That will impact many of my answers. But a few general notes in-line that will apply in any case....
>
>The server will house everything. The ASPX pages, the COM components and the VFP tables.
>

In that case, I would go with as much RAM as possible. A gig sounds like a lot, sure, but right now, my home machine has a gig. For a server, a few hundred extra dollars to max out on RAM sounds like a very good investment to me.

I have not worked with an n-tier app using VFP tables, but in the cases where I have worked with VFP components against SQL Server data, dual processors and even dual hard drives have proven to be good things. Will you be loading the components under COM+? If so, a dual processor is a very good thing. With SQL Server machines, I have seen huge performance boosts by using two physical drives and loading the transaction log on one and the actual data file on the other (I could get into the reasons why if you care but its kinda OT). I could imagine that under your scenario, there might be some benefit to loading the data on one drive and the components on another. But, I will defer to the judgement of those with empirical evidence rather than my morning rants... :)