>
>IMO, speed is not a reason to move to SQL Server. Table size, security, decreased network traffic, and remote users are good reasons. I've managed DBFs with 11,000,000 records (1.7 Gig) just fine.


What kind of hardware did you do this on?

I've never worked with milion+ record dbf tables personally. One developer in our org who has, claims when you get table close to a million, you get major peformance hits. Even parameterized views loading a few thousand records out of the million take forever. Apparently you've done ten times the size with no trouble. What do you need to do with a million record table you don't need to do with a 500,000 record table? What do you need to do with an 11 million record table you dont need to d with a million record table? I remember in the foxbase days, it would take 15 minutes to build a new index on 600,000 record table. How long does it take to build a primary key index on (say) a single integer field in an 11 million record dbf.

Thanks

Gar