>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

Visual Foxpro would be perfect for this job, but it would work out better with a VFP front end. While there is a VFP ODBC driver, VFP tables were not built primarily for Client Server access.

The new mutlithreaded feature refers only to the Multithreaded COM servers tht oyu can build with VFP. These are prmarily meant for running under MTS, and in oyur situation, might be a prime candidate for exploration. If you want to use VFP on the backend, and VB on the front-end, I would look at building VFP middle tier components to access the data and return ADO recordsets to the VB front-end.