Let's say it's been added using addproperty() to the _screen. Checking with '5' instead of '4' will return .t. Now if I check using '4' to see if it is user-defined, I still receive an error, not a false. How do you see if it is user defined without the error occuring?

>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.