Uwe Raabe

It also works at runtime. In that case you need to set the FieldOptions.AutoCreateMode of the query to acCombineAlways to create the dynamic fields and the FieldOptions.PositionMode to poFieldNo to get the same order as before.

Works perfectly over here with static fields. Probably something in your setup.

Well, it does not do that in all of my queries and those of my customers. Can you also show the table definition of CD_Main (the CREATE TABLE command)?

Can you show the actual SQL for that query?

Seems it is time to get to know the reason now.

The simplest way is to create static fields for the query and set the DisplayFormat of the Hour field to hh:nn (Note: mm gives the month).

You may even try to contact sales online: https://www.embarcadero.com/company/contact-sales If you've got that decline by email, check if it contains some phrase that you should contact sales instead. OK, they might try to sell you an update, new license or something similar, but you don't need that to get your registration counter bumped.

No, unfortunately that won't help. Although you remove the license from that PC, you won't get a registration bump with that. The key for getting a bump without active subscription lies here: While the technical support is the right place with an active subscription, you should contact your local Embarcadero Sales representative for a bump when your subscription ran out.

If it were a bug and it is not filed in QP it most likely will never be fixed. To file it as a bug report in QP (with hope it going to be fixed) one needs a detailed description and steps to reproduce.

I guess, the spooky part is the in some files...

I don't know, because up to now I've never let my subscription run out.

It is just a reminder to renew your subscription, just in case you missed to do that.

One possible scenario: Product Management schedules RSP-38842 for 12.3 Product Owner assigns the task to implement that to some developer Developer implements it in an interface breaking way Developer team realizes that the change cannot be done in 12.3 and postpone merging the change Unfortunately they forgot to notify the Product Owner to adjust the fix version

It looks like a mistake when writing these release notes. A new event would be an interface breaking change and thus cannot (should not) be implemented in a point release. Most probably this will make it into Delphi 13.

Can you point to the comment you are referring to?