Hi everyone,
I am consistently encountering an unhandled exception in the latest Toad for Oracle Beta (v26.2.222.8909) as well as the 2026 R1 Release.
Note: Since I am a new forum user, the system does not allow me to attach the full text or log files directly. Therefore, I have extracted and pasted the most critical parts of the call stack below.
Issue Description:
The crash occurs specifically when I execute a query containing bind variables, which pops up the Variables window (TFormBindVariables). When I click to modify or select a date value using the date editor option, the application throws an ECommonCalendarError exception.
I have already tried changing and testing all available date/time format options within Toad's Options/Preferences, but the crash persists regardless of the internal formatting settings.
Error Message:
Type: ECommonCalendarError
Message: Failed to set calendar date or time.
Source Unit/Class: Vcl.ComCtrls / TCommonCalendar ->
SetDateTime
Steps to Reproduce:
-
Write a query with a bind variable (e.g.,
:my_date). -
Execute the statement to open the Variables modal window.
-
Attempt to click or trigger the date editor (
ShowDateEditor/btnEditClick) for the date type variable. -
The calendar control fails to initialize properly, leading to the crash.
Environment Details:
-
OS: Windows 10 (64-bit) - System Language/Locale set to Turkish (Non-Unicode Language: Turkish 041F).
-
Toad Versions affected: v26.2.222.8909 (Beta) & v26.1.193.8012 (2026 R1).
Call Stack Highlight:
Vcl.ComCtrls.pas | TCommonCalendar | SetDateTime | Line 29853
Vcl.ComCtrls.pas | TCommonCalendar | CreateWnd | Line 29786
Vcl.ComCtrls.pas | TDateTimePicker | CreateWnd | Line 30373
frmModalCalendar.pas | InputDateTimeQuery | Line 72
frmBindVariables.pas | ShowDateEditor | Line 453
frmBindVariables.pas | btnEditClick | Line 467
Suspected Cause:
Since my Windows system locale settings are Turkish, I strongly suspect there is a date-time parsing/formatting conflict between the OS regional settings and the VCL's TDateTimePicker component rendering wrapper when it initializes.
Has anyone else experienced this with non-English Windows locales, or is there a known workaround while the dev team looks into this?
Thanks in advance!
