>> I see you're still taking every >> opportunity you can to attack me.
I did not attack you and I have nothing against you personally, blue.I continue to object to the repeated practice by representatives of Genealogy.com (and its predecessors) of blaming Foxpro for its programming problems.
Despite my repeated objections through private e-mail to multiple company reps over many years, the shameless practice continues.And since you use an alias and no longer offer a private address for technical correspondence, you leave me little choice but to contradict you in public.
My apologies to other readers but when Foxpro is repeatedly blamed for UFT's problems then other developers are negatively and unfairly affected.
>> There were two articles I based this >> statement on... I was only able to >> find one of them in the Microsoft KB, >> I'll have to dig deeper to find the >> others, but here's another case of >> VALIDs not firing, and MS saying >> it's "By Design". I'm not making >> this up.
That article doesn't deal with hot keys.Even if it did, it says that Foxpro's code is triggered according to design.It is up to you to deal with that in a way that does not cause the users' data to be lost (just as every other developer I know does).To imply that you don't have any control over the matter (just as you continue to do about the 250 record limit on list boxes, for instance,even though I repeatedly offered you the solution to that problem) is just pitiful.
If you continue to blame such coding problems and the resulting loss of data on Foxpro then I'll continue to call you on it.Foxpro isn't to blame for the way in which you choose to use it.
Besides, the user specifically said that he was using the mouse. If you had even TRIED it before publicly speculating that it is all Foxpro's fault then you would have found that the problem has nothing whatever to do with hotkeys.
So you've started a false rumor (that Foxpro's hotkeys are inherently unreliable and cause loss of data) that will no doubt be repeated in other venues at the expense of other Foxpro developers - rather than just fessing up to a bug in UFT.