>There's definately something fishy with using _SCREEN inside the NVL function.
>
>I boiled your code down to the following:
>
>LPARAMETERS MSG1
>
>if type( 'msg1' ) = "O"
> ?"object"
>else
> ?"not object"
>endif
>
>When you call this test function with an argument of NVL( .NULL., _SCREEN), you get a program error (usually on the second time you call it). If you make the same call, except with a form object (that is, o = createobject( "form")), it works fine. An argument of NVL( _SCREEN, .NULL.) works fine too! That's wierd.
>
>- Mark

---

Yes, I have tried to use the above BOLD code with another name.(test.prg)
Still the Same problem!!

Test(_SCREEN) && no error
Test(NVL(_SCREEN, .NULL.)) && no error
Test(NVL(.NULL., _SCREEN)) && OS/VFP error

---

Even I start the VFP again with type the Last Error code in COmmand WIndow.
The Error occur AT ONCE!!!

So, This Thread Topic is: Are there any error which cannot be handled!!
I want to know what BUG(s) will cause these serious type error.
It will be great problem as an application have over 1-2K LOC but may cause
serious problem even for 1 line of code! ~~~~>_<~~~~

This problem is more serious than Ime Problem in grid nor #253 failure in listbox or ignore code on CreateObject init Field-type statement!

Can anyone who have VFP 6 or Devcon check if these problem also occur or not!?
Thanks for attention!