Migrating data from Visual Foxpro using OLEDB - Less number of rows migrated

I am rewriting an application that existed in Foxpro earlier. As a part of this rewrite we also need to migrate all the data from Foxpro to SQL server.

We have built a .NET application for data migration. The application reads data from Foxpro (.dbc file), transforms it, and then load to a SQL server table. We are using VFPOLEDB provider. The process works fine for most of the data. But for some data the extract process does not load all the rows from开发者_如何学JAVA Foxpro. I cannot see a valid reason for this behavior. For instance if I go to Visual Foxpro and run a sql query it returns me more rows than when I run the same query with OLEDB provider. Why is this difference? I would highly appreciate if someone can provide some insight into it.

Are the rows deleted? If you have SET DELETED ON in VFP deleted rows will also be returned.

FoxPro tables are notorious for getting corrupted. What version of VFP are you using to test the tables? Earlier versions of VFP did not complain about corruption but the OBDC driver might skip those rows.