Cristian Peța

Not exactly the database ENCODING. Every database can have other encoding but probably it is OK.

Using TSQLMonitor you can see parameters value. If there are wrong characters then is something from FireDAC otherwise is from PostgreSQL.

This is not the proof that Encoding is UTF8. You need to verify database encoding. Have you?

Personally I would debug the FireDAC code to see where the characters change. Do you use parameters or the values are in SQL text directly? I suppose if you use TSQLMonitor the values are already wrong.

Is the database ENCODING = 'UTF8'? I think it can be specified only when you create it.

Have you tried a new empty project with that line of code? If the issue persists then it would be better to report.

It is easily to generate MD5 with some tool like Notepad++.

Try to add MidasLib unit in the projects uses clause. Maybe the cause is an old midas.dll

After you created the form and want to have only one form you can not return to the code into the constructor without creating an other form.

If you create only one form and want to keep it to change the table the I ask myself as Remy asked: why is that code in the constructor? Also calling Abort into the constructor will destroy the form.

This happens also when you build you package? Usually this happens at compile but not at build. If build was successful then try install again.

Compiler generated code can tell you if a variable is automatically initialized or not. I only wanted to point out that there is a method to check if an AI statement in this regard is true or not.

I apologize, now that I read again was I wrote... but it was not my intention.

Assembler of that code will show the truth... but I think that someone that ask such things do not have ability to read assembler.

Not. The best practice is to initialize to nil if you need this. Because there was something before and that memory was deallocated. It doesn't have anything with object allocation. You can allocate the memory for an object and you variable will remain as it was. var LObj: TObject; begin TMyClass.Create; //LObj is not changed and will contain garbage Only if you pass the value of the object to the variable: LObj := TMyClass.Create; Not. Declaration will only allocate the memory for the variable (a typed pointer in this case) and that memory will contain garbage.