Quote:Thanks for the link to the work arounds Mark. I don't go there on a regular basis. I must have missed a message on the forum that work arounds were posted there.
I consider all programming to be critical. If not critical it is not needed and can be eliminated.
Note that I said "data critical". For example, programming that allows selection from a popup - yet still allows the user to enter any value, even if it does not appear in the popup, would
not be "data critical" in that any value is legal. It is merely a convenience. But code that checks that a part number is new and has not been used previously, is "data critical".
Quote:The workaround that is referenced does not seem practical to me. I can have programming on entry to every element, I have no idea which one will be clicked on, and cannot replace every element with a button.
The only "workaround" suggested on the web site is to request the HF from technical support. The workaround you are referring to was a suggestion to the particular customer that discovered this problem and the suggestion was directed to his specific circumstances.
Quote:Since it is noted that the fix is in 1.14,
It is in 1.1.3 HF1, as stated on the web page.
Quote:then I guess I will have to wait for that release.
As I mentioned it is available on request for those that need it.
Quote:I must be missing something in the explanation here. I cannot believe that others are not concerned about this issue.
Again, if you have data critical code in a LE on entry event - redesign. You have no way of knowing that it will ever run in that the user may (and always can, in any program with a mouse) opt to skip that field.