> >>Example, for me, my application is written in VFP. Therefore, should I, and those in my shoes consider:
>>>
>>>1. VPF/SQL
>>>2. Move to VB/SQL
>>>3. The whole .Net thing
>>
>>Developers and architects are often the best people to decide what is best to use and why, but I will offer you some suggestions to consider. If your data is in SQL Server, then using VFP 7.0 for the smart client (desktop) and/or the middle tier is very useful and powerful, properly the way to go. If you need to add web/internet access to the application, then adding ASP.NET to the application is a good solution. VFP 7.0 + ASP.NET + SQLServer is a great solution for many modern and future applications.
>>
>>I will add for your planning purposes this additional information. The next version of VFP (Toledo, Visual FoxPro 8.0) will have new and improved features and functionality for both SQL Server integration with VFP as well as new .NET related features including ADO.NET with VFP interop. VFP 8.0 will be even better at integrating with SQL Server and ASP.NET/ADO.NET than VFP 7.0 while being backward compatible with VFP 7.0. More information and details will be announced and be taught in sessions at the upcoming DevCon conference Sept 29th-Oct 2nd in Florida.
>
>Sounds like great news. Thanks.
>
>I've had 3 clients in the past 2 years that have taken this approach. It took a lot on my part to prove that this is the best approach but they seem happy with the results. Feel free to contact me if you need recommendations. I have plenty of experience in this arena.

Thank you very much for the offer, Victor. I will take you up on it. What book would you recommend for ASP.NET?

Alex