>>>In case you missed it in another thread here today, there is a Gotcha in using a BINDEVENT for an event where VFP passes parameters to. Take the MouseMove event for example. Edit the MouseMove, and you see a parameter statement:
>>>
>>>LPARAMETERS nButton, nShift, nXCoord, nYCoord
>>>
>>>So, when you BINDEVENT any event to which VFP passes parameters, the delegate method or procedure needs to lead with a parameter statement with the same number of parameters. So the MyMouseMove code in the BINDEVENT example below must have a parameter statement in order to avoid an error:
>>>BINDEVENT(THIS, 'MouseMove', THISFORM, 'MyMouseMove')
>>>BTW, this is documented in the VFP Help CHM file.
>>
>>How come this is a Gotcha if it's documented? :)
>
>Hehe! Just saw this after months away. Poor choice of words in the subject. It's really something that will bite you because who reads Help files?
>
It's not really a problem because it will immediately come up on the first test. Then you read Help. :)
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison