VFP will handle what you describe without any problems. Attention needs to be paid to the indexing of all files, and the design of your tables needs to follow the rules of normalization - but you probably already know that.

Outside of your application design, your focus needs to be on the integrity of your network, etc. Most problems with data corruption occur because of something that happens unexpectedly - like a power failure, etc. If you design your network with sufficient failsafes, you will see little to no problems with reliability after deployment.

You should also consider the needs of your application as far as bandwidth is concerned - if you are running on 10bt, you will not have the performance. So at least 100bt backbone with good equipment that is reliable will help with that.

Then you need to ensure that you have good hardware at the user's desk. High speed pentium based machines with 256mb + RAM will ensure that any local processing does not suffer when large queries are run.

hth
Wayne


>I need to build a medium sized application to process sales, production and shipping.
>
>It will support about 30 users, 100 screens to enter/maintain data, 20 major and 40 minor tables, 1000 to 2000 non-inquiry transactions daily.
>
>I would like to consider using the Foxpro database instead of a third party database.
>
>If you have recent experience in doing something like this, I would like to hear from you about your results including problems you had to overcome in designing and operational reliability after deployment.
>
>Kindest regards to anyone who can contribute.
>
>"Not all who wander are lost."
>- J.R.R. Tolkien