>>Hi,
>>
>>I have a problem accessing a VFP 9 database (container) via Ole DB driver from ASP.NET application. I believe this is an issue with Ole Db driver and this is why I am posting this question in VFP forum. Here is a description of the problem.
>>
>>I have a database container that servs nothing else but a few stored procedures called from ASP.NET application. One of the stored procedure returns the version number. Very simple one, just about 2 lines.
>>
>>I had to do some changes to the database container (some other stored procedures). So I modify it and of course changed the version number. I send new files MyFile.DBC, MyFile.DCT, MyFile.DCX to the customer. He placed them where they supposed to be, overwriting existing file. But when the ASP.NET calls this (Version SP) it still returns the old version number. I even asked the customer to send the files back to me to make sure that what he has overwritten the old files. And yes, when I open this MyFile in VFP 9 I see the version correctly.
>>
>>I asked the customer to search (via Windows search) for another instance of the MyFile.DBC and delete if found. He did, deleted. But still the version number returned is old one.
>>
>>So it seems like VFP OleDb driver uses some older version of MyFile.DBC but we can't find it. Where can it be? What else could cause this type of issue?
>>
>>TIA.
>
>Did you try compile database myDataBase command?

No. Do I need to do it in my VFP 9 Command window against this database? What would it do?

Thank you.