>If you're referring to error 2066 than no, it wasn't resolved in VFP9. See Re: Error 2066 Thread #969271 Message #972079.

The simple bug is causing a big disadvantage of the choice of database selection. Recently, I had to mention this to the client as the only problem I faced with VFP 8 in regards to index corruption. For some kind of reason, many project manager have heard bad things about that in VFP and they need to verify that. So, I told them, for me, when I got that, about 4 times in the year, at each occurence, it was only a message returned by VFP which was not representative. In each occurence, no index failure was present and everything was smoothly continuing its operation. But, this is hurting. They just don't want to rely on VFP anymore.