James,

We've all wasted time on bugs in every language, VFP is a complex product, it's just something we have to live with. MS does appreciate being informed of these issues and does put them in the queue to be fixed.

In VFP5 including SP3 there is a bug where GETPEM() on two objects tested inside an IF doesn't work. I've had to put the GETPEM() result into memvars and test the memvars in the IF.

Sometimes using GETPEM and/or PEMSTATUS in a loop can cause internal object references to be held on the objcet which will prevent it from being released. If you run into this you can usually use TYPE() instead.

>Thank your for the information. If M$ had at least documented this unexpected result I would not have spent 3 hours pulling my hair out wondering what I was doing wrong -- especially in a function I have used hundreds of times without a problem. Time is money and I hate it when M$ costs me money.
>
>If you have a moment and you know of any other specific anomolies in PEMSTSTUS() I would appreciate the information. I would have to be tricked again.