Uwe Raabe

47 minutes ago, dummzeuch said:

Aren't we doing that right now?

Unfortunately not for every patch.

10 minutes ago, Lars Fosdal said:

Half-baked patches are no fun. 

I wonder if beta testing for the patches would help here.

15 minutes ago, Lars Fosdal said:

I just tried my example code which failed before the April patch in the 64-bit IDE, targeting 64-bit Windows.

Try with external MSBuild in the project options and select x64 as preferred architecture. Key is to use the 64-bit compiler versions from the bin64 folder. The target platform is almost irrelevant. Only bcc64x got an update with the April patch.

30 minutes ago, Roger Cigol said:

It's called the April patch

Sounds reasonable:

13 minutes ago, Squall_FF8 said:

Could you try that at runtime?

It also works at runtime.

14 minutes ago, Squall_FF8 said:

Also the query to have at least 2 fields (Hour and whatever) (so we have a static and dynamic fields at the same time).

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.

11 minutes ago, Squall_FF8 said:

Personally I think the problem is from FD engine ... it returns all fields as WideString instead of appropriate type.

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?

29 minutes ago, Squall_FF8 said:

for unknown reason the quarry returns WideString instead of Time.

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

6 minutes ago, TWinAPI said:

Well, as I said, my request was declined because I don't have an active support and maintenance agreement in place.

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.

35 minutes ago, TWinAPI said:

So, my main question is simply this:  If I delete the existing licence from my old PC, will this free up the serial number so that I can use it on the new PC?  Or will it remain unusable?

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:

37 minutes ago, TWinAPI said:

I approached Embarcadero technical support with a request for an additional registration slot for the serial number I have

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

1 hour ago, cupwalker said:

Will it disapear after 0 days?

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.

2 hours ago, Rollo62 said:

How can that happen

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?

Yeah, I know. That's a pity...

27 minutes ago, limelect said:

but my stable Delphi is more important to me.

A stable Delphi is also important to me. That's why I do my best to help Embarcadero achieve this.

There are several toolbar issues listed as fixed in 12.2.

6 minutes ago, dummzeuch said:

Is that just another oddity of my particular installation(s) or does this happen everywhere?

It doesn't happen here and at least I cannot remember having this seen anytime.

As usual: Can you reproduce with a vanilla IDE installation?

You can iterate the protected DataLinks property (there are several ways to access a protected property described elsewhere). For each TDataLink in this list act according to the actual class type: A TFieldDataLink gives you access to the corresponding Control, while a TGridDataLink provides the connected Grid. There are other classes inherited from TDataLink with other purposes, but that should you get started.

Make sure that the query is not Active in the designer.