Lajos Juhász

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.

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.

I believe the apple hype is over. In Eastern Europe Apple was never a thing. Maybe in 10-15 years Android will take over the place of desktop oses, however I do not see that it can be earlier (the idea to dock your phone on a monitor and use a keyboard and mouse to do everyday tasks).

I can say the current trend for the company for which I am working. For us, the most important OSes are Desktop. We develop business applications. There are managers that like to get reports on their phones, most of the users use desktops or laptop computers. The applications we are creating are 90% Delphi VCL applications, 10% are mobile or handheld devices that are supported by other programming languages.

It is not possible if you want to design the forms. The IDE will show only the visual design for one form. 1 pas + 1 dfm is the limit. You can have multiple forms with the limitation that you create the components on the form in the code.

You should try these steps to report the bug using the e-mail to protect the source code you are working on: https://docwiki.embarcadero.com/RADStudio/Athens/en/Troubleshooting:_Delphi_LSP.

in general, when using with you can never sure to which object you are assigning a value. It can work in one version of Delphi and break in the next one. You can always write: var a: TFDAggregate; begin if Qry.Aggregates.Count = 0 then begin a:=Qry.Aggregates.Add; a.Expression := 'COUNT(Town)'; a.Active := True; a.Name:='NoName'; Qry.AggregatesActive := true; end; end;

First of all do not use with it is always a bad idea. You are not setting the name property for the aggregate object. Edit. I have checked even the examples on docwiki are wrong.

You can send the query as a parameter to the function that generates the XML.

Most probably yes. It would be easier if we could get that information. I do hate when on codebase I am working on changes like this does not have a comment with a proper description or ticket number. Searching in repository for the specific change can be time consuming.

Maybe it is commented out to fix some strange issue/bug. In that case the developer that has commented out the code should include the report number in the comment to document the change in behavior.

You can try the test 64 bit Delphi IDE.

Same on my system 2 different exe files.