>>Why do you think this? Every time a new version comes out (SQL Server, Windows, etc), people worry that there will be issues instead of thinking through what happens if there are issues.. If there are problems, it's with the new ODBC driver. And if it has problems, there are bigger issues than VFP not working. It's also REALLY easy to test this for yourself. SQL Server Developer Edition is free and *is* SQL Server, not a wanna-be like LocalDb or SQL Express.
>>
>
>I know, but wanted to make sure since SQL Server 2016 is 64 bit application. I know I can install it for free, but I have SQL Server 2014 installed and it's enough for me right now.

This is why VMWare (and other, free virtualization tools) exist.

To answer your original question, I have no idea if there are any issues regarding VFP and SQL 2016. But the best way to find out is to create a test environment in a VM and see what you find.

In general, you might be able to do some web searches - but then again, I would not expect too many people are using both VFP and SQL 2016 together at this point.