Hi Pertti

>And you are right about the .F. -return. The error handling was just a stub. VFP of course stops you dead in your tracks without returning anything. How about returning a NULL on error? Wouldn't be 100% compatible, either, because in VFP comparing ANYTHING (even NULL) to NULL returns FALSE, so your original code would get "false negatives" whenever there's an error in the BETWEEN() -function parameters.

You probably have seen that I left that area mostly out in my implementation. The reason was that .Net is a statically typed language - and I looked into the vfp toolkit to get an idea how they handled methods with the same name but different method signature. Well, just like java<g>. So I could refrain from writitng the needed other stubs any method capable of working with different parameter types needs (this is only a guess, not a missive from ETec).

I was hopong some of the effort writing on vfp demise flames threads could be channeled into this, but that has not really materialized as of now - perhaps a few more people showing that bootstrap compilers are still possible will help.

regards

thomas