I guess that's an explanation alright.

So I guess too that it is expected that one will do a "5" first, then do a "4" if that returned a .T.

I do think the Help could be better phrased to be more clear about the issue. The way its worded now sure led me to believe that I could safely use "4" directly.

cheers


>Jim,
>
>I don't think it's a bug. If property doesn't exist it's nether intrinisic nor user defined. You should first check if it's exist and only after that see if it's user defined.
>
>>The following 3 commands:

_screen.AddProperty("PrintScr")    && add the property (no error)
>>? PEMSTATUS(_Screen,'Printscr',4)  && returns .T.
>>? PEMSTATUS(_Screen,'xPrintscr',4) && gives error re invalid argument

Interestingly the command following run immediately after returns .F.

? PEMSTATUS(_Screen,'xPrintscr',5)

While it may be (don't know) that a property added by AddProperty is not considered to be "user defined", I don't think that using "4" should generate an error.
>>
>>This occurred in both VFP8 and VFP7SP1. A search of (online) MSKB using "Visual FoxPro 7" and "pemstatus" returned nothing.