At 20:37 2018-09-18, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2018-09-18 21:18, Gene Wirchenko wrote:
I use on key label "ctrl+0" *so .null. can not be entered into controls.
Clever!!!!
Thank you, but ...
I do not think of the above as particularly clever; it is simply something that I worked out to avoid nulls. I happened to think that way; you did not. With something else, it may go the other way. Because we can communicate our discoveries/solutions/what-have-yous, we each end up with more as a result.
This is a big reason why I like forums and lists.
On another point, I had an icase() function about five years before Microsoft added it to VFP. Except for that Microsoft's version has selected parameter evaluation and mine has all parameters evaluated -- not something programmers can control in the VFP language -- our icase()s work the same.
I wonder if Microsoft came up with the idea themselves -- not that difficult; it seemed obvious to me -- or glommed onto my idea (which I had posted publicly). Either way is fine with me, just as I do not mind anyone using the above bit of code.
Sincerely,
Gene Wirchenko
Except for that Microsoft's version has selected parameter evaluation and mine has all parameters evaluated -- not something programmers can control in the VFP language -- our icase()s work the same.
Technically speaking, you would be able to achieve this by rewriting the FXP file which must not be encrypted. There's a token for SkipOnTrue and SkipOnFalse that VFP inserts into expressions that are not fully evaluated, such as AND or OR. Whether this is really worth the effort is an entirely different question, though.
-
Christof Wollenhaupt -
Gene Wirchenko