Going forward, you will be in better shape going with C#/.NET. And for smaller sites, you would be much better going with MSDE or some other flavor of SQL Server.

Just being more comfortable with VFP might be the worst reason to stick with the product.

< JVP >



>Hello Universal Threaders!
>
>Our development team has been Visual Foxpro developers since version 5 and are very much comfortable with VFP. All our previous applications have been done with the native VFP databases (DBF's).
>
>Now, we are embarking on doing a brand new version using 3-tier approach and using SQL databases (but also would like to be able to scale down back to DBF's for small size clients).
>
>It is important that when we decide it would be for both short term and long term benefits, so -
>
>Should we use VFP 8.0 where we would still be comfortable? or move over to C#.net that most "IT gurus" are saying the language of the future?
>
>If we stay on with VFP, would it be not a waste, and just get the components done in VFP and port it over to C# later? (Some where saying a problem with COM wrappers, whatever that is..)
>
>More comments would help us decide... thanks!