Lajos Juhász

Am I missing something?

You are missing the information from the webinar all the numbers are raised to 370 / 37.0.  https://docwiki.embarcadero.com/RADStudio/Florence/en/Compiler_Versions

During the release webinar Marco has mentioned that it was trained among other informations using the Delphi 13 docwiki.

Congratulations. Wow you went on a double-dark side? (Remobjects and Pascal instead of  that other language).

PS. I wonder will Remobjects do anything with Pascal Script in near future? While Delphi is far behind other languages PS is also lagging.

26 minutes ago, Javier Tarí said:

When a question is about using i.e. MyQSL in Delphi, should it be asked here, or in MySQL places?

Most probably AI. That is another good topic where AI can shine. You give the required information and the AI can generate the SQL or give the relevant topic what you are interested in.

1 hour ago, Kas Ob. said:

Such question and its answer is a reason why a sub forum (specified place) is needed.

No, this is not a good question to ask here. You should ask your favorite AI tool.

21 minutes ago, Stano said:

I can't vote. The questionnaire is unavailable to me.

It is already finished: 

• Poll closes on 10/09/25 at 11:59 PM

On 9/8/2025 at 6:40 PM, Dalija Prasnikar said:

I selected "Existing forums are sufficient", because they definitely are sufficient and can cater for topics around using AI in Delphi. I am also monitoring all activity on this forum, so it does not matter to me whether such posts have another subforum or not.

Please do not be such a selfish. You should also consider those poor AI engines that must filter this forum to learn what is Delphi. It would help them if there was a special AI subforum.

I doubt those organizations will meet the requirement for the Community Edition. CE is for individual (hobby) developers and start up companies. 

You could and (definitely) should wait for Delphi 13. In theory it is going to have better support for newer versions of IOS and MacOS. Migrating a code weeks before a new version of Delphi is available does not make a sense.

On 8/19/2025 at 9:38 AM, Die Holländer said:

Yes, what happened with her between 2001 and 2003 ??

This is off topic. The rumor says she got divorced and kept the house, yacht and the private jet.

You can try to check "Allow Side Effects and Function Calls" in some cases that can help. 

https://docwiki.embarcadero.com/RADStudio/Athens/en/Watch_Properties

(When a property has a getter method the IDE can give "Inaccessible value".)

Dynamic loading might solve the problem. In that case you can change the current folder to be the folder where are your dlls.

You can also try to use https://learn.microsoft.com/en-us/windows/win32/api/Winbase/nf-winbase-setdlldirectorya .

This code works "properly" even though as others mentioned not the best user interface to do it:
 

procedure TForm1.Button1Click(Sender: TObject);
begin
  Memo1.lines.clear; // delete old values
  Memo1.lines.Add(Label1.caption);
  Memo1.lines.Add(Label2.Caption);
  Memo1.lines.Add(Label3.caption);
end;

procedure TForm1.Button2Click(Sender: TObject);
begin
  Label1.caption := Memo1.lines[0];
  Label2.Caption := Memo1.lines[1];
  Label3.Caption := Memo1.lines[2];
end;

Steps to test it:

1.) Click button1

2.) Edit the memo make sure all 3 lines remain.

3.) Click button2 - the captions will change on labels.

This comment is wrong: 

FROM LABELS  this does not work reliabley

That does work reliabley. You are assuming that the TStrings (lines) will add new lines where it will not. Try this one:

procedure TForm1.Button1Click(Sender: TObject);
begin
  Memo1.lines.clear; // delete old values
  Memo1.lines.Add(Label1.caption);
  Memo1.lines.Add(Label2.Caption);
  Memo1.lines.Add(Label3.caption);
end;

According to a google search that dll can have dependencies. In order to load successfully any dll you have to make sure that all the dependencies can be loaded.  (You can try to find out all the dependencies using the proccess monitor).

Dependencies:

• libpq.dll often depends on other DLLs, such as ssleay32.dll and libeay32.dll (for SSL/TLS encryption), and potentially others like libintl-9.dll (for internationalization).

   

  Open ssl can be also compiled to be dependent on Microsoft Visual C++ Redistributable runtime libraries.

You should provide some code you are testing. Not even Remy can see your monitor or debug inside your IDE.

8 hours ago, Gord P said:

Edit:  It is ironic that their own IDE is 32 bits and that they are just now experimenting with the 64 bit version yet they expect all their users to be totally in the 64 bit camp.

I strongly believe that the move to 64 bit IDE was forced due to the fact that more and more database engines allowed only 64 bit access. On the other hand this could be enable to debug a 64 bit Delphi code.

There is none. You have to use a component that is native for the OS/OSes you are targeting.

you are showing the uses section not the scope names for the project.

I do not have to see a screenshot in order to know that the unit scope names for the project is most probably empty or not complete?

Depending the servers you are using to could be still possible. 

2 minutes ago, direktor05 said:

The biggest problem is if I throw this components out would have to rewrite a lot of code which would take me more time than including them.

I  doubt that could be true. I did the conversion from TNT to native VCL 11 years ago, 99% of the job was done using a refind script.

An old application should not require the TNT Components. You should upgrade the forms to use the default VCL components. Adjust the scope names or use full unit names to make the IDE faster and more stable.

Do you need a universal aproach or on a specific setup? If you need for a specific case you should check out how your server implements insert into select between two databases.

Most probably the unit scope names is empty for the package. 

Why would you like to use TntUnicode in a Delphi 12 project? It is outdated, the purpose of the components were to add unicode support for Delphi. Delphi strings and VCL is unicode compilant since Delphi 2009.