>Does somwbody knows about tool for VFP that can check the source codes.
>
>It should be able to find:
>- unused variables
>- using not-initialized variables
>- Syntax errors
>- Type mismatch errors
>- etc
>
>Any compiler is able to do this. Unfortunally, VFP has no compiler and allows programmer to meke too many mistakes.

What you're asking for is a tad difficult to do for FoxPro.

Unused variable - how do you know it's unused? It may be declared as PRIVATE or PUBLIC in some other piece of code.
Using unitialized variables - same as above.
Syntax errors - what's not happening here for you?
Type Mismatch errors - a FoxPro variable can hold any kind of value at any time. It does not do strong typing.

See what I mean? VFP is not a true compiled language. That has both it's pros and cons.