Uwe Raabe

Application.MainForm is set with the first TForm created with Application.CreateForm.

Sorry, but I don't understand your question.

None that I am aware of. So far a I was under the impression to be able to find the cause in my own code.

Are you sure that the dataset is open?

Actually that is exactly the way to do it. It just seems that setting the Checked property of TDBCheckBox is not propagated to the underlying field. I need to investigate that and file a bug report as soon as time allows. As a workaround don't set the Checked property but the field value directly: chk.Field.AsBoolean := chk = Sender;

@haentschman Not all of the lower numbers still exist...

Oh, now I understand what you want to achieve. One solution would be to wire this event handler to each TDBCheckBox inside the TGroupBox: var DisableEvent: Boolean = False; procedure TForm747.DBCheckBoxClick(Sender: TObject); begin if DisableEvent then Exit; DisableEvent := True; try var grp := (Sender as TControl).Parent as TGroupBox; for var I := 0 to grp.ControlCount - 1 do if grp.Controls[I] is TDBCheckBox then begin var chk := TDBCheckBox(grp.Controls[I]); chk.Checked := chk = Sender; end; finally DisableEvent := False; end; end;

I cannot reproduce that. If I have several TDBCheckBox inside a TGroupBox each can be switched independently.

The patch does not enable that, but IIRC it is standard behavior since 11.2.

Can you please give an example?

You need more patience:

The FieldName is always taken from the database, so you cannot force that. You can change the Name and DisplayLabel after the fields are created. For static fields that is not a problem, but dynamic fields simply don't exist before Open. Therefore AfterOpen is a good place to do. The data type is derived from the type in the database and you have only limited influence on that. At the end, what you are doing is rather unusual, so I assume you are trying to solve another problem using a wrong approach.

Run the for-loop from 1 to length.

I'm sorry, but I cannot understand your problem in the first place. Can you create a small example to allow us to reproduce?

I urge to create a bug report with detailed steps to reproduce. It should be verified that the patch is the real cause and that it doesn't happen without it. That allows others to confirm this or give hints what configuration is necessary to make it happen or not. The changes incorporated in this patch are probably pretty small, so the cause should be easy to find.

AFAIK, they require an active subscription (at least that is mentioned in GetIt as of 10.4.2) , which is not available for the Community Edition. The fact that they were available in 10.3 was probably an oversight.

As far as I understand, the dongle is for the system that does the signing, not the one checking the signed exe. The problem I see is that this completely counterfeits the idea of virtualization when the dongle (or HSM) is hardware bound. I can move around my build server and agents, which are all realized as VM. If my build machine breaks, I can easily set up a new one and continue. In case of a dongle I may be able to move it too, as long as it did survive the fire, flood, earth quake or bomb attack that destroyed the old machine. It creates a new hardware dependency and a single point of failure.

I wonder how the option is going to work. Do we all have to send our dongles to Amazon or Microsoft so they can plug them into their servers? There must be a system that allows to deploy the certificate to these services in some way. As they mention a "such as" for AWS or Azure, there should exist something like an API or guide to implement this for other cloud services, too.

My signing process is part of the build process running at the build server being a VM on an ESXi machine. While I have no problem to connect the security device to the physical machine, I still need to see if and how it can be accessed from the build server VM.

Can you revert the update to see if it can actually be the real cause?

What types are dsetAddUser and tbAddUser and how are they related? Where do you specify the table name the insertion is supposed to go?

Well, that can obviously be simplified to b := 1;

There is! Via the IDE menu select Tools - Manage Platforms, then switch to Additional Options, uncheck Help and click on Apply.

You can achieve the desired result with TTimeSpan: diff := TTimeSpan.Subtract(ET, ST).TotalHours;

That may indeed be a problem with Delphi and/or the TreeView control. MMX suffers from the same symptom.