simterico wrote:Ok thanks for the explanation.
Andreas is right, only information on what is visible on client side is transferred to the client in a message-exchange type way. Similar to Citrix, but more on a component level (e.g. textfield at coordinate xy, content xyz, colour xyz).
So for example if you show a data block on a canvas, where there are 10 rows visible - it does not matter how big the query/database table behind the datablock is, the Forms Server only transfers the current screen content (+ any updates) to the client. If you go PgDn, Forms keeps the fields and just transfers the next lot of data - just enough to fill the screen.
You can look at the registry.dat file to see the type of components which are transferred, or you can turn on Client side logging in order to see performance data around message exchanges (if I remember right the basejpi parameter is "printHeaderInfo=true" )
Anyway, it looks like if you have performance issues with certain big FMX, it is because they take longer to load on the server end & pre-form triggers etc. Worth tracing that.
Ok thanks for the explanation.check your form having procedure,trigger or any other validation checking and execution of data when form is loading.
So for the forms which are slow to load, it means that the triggers are slow (or making too much job) ?