>>>My company has a legacy system running pure VFP8.
>>>One of our client wants to move to sql server as a back end.
>>>We thought about rewriting the app using c#.
>>>But have decided to use the same VFP code and simply adding SQL server capability...... with same table structures.
>>>
>>>So, the app can run in full VFP mode. or full SQL SERVER mode.
>>>
>>>Can anyone make an argument AGAINST doing such thing?
>>>
>>>Thanks in advance..
>>
>>
>>The question is, why would you want to Keep the VFP backend alive when you can support SQL Server?
>>SQL Server has so much more capabilities, if you restrict yourself because you want to keep the legacy VFP Tables you will regret it.
>>
>>Which arguments do you have to not move fully to SQL Server and abandon VFP Tables?
>
>Some client can't afford SQLServer. Not mention all the support that is required.
>And part of it is speed/performance.

What I have seen from experience is that most companies that cannot afford SQL server licensed version often have also smaller database sizes, so they can use the free express versions. Additionally, there is a lot of confusion about SQL Server licensing. Some people get a quote for SQL Server and end up with a price tag of 20,000 USD while they could work with a version of around 2,000 USD. But as I said that is necessary when the database is larger than 10 GB.

I would be curious how large is your database size on average?