Thank you guys for your response.

I'll try to give you a little more background info of what we've got and where we are wanting to go with it. We currently have an app written in VFP that uses roughly 200 related tables in its database. We have roughly 350 different locations using this program individually and housing the database(s) at their location(s). The size varies on each table considerably. We have tables ranging from 1KB to 30MB in size for each of the 200 tables.

Now, what we're wanting to do is centralize all of this data from the 350 locations and house it at our location. Then we want to write a web app. that has the same functions as our program that is in place now. This will give them all of the flexibility they previously had and the convenience of it being over the web, plus we will be housing the data so it will be safe and secure. We would like to use a SQL backend for this web app. to work with these tables that are in place. We know that we might have to change the structure of our tables drastically and we will probably sub-contract the job of creating this web app. Then, we would pick up on maintaining it from there on out.

We just need some ideas for servers, other hardware and load balancing scenarios that we would need to make this application fully functional for all of our locations to use at the exact same time.

If you need any more information, just let me know.

Thanks again!
Matt