Hi Ken,

VFP is more than capable for what you are asking - try hundreds of users simultaneously accessing tables with millions of records.

Unlike SQL Server, the VFP data engine is not a server. I suggest you read up on the subject concerning client-server technologies so you can make a better judgement. You should also read up on COM and multi-tier development to gain an understanding of apartment model threading and how it not only applies to VFP, but to VB as well.

As far as I see, you main problem is using VB as a front end. VB lacks the language datacentricity and the controls for binding to VFP cursors. While your at it, you should also read up on ADO and how to create record sets from VFP cusors.


>Hello- my name is Ken Busse,
>I am currently looking at using Visual Foxpro with small tables (40 to 70 records with not more than 20 fields - char type fields not over 4 characters in width) with a Visual Basic front end. Will this be over taxing Foxpro if I have as many as 80 clients accessing simultaneously on a local network. I have read on the Foxpro web site that the new service pack for Foxpro 6 is multithreaded. Will this help or is Foxpro just not capable of client-server usage at this level? Transaction usage and logging will not be used.
>
>Any input will be much appreciated,
>Ken Busse