>First I would like to thank you all for your fast response.

You're welcome.

>By Resource files, do you mean the "config.fpw" file?

No, I mean what's typically named FOXUSER.DBF/FPT.

>If that is the case, I use it.
>On the other hand, I told the client to go to another option of my program that uses precisely the same tables I use on the one that is causing the error.
>
> The client was able to open it, and all the options (insert, edit, delete) are working fine on the tables. That form is the only thing that is not working on my program... Menus, reports, and all the forms are fine.
>
> Meanwhile, I did a search, and apparently the error IS a VFP error. Surprisingly, Microsoft DOES NOT have one reference to this error.
>
> Any ideas?
>
> Quickly going insane,

I got the reference to the class browser from MS KB article Q247248. You'll also find a reference to it in the prelimary VFP ODBC driver errors list. It doesn't specify what the problem is nor the solution there. The KB article does indicate that the error is not limited to the Class Browser. I'd start by deleting the FOXUSER.DBF/FPT and see if the problem persists. One of the reasons that I think that it might be similar to the Class Browser are the following lines from the KB article:

"Possible causes of this problem are a corrupted Browser.dbf file resulting from an abnormal termination of Visual FoxPro from a power outage, a computer lockup or restart, and turning the computer off without properly shutting it down."

and

"The Invalid buffdirty call is not limited to the Class Browser."

hth,