Thank you for the reply. We too do not use DBC for the SQL. Do you know of any guidelines for the capacity of a SQL server machine?
I am anticipating a lot of questions from our end-users.

Thank you
Yelena
>>Since we are on the subject what are the tools ex-VFP developers are using for the UI?
>>Any preferences and why? We are in the process of moving data from VFP to SQL Serever, and will add MySql. But the front end of the application is still VFP.
>>Any suggestions?
>
>I went into .NET. I now almost exclusively do asp.net development. My preferred language is vb.net (I prefer not to fight the compiler on things the compiler could easily deal with) although I can handle c# when needed. I started my .net development using c# BTW.
>
>.NET has some issues to be sure, but it is Microsoft's app development flagship and they support it now and will for any foreseeable future.
>
>I had been using SQL Server as the database back-end for almost all my VFP apps since the late 90's. No DBCs or anything - just straight SQL pass-through. Never looked back - SQL removed any concerns about data reliability and capacity.
>
>I've had to work with Oracle and DB2 for a couple of clients over the last couple of years - all that does is remind me why I think SQL Server is the king of the hill.
>
>>
>>>>I got an email last night from a company on the east coast looking for Fox devs. They're getting harder to find. My advice to anyone in this situation... rewrite.
>>>
>>>Absolutely.
>>>
>>>>
>>>>>It's been a long time since I developed in VFP. When MS dedcided not to support VFP any longer, I made the switch to C#. Since then I haven't really had my finger on the pulse of the community as I did before.
>>>>>
>>>>>
>>>>>My question is - what's the sense of folks out there? Is VFP still going strong? Are there alot of developers still writing new applications in VFP?