>We are trying to get feedback as far as the maximum number of concurrent users that can be supported by the VFP database engine in a real-world application.

Many moons ago (1994? 1995?) there was a thread on Compuserve about 250 users in m/u environment. Christian Broadcasting (the home of many Fox alum, including Dick Whetstone) ran a huge (for FPW) app - something like 10 million records - and think of the hardware it was running on back then... Reindexing this thing took about a day.

They had serious issues (as did many of us) with indexes getting corrupted in a many user m/u environment. To combat this, as well as handle >200 users, they used an interesting technique that employed a posting engine that wrote to the main database files. Thus, users never saw the actual data tables - just temp tables - and evidently performance using this mechanism was acceptable.

Thus, > 200 users definitely can be done.

OTOH, given the work it would be to rewrite your app to do this, you might consider a bigger back end like S/S. It depends on your user requirements...

Whil