>>We ain't picky! Naw! (s)
>>
>>One thing I have noticed is just standard performane in memory upgrades. Everyone I have talked to has seen a big difference & develops with 24 to 32 Megs or more of memory (32+). None of the people I chat with have 16 Megs or less of RAM, the speed is that different. I could possibley see where speed is not noticed with SCSI when RAM is increased because of throughput. A large number of people I know use EIDE because SCSI is just too outrageous ($). For the pice of a 2 Gig SCSI they can get between 4 & 6 Gigs of EIDE.
>>
>>Of course other 'normal' optimizations are assumed. I totally agree, get respectable speed & move on. Too much to do to get too technical.
>>
>>I see some VERY good benifets with PCI LAN adapters and some other performance boost with a 512k pipeline burst cache (intead of 256k). The cache is really quite economical too.
>>
>>HTH,
>>Tom
>
>Just to let you all know, I've since tried a test using a different PC as the server, 32MB RAM, 1GB IDE Disk Drive. The client PC had 16MB RAM and also a 1GB IDE Disk Drive. The query did perform better, but still quite different from when I run it locally. Locally takes 15 seconds, Using the PC with 16MB RAM as server, it takes 3 minutes, and using the 32MB RAM PC as server, it takes 2 minutes. Am I correct in having TMPFILES on the local drive? Perhaps, one of the limiting factors here is the Peer-to-Peer network. Has anyone used FoxPro on this type of network? Thanks for all input.

Martha

I run ALL my VFP development via the Server. You are correct on the Tmp files.

Run the query & then run to the Hub. See if the Collision light is blinking. If so then it is a network problem. Collisions will bring you to a crawl if there are many of them. One thing you can do is re-load the NIC driver. Sometimes that will help.

My 2 cents is to have a PCI LAN adapter on at least the server. We have seen impressive reults when you do. IMO, all high traffic PC's should have a PCI (if not all PC's).

HTH,
Tom