Yuri -

I took a look at your program over on FOXITE.COM.

Yes, TYPE('x') behaves differently in VFP7 as compared to VFP6 for me as well. For me, TYPE('x') comes up "". Very strange.

It definitely seems buggy. We do a lot of work reading and creating Excel files with VFP. I'm hoping this isn't just the tip of the iceberg.

- George

>Yes, and therefore here is the uncertaincy. What does it mean when type() returns empty string? Obviously, it is that Excel has not yet assigned any value and the type of the variable/expression is undefined and/or variable does not exist. And there is a difference: when foxpro declares x=.NULL., it means that x is already declared as a variable and should have type "L".
>
>However in this case VFP type() should return "U", but not empty string. At least this behavior is not documented.
>
>See other opinions on foxite.com forum. I initiated there a discussion yesterday.