Hi James,

I think where Richard is going here is the realm of Windows Events, or more accurately, COM events. VFP currently does not generate these. And, while Access/Assign methods simulate an event, they are completely different animals. On a technical basis, Richard has me here.

However, that was not the point of my comment. There are things in VFP that cannot be done in VB. OOP and inheritance being the number 1 item here. The fact is, you can simulate much of it in VB. The point I was attempting to make is that you can take a VB app, and port it to VFP. The converse is also true. Is it hard? Well, it won't always be easy. But, it can be done.

>>>> Right here, right now, I personally put out the challenge to somebody to present me with VB code that I cannot duplicate in VFP...
>>
>>Is there a prize for coming up with VB Code that cannot be duplicated in VFP? If so, I'll accept it now. The answer: any VB Code that raises an event.
>
>Richard,
>
>You'll lose.
>
>If you can define a property in VFP you can define an Access/Assign method to handle changes to the property -- in effect the same as defining and handling handling an event in VB, just a little indirect.
>
>regards,