Stano

I know/I read of two cases where programmers used it. AI reduced their time to create the right code from a week to a day. No, they didn't get the right result. But AI led them to it. He who knows what he wants and what he is doing will help himself.

It seems to me that they are doing everything to make it the opposite.

I am enough for nonsense and stupidity. At 100%

I can't work with ChatGPT. Too hard for me.

I do that. But this was Delphi and the description looked interesting. I couldn't resist

Do not insult! (Irony) It's simply curiosity.

The same with me. Before that, a golden Norton

Sorry Lars Fosdal, but that was for Henry Olive.

Where is System.SysUtils.SplitString( ... ??? I don't see it there.

So I put TDBGrid on the form. I do not use it. The LSP Insight offered - see picture. Selected is not there. I'm a little surprised, because it's not hard to find out

Since you are editing the code, what prevents you from getting rid of "with"? We don't even know what grdSelection1 is!

Check out IDE Style. That was my case.

OT: I'm no expert on spilled tea. But Your demo is not in Japanese or Korean. In my opinion, it's a random cluster of some characters. No specific language.

MyTable.Fieldbyname('MyField').IsNull

I'm moving on from Delphi.cz As a temporary solution, the LSP from the previous update was published, which does not have some features from D11.2, but works better with some - https://altd.embarcadero.com/releases/studio/22.0/DelphiLSP_11_1.zip

I paid support for one reason only. Hopefully I'll get a patch that fixes the underlying LSP issues At their rate of repairs for two years to be sure

Have the right DataSet. Use Query and there you go Distinct Where Order By - Check it "manually"

Record locking is one of the reasons why many do not use "DBEdit" type components. You definitely didn't want to read that. It leads me to think of using TMemo. Unfortunately, I can't think of a proper way to resolve the conflicting record access situation. It would have to be server side. Maybe someone knows. I personally use Firebird and it does not use record locking in normal mode. OT: in that case, how do you handle a situation where someone starts editing a recording and goes to lunch? Will you shut down all users for that time?

In other words: there are problems with small projects that do not appear with large projects. This applies to LSPs. I don't know if this includes your case.

You probably confirm what I wrote today. Big project - no problems. A small project - there are problems. Emb I know about it. He doesn't know why. Apparently, they would need some small project where they could study it. I don't have one. But problems do.

I have no information. It mainly revolved around LSP. Generally.

It is said that big problems appear in small projects, which are not present in large projects. EMB knows about it. They don't know why. I have a small project. Sometimes I even cry.

Golden socialism. It was almost stable there Irony of course.

Kinda OT As a lay amateur, I am puzzled by the fact that there are several files in one BLOB. Too much. I would save each file separately from the very beginning. I was already taught that with modern DBs the number of records in the table is not a problem. But I don't know your program, nor its philosophy and function.

Jednoduchými slovami. Ak chceš vytvoriť nový prázdny formulár, tak použi príspevok od FPiette. Ak nejaký existujúci tak CardForm := TMyForm.Create(Self);