>Visual Foxpro or Visual Basic.
>
>Please consider:
>Speed.

Too close to really consider being a factor. VFP string handling is _VERY_ fast, but a highly skilled VB programmer can match that speed.

>Easiness.

This depends on what language you know better. Neither language is known for being "harder" to work with, IMO.

>Database size.

The development tool you choose to work with has little to do with the database you choose to use. VFP can use a client-server database as easily as VB can (although with VB, you don't have a choice).

The choice of whether to use VFP data or a Server database goes well beyond the scope of your question. There are lots of things to consider in this choice including needs for security and transaction logging, price, database size, number of concurrent users etc.

>Hosting availability.

Hosting your site on a shared box with other machines that are also running COM objects is a bad idea, IMO. If your app crashes, it can take the whole box down, and perhaps just as importantly, other apps can take your site down. Any serious website deserves to be hosted on its own machine. Colocation is fairly reasonable at most ISPs.

If you can't afford colocation, and are forced to find a COM friendly ISP that'll install your objects, you're more likely to find one with the VB runtime installed than you are to find one with the VFP runtime. There is a list of VFP friendly ISPs at www.west-wind.com.

>Safety.

Irrelevant, except if you are talking about databases. If you are, then see above.