Just to let anyone who may be interested know, I have solved the problem I was having. It turned out that the user's C:\Temp folder had the System attribute set on. When he un-set that attribute, the problem went away. ODBC creates temporary files in the system temporary folder, and I guess when the VFP ODBC driver went to create a temporary file, it couldn't "see" the temp folder so it just created the file in the same folder as the table. Then, when it went to open the temporary file that it had created, it looked for it in the temp directory and couldn't find it. This problem will also occur when the Hidden attribute is set on the temp directory.

>Visual Studio 6.0 SP3, Windows NT 4.0 SP5
>
>I have a Visual Basic program that accesses a Visual FoxPro table via DAO and ODBC. I have never had a problem during the last 3 years or so, but I now have a user who is unable to open the table. When OpenRecordset() is used to open the FoxPro table, an error is generated that says it can't open file "C:\Temp\4IB0000K.TMP". Well, that file doesn't exist in the C:\Temp directory, but it is in the directory where the FoxPro table exists. In running the program on my machine, it appears that the temporary files are created in my C:\Temp directory. On the user's machine, he has TEMP and TMP environment variables that point to C:\Temp. So, it appears that the problem is that the Visual FoxPro ODBC driver is putting its temp files in the wrong location on the user's machine. Is there any way to specify where the ODBC driver puts its temporary files?
>
>Thanks in advance,
>Jonathan Cochran