Stano

Sometimes it is useful to make a list of these components.

If an array of type Date has the option "null" in the DBTable so DTP_STAT_HAND_GRIF_VOL_DOSSIER_OPVR_DATE.Field.AsDateTime := 0;// = strToDAte('30/12/1899') You can set DTP_STAT_HAND_GRIF_VOL_DOSSIER_OPVR_DATE.Field.Value := null;

I don't know the Konopka components. But: In the second part of the code (else) you don't have a value for the date Some components have the property "Allow null value"

https://docwiki.embarcadero.com/RADStudio/Athens/en/New_features_and_customer_reported_issues_fixed_in_RAD_Studio_12.1 https://blogs.embarcadero.com/announcing-the-availability-of-rad-studio-12-1-athens/

I downloaded RADStudio_12_1_esd_61_7529b.exe. During and after installation it tells me Delphi 12. That doesn't seem right to me. Is it ok?

Several of us have a set value of 120 points. It depends on the resolution of the monitor. At my 3440 x 1440 it's fine.

I've dealt with this in the dpr unit. I left things around in the demo as well. Maybe they will inspire you in something program MyProgram; {$R *.dres} uses ... subBillingRestEnBloc in 'SubForms\Settlement\Edit billing\subBillingRestEnBloc.pas' {frmsubBillingRestEnBloc}; var LogonForm: TfrmLoginForm; {$R *.res} begin ReportMemoryLeaksOnShutDown := True; Application.Initialize; Application.MainFormOnTaskbar := True; Application.CreateForm(TdtmdBasic, dtmdBasic); oAppEnv := TAppEnv.Create; Certificate := TCertificate.Create; oGlobVar := TGlobalVar.Create(Certificate); try Licence := TLicence.Create; try Licence.CheckUp; try LogonForm := TfrmLoginForm.Create(nil); except Application.Terminate; Exit; end; if LogonForm.ShowModal = mrOK then begin FreeAndNil(Licence); SupObjJson := TSupObjJson.Create; oAppearance := TAppearance.Create(nil); oAppearance.ReadOptions; if oAppearance.IsTMSStyle then oAppearance.SetStylers(oAppearance.StyleName) else begin TStyleManager.TrySetStyle(oAppearance.VclStyle); oAppearance.UpdateToolBarPager; end; IdentificationData := TIdentificationData.Create; try IdentificationData.Make; finally FreeAndNil(IdentificationData); end; Application.CreateForm(TfrmMainFormFOC, frmMainFormFOC); frmMainFormFOC.Position := poDesigned; SupObjJson.ReadForm(frmMainFormFOC); frmMainFormFOC.Show; Application.Run; end else begin FreeAndNil(LogonForm); FreeAndNil(oGlobVar); FreeAndNil(oAppEnv); end; finally FreeAndNil(Licence); end; finally FreeAndNil(Certificate); end; end.

If the condition "if s<>#48 then" is never satisfied, then j is not initialized. immediately after begin, initialize the variable. I use inline var for this.

Isn't it enough to just make it inaccessible?

It seems to me that you are referring to the Master - detail link. That is handled differently. If it is something else so: the button bothers me a lot I would run the code every time I change a record but the code is time consuming... Which of these applies?

I kind of don't understand your problem. What are you actually pursuing? If you have only one record then the active buttons in the Navigator will be Insert/New, Edit and Delete. This is to say that you can't rely on the cursor buttons. It is better to work with the attached DataSet. Either it has an active/selected record or it doesn't. If you have something else in mind, then describe it more precisely.

Ignore this.

CnPack has a function to remove unused units. to check it is laborious it is not what you require But a miracle can happen

HI, when I tried TFrame more than 20 years ago, I had problems. I was immediately recommended to use SubForm. At that time TFrame was very unreliable. The question is: has that changed? Is TFrame problem free?

This is interesting information regarding Frame. It's probably worth the effort to study it.

Yes. I asked the question mainly out of curiosity. Thank you for all the answers I create a form and set its Parent to some component on the "base" form. I don't have any problems with this.

Please translate this into English. It's an English forum.

Or SubForm.

Setting it while running doesn't help?

Or Continue.

I will note that most programmers completely reject the "with" construct.

You have two options: Test if the list is empty. If so, put the original list Create an auxiliary list. Work with it. If it is not empty, put it in listBox1

In my opinion, the question belongs to TMS https://support.tmssoftware.com/categories

I wrote that you should hide the procedure as much as possible. And you put it on display for the world to see You're supposed to proceed from the top down strict private FSeasonSelect: TSeasonSelect; private strict protected protected public property SeasonSelect: TSeasonSelect read FSeasonSelect write FSeasonSelect;

I'm glad. Now that procedure needs to be placed in the right place within the form. The challenge is to hide it as much as possible from the environment.