Leaderboard

Uwe is providing useful information that your problem may have an environmental aspect to it. Your antagonistic response is very counterproductive.

type {$I jedi.inc} {$IFDEF DELPHI28_UP} {$DEFINE HasPixelsPerInch} {$ENDIF} TBaseDataModule = class(TDataModule) {$IFNDEF HasPixelsPerInch} protected // Ignore PixelsPerInch property in TFrame introduced since Delphi 11 procedure DefineProperties(Filer: TFiler); override; procedure IgnorePixelsPerInch(Reader: TReader); {$ENDIF} end; {$IFNDEF HasPixelsPerInch} procedure TBaseDataModule.DefineProperties(Filer: TFiler); begin inherited DefineProperties(Filer); Filer.DefineProperty('PixelsPerInch', IgnorePixelsPerInch, nil, False); end; procedure TBaseDataModule.IgnorePixelsPerInch(Reader: TReader); begin Reader.ReadInteger; end; {$ENDIF} I created a base module to solve this kind of issue

You don't need a Delphi specific text to learn about unit testing. In fact I expect that the best texts won't be Delphi specific.

Seems... you are perfect, too? 🙂

On a more serious note, I often use a ListBox or something and show the types of things that are being loaded which are taking time, such as opening datasets or connecting to a remote resource. Not only does it inform the user of what is happening but also might show (visually) where the bottlenecks are when there's a pause in the scrolling list of activities.

Sounds to me like chasing the wrong rabbit.

Hi... I hope this SQL is only for you in the development? For editing SQL by users...have you heard of SQL Injection? https://en.wikipedia.org/wiki/SQL_injection

What happens if you add over time WITH XX AS (... ?

I downloaded and the PAServer patch shortly after it was made available and can confirm that it is 13.0.12.0

I would suggest that before you claim to support pmv2 you should add a second monitor which you can run at a different DPI, and test everything. This is the best way to be confident that your users will find no surprises in your software. But even then if the user setup differs from yours, it may not be enough.

I strongly recommend that you identify the problem before trying to solve it.