I've had tables with millions of records and not had corruption. It's more a matter of application design.

You'll also have transaction difficulties if you need to update the one table in SQL Server and others in VFP.

>I was wondering if anybody ever created a project with database split between VFP and SQL Server? How practical it was? Any problems?
>
>I want to start converting a very large application from VFP 6 VFP DB to VFP 9 and SQL Server. But I realize the magnitude of the project will be too big to accomplish in reasonable time. So I am thinking about an approach of moving only one table to SQL Server. This is a very big table (of about 300,000 records) that often gives me problems (corruptions). Then, I could move other tables of the application to SQL Server, one step at a time.
>
>Any suggestions or warning will be greatly appreciated.
>
>Thank you.