I think this is a Unicode issue, but...

[DaveR]

Related possibly to
https://support.dataaccess.com/Forums/showthread.php?69500-Compare-variable-to-string-returns-different-result-in-64bit
and thus to
https://support.dataaccess.com/Forums/showthread.php?65401-Congratulations-about-ICU-addoption-request-to-not-stop-there!&highlight=DF_LOCALE_CODE

I put shortcuts into my cMyDateform so that a single key B (or b) could (for instance) insert the month-start date, E for month end, Y for Year start, and T for Today. Since 20.1 it has ceased to work whether in 32 or 64 bit machines. As all my chosen keys are in the low aAscii range I though it just just work. Suggestions?



//idea from from csyintellisense mixin, allow hot keys in dates
Procedure Key Integer iKey Returns Integer
Date dToday dTemp dDateNow


Move (CurrentDateTime()) to dToday


If ((Character(iKey) = "T") OR (Character(iKey) = "t")) Begin
Set Value to dToday
End
Else If ((Character(iKey) = "B") OR (Character(iKey) = "b")) Begin
Get FirstDayInMonth dToday to dTemp
Set Value to dTemp
End

[Frank Cheng]

My suggestion would be to attach a debugger and start debugging it.

1) Is the procedure getting called at all?
2) When you press "T" on your keyboard, what is the value of iKey?

Frank Cheng

[DaveR]

My suggestion would be to attach a debugger and start debugging it.

1) Is the procedure getting called at all?
2) When you press "T" on your keyboard, what is the value of iKey?

Frank Cheng

1) yes.
2) WFH right now and remotePC seriously plays havoc with keystrokes so it can wait until I'm back in, but that was likely to be my first approach.

thanks

[DaveR]

1) yes.
2) WFH right now and remotePC seriously plays havoc with keystrokes so it can wait until I'm back in, but that was likely to be my first approach.

thanks

and today, at the desktop and without remotePC, it is working as before. I know what I saw yesterday and I will wait for it to manifest itself again.