ECommonCalendarError when selecting date in Bind Variables window (Toad Beta & 2026 R1)

Toad for Oracle - Beta
1

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:

  1. Write a query with a bind variable (e.g., :my_date).

  2. Execute the statement to open the Variables modal window.

  3. Attempt to click or trigger the date editor (ShowDateEditor / btnEditClick) for the date type variable.

  4. 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!

2

Hi Matt,

Thanks for all of the details and congrats on the World Cup win last night.

You are probably right about the date format. As a workaround, you may be able to fix it by going to Options -> Data Grids -> Data and setting the date format there to match your windows settings.

image
image852×665 34.1 KB

I will try to reproduce this soon and let you know what I find.

-John

3

I just tried to reproduce this by changing the windows date and time format to various settings.

I was never able to reproduce any problem when setting values for date type variables in the editor.

I am on Windows 11 though. I can try again with 10 next week.

4

Hi John,

Thanks for the quick follow-up!

Regarding your suggestion: I had already thoroughly tested changing the date/time formats under Options -> Data Grids -> Data to match my Windows settings (as well as trying several other standard combinations). Unfortunately, modifying these settings inside Toad does not prevent the crash; the application still throws the exact same ECommonCalendarError the moment the date editor button is clicked.

Additionally, I noticed a subtle difference in Toad's custom Date Format window (as seen in the screenshot I attached below) that might be worth mentioning, just in case it's somehow related to how the VCL layer (TDateTimePicker.CreateWnd / SetDateTime) initializes:

image
image457×206 5.57 KB

At the bottom of that modal, the preview shows:

  • Toad: d.mm.yyyy

  • Windows: d.MM.yyyy

I know that in standard Windows API and Delphi formatting routines, lowercase mm usually denotes minutes while uppercase MM denotes the month.

Could there be a chance that this minor case-handling discrepancy or string mask mismatch causes a conflict when Toad initializes the native Windows calendar control under specific regional settings? I even tried tweaking some related format strings via the Windows Registry (Regedit) to see if I could force them to align, but the crash persisted.

It might just be a cosmetic difference in the preview label, but I wanted to share it with you since it stands out on the Turkish locale where the dot . separator is used.

Hopefully, the attached log provide some extra clues for when you test it on Windows 10!

Best regards, Matt

Log.txt (96.4 KB)

5

Thanks.

I can reproduce this now. I had to go into Control Panel to be able to select Turkish for the date format. Before, I was just trying different settings in the new Windows settings window, which is not as flexible.

Delphi was returning the wrong value of TRUNC(DateValue) when the date settings are in Turkish. We were using TRUNC to assign the date value to the calendar edit, and DateValue - Trunc(DateValue) to set the value for the TDateTimePicker in that dialog. I switched to DecodeDateTime and EncodeDateTime and the problem is solved.

I'll have this fixed for next version.

-John

6

Hi John,

Great news! I'm glad you were able to reproduce it and find the root cause.

Thank you for fixing this for the next version. I look forward to the update!

Best regards,

Matt