Hi Wilson

I'm working with MSDE-C#-VFP arquithecture. VFP 8.0 is great webservices consumer of C# webservices. With this architecture type, you don't need COM or COM+ neither the Framework in any machine, and the MSDE it is free. You only needs to install the webservice microsoft toolkit, and the VFP's runtimes.
VFP 8.0 is a great data-centric smart client tool. C# is a great language to create bussines components,and SQL server 200(MSDE) it`s a great database.

This is Better than Distributed COM, is a great solution for large companies that must share data between many systems and clients.

And if you see it well, the client doesn't have to spend in licenses. The runtimes of VFP are free, the webservices components are free, MSDE is free, and the client only would pay for the components and the interfaces that you design.

I hope this information helps you in your design.

Regards

Carlos Miranda

>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!