Lajos Juhász

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.

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.

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.

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.