Try it, with your small internal group you ought to have pretty good control over incidents. If it's a problem then you know what direction you'll have to go in.

I use OLE DB for synchronizing the data and haven't had problems, but that's more like batch processing.

>Does it depends on traffic load?
>
>I mean, couldn't this likely support a 10-user small team web app?
>
>I ask because I seriously don't know. I have no experience in this field. (Well, except the example below)
>
>It just seems that any time people go talking about web apps, they talk as if there will be thousands of simultanious users all banging the back end at once. Truth is, many little apps just don't have that many users.
>
>For instance, I've written a Rails web app which uses SQLite, which I think is single threaded, and it nicely handles 7 distributed users in their web browser, without a noticeable speed hit. An admittedlly small scale, and anything else database-wise would be overkill. They spend most of ther time looking at the screen, and a few milliseconds calling a REST CRUD method on the back end to get the page rendered. So what if they have to wait 250 milliseconds here and there, instead of 10 milliseconds.
>
>Sure, this breaks down at some point, but it's worth asking the scale of his user base and their data hit rate.
>
>
>
>
>
>>But it uses OLEDB. Not a good idea in a web app.
>>
>>>Here is a library someone has written that allows you to write Linq queries against FoxPro free tables.
>>>
>>>http://linqtovfp.codeplex.com/
>>>
>>>
>>>With this, you can pull back record sets and use them in whatever .Net UI paradigm you want.