Stano

I don't know what your table looks like, but: every table "must" have a PK primary key You save the PK in the component that displays the data you only access table entries via PK I consider it the alpha and omega when working with DB

I'd rather wait

It didn't help. Just did I do it right?

That will be difficult with me. My knowledge is close to zero. I don't remember such a notice before - but... Some *.inc files exist. Where should they be for MMX to see them? Or what should I do. It's more of an aesthetic problem. I would like to get rid of him.

The vast majority look like this {$IFNDEF DEBUG} {$I OBSIDIUM_ENC_START} {$ENDIF} inherited; FqryService := TFDFunction.NewQry; FqryService.SQL.Text := obsSecureStringW('SQL Text...'); {$IFNDEF DEBUG} {$I OBSIDIUM_ENC_END} {$ENDIF}

I can't understand the code But is it necessary to create a new TQuery every time? I can't judge. In such cases, I have only one TQuery and I only change its SQL.Text.

I feel the same way. I see no reason to worry about it.

I made one more attempt. Nothing again. Maybe they don't like that I'm from Slovakia - Central Europe I give up.

Interesting, they didn't send it to me

Free download Dependency Injection in Delphi Nick Hodges . https://lp.embarcadero.com/DependencyInjection

Last patch - 4 oct. November nothing.

Hi, I am using obsidium and have this problem. I have versions obsidium_x64_1.7.5.13.msi obsidium_x86_1.7.5.4.msi Build configurations: Release Targer platforms: Windows 32-bit [dcc32 Error] obsidium32_enc_start.inc(1): E2029 'END' expected but 'ASM' found [dcc32 Error] obsidium32_enc_start.inc(1): E2050 Statements not allowed in interface part 64bit [dcc64 Error] obsidium64_enc_start.inc(1): E2003 Undeclared identifier: 'obsidium_pattern_marker_a' [dcc64 Error] obsidium64_enc_start.inc(1): E2003 Undeclared identifier: 'obsidium_pattern_marker_c' [dcc64 Error] obsidium64_enc_start.inc(1): E2003 Undeclared identifier: 'obsidium_pattern_marker_b' Debugs are OK. Win11, D 11.2 Support response There's nothing about the include files themselves that could conceivably cause this. I'd think this is either an obscure bug in the Delphi compilers, or some other unit/component causes this. Does anyone know a solution?

I had errors in the code. The compiler did not register them

I would check the printer driver first. With almost every update, MS fixes these drivers. He breaks a lot of them. At one time, a bunch of printers were out of order because of it. They also changed the controller for me and I have to learn a new environment.

Static code analyzers can do that. PAL for sure.

I assume that IBExpert is connected to the FB server. So it knows the path where it is installed. OP knows nothing.

That information about memory management is at least 20 years old. That's why I wrote that now it's probably irrelevant

I am a layman. I remember that the number of arguments 3 is related to memory management. I hope I'm not wrong. It is one "block". I don't know if this argument is still relevant today. I would like to know the answer, the opinion. Such a VirtualStringTree usually has functions with 7 parameters. All static analyzers (FixInsight, PAL) screamed at them. So I turned off this check.

Oh, I forgot that. So I use a separate RadioButton. And he put the buttons in groups.

In such cases I use RadioGroup. It is easier and the user immediately sees what he can and cannot do. The principle is the same.

In my opinion, this is a typical example of failure - bad logic. Simply, the user cannot/must not enter such a combination. You have to solve that on the client.

If I'm not mistaken, there is some time limit to get the lower versions. Did you not cross it?

Turn on automatic saving.

It would be more correct to create the form only at the moment of need. Of course, this also depends on the logic of the program.

----