JGMS

Thank you @Serge_G and @sjordi for taking time to answer. Initially I had FMX installed by using the installer V1.77 that comes with the updates that I got from the original developer (I bought a lifetime version a couple of years ago). It always ran perfect, except for this time. Because of the error I subsequently installed it via GetIT (V1.76), but this yielded the same error. I quess things will get better after a fresh installation of the latest update to Delphi version 12.1. I will keep you informed. I

I changed the parameter TNavigateButton to TBindNavigateBtn in both events, and I added FireDac.Stan.Intf to the unit clause to have TFDCommandKind constants like "skInsert" recognised. Problems solved. Thanks for your help.

When I create an FMX application with a StringGrid and a BindNavigator with an Onclick event, the latter sets TBindNavigatebutton as parameter rather than TNavigateButton. The former comes from the unit Fmx.Bind.Navigator and the latter from Data.Bind.Controls. This leaves the question: is there a way to let the compiler accept both parameters?

These are the error messages I got. In common: '...has an incompatible parameter list.... There are a number of TBindnavigators on the form connected to TStringGrids in an FMX 32 bits Windows application. The events that are connected to the BindNavigators from within the Object Inspector are defined by procedure TForm1.BindNavigatorBeforeAction(Sender: TObject; Button: TNavigateButton); and procedure TForm1.BindNavigatorClick(Sender: TObject; Button: TNavigateButton); If I'd click 'Yes' I will loose the LiveBindings connections. I don't even want to think of that!

Thank you @Uwe Raabe I preceded the respective constants in the code with 'TFDCommandKind." to overcome this problem. I am surprised that the Delphi 12 requires the user to make code adjustments due to changes in the compiler. This is so unlike Delphi! Another surpise that I face a problem due to changes in the BindNavigatorBeforeAction and BindNavigatorClick events: they fail because their parameters (Sender asTobject; Button: TNavigateButton) are no longer accepted! In Delphi 11.3 my code runs flawless! Might I ask whether you know what to do about this? May thanks, Jan

Integer constants as defined in "TFDPhysCommandKind" in unit 'FireDAC.Phys.Intf' in Delphi 11.3 and below, appear to be missing in Delphi 12. TFDPhysCommandKind = (skUnknown, skSelect, skSelectForLock, skSelectForUnLock, skDelete, skInsert, skMerge, skUpdate, skCreate, skAlter, skDrop, skStoredProc, skStoredProcWithCrs, skStoredProcNoCrs, skExecute, skStartTransaction, skCommit, skRollback, skSet, skSetSchema, skOther, skNotResolved); Does anybody know what has happened to them? Any idea where to find them? Thanks ahead.

You are a genious! Great! It worked for me too. Thank you very much indeed.

I took PDFFonts from two different installations. But, bad luck indeed: the error remains after rebuilding and restarting D12. I hope @lajos can help me out, once he finds time to do so. Thanks again.

Meanwhile I compared the file PDFFonts.pas in Delphi12 and Delphi11 and found a single difference: "sysutils"was missing in the D12 version. I will check whether or not this is causing the problem using your building tips?

I added PDFfonts to the units clause, but the error remains. I understand that there seems to a bug, which is what confirms my findings. Thanks for answering.

The very day after my first post PowerPDF was available via GetIt. I removed the GitHub version and re-installed it through GetIt. However, the same "Class Arial not found" message pops up when trying to drop a TPrPage component on a form. Arial is a standard font and cannot be removed nor reinstalled. Moreover, it is not missing. Hence it does not seem te be a Windows 11 issue, but rather something wrong in PowerPDF. Can anyone help me with some hints? Please...

I have installed PowerPDF in Delphi 12 via GitHub. The master package in Git seems to be made ready for Delphi12 (there is an 11AndAbove subdir). In previous Delphi versions I used to install PowerPDF via GetIt, but the package still is not available. After about 3 months I can no longer wait. Anyway, it looks like the installation was a success: all controls are in place, and I can drop a TPrReport component on a form. However, the next step, i.e. to drop a TPrPage, fails, showing the "Class Arial not found" message. Since a TPrPage is the container for all other PowerPDF controls, the package is unusable. I have no idea how to get it to work. Do you? I very much appreciate your help or hints.

Thank you for your answer. There was no drive letter assigned, indeed. Good to remember next time.

I found out what the problem was: installing from a network disk (NAS) appears not to be possible. I copied the repository to the C:\-drive and everything went smoothly.