It sounds like you are getting confused between a problem with your dbf tables and a problem with your SQL tables. The error you got is caused by a problem with dbfs, not by a problem with the SQL tables.

Have you tried validating the database since you ran the upsizing wizard?

BTW, you might find SQL's DTS to be much more flexible than the VFP upsizing wizard, which is widely regarded as bad news. (I haven't used the wizard, so I can't testify personally).

Erik:
You're right, it's a problem with dbfs. I'm confused because it's happening when I am trying to connect to an SQL backend using remote views. The app shouldn't be trying to open the local dbfs, so why do I still get the error?

I can open the local dbfs using VFP with no problem, and I can go to the SQL box and open the SQL tables there with no problem, but the VFP app chokes when trying to use the remote views in my DBC to open the SQL tables.

Validating the database simply regenerates all of the aforementioned error messages.

I haven't tried the DTS wizard. Does it port over all the indexes, default values and so on as well as the data?

Thanks for the reply.