Database encryption performance

[bilalo]

After applying password encryption to my back end, I noticed a slower performance in the front end, forms are taking more time to load. Is this a normal behavior? Is there anything that could be done to solve this issue?

[CJ_London]

by definition, decrypting is a process - and a process will take time. However if you have applied good design principles it should not really be noticeable.

Good design principles include

• not using domain functions in queries
• minimising the amount of data brought across from the BE (only the fields required, apply filtering techniques to the recordsource query criteria, not the form filter, etc)
• applying appropriate indexing
• probably the most effective - once a connection to the BE is made, keep the connection open

[bilalo]

Thank you, how to apply the last part ( once a connection to the BE is made, keep the connection open) ?

by definition, decrypting is a process - and a process will take time. However if you have applied good design principles it should not really be noticeable.

Good design principles include

• not using domain functions in queries
• minimising the amount of data brought across from the BE (only the fields required, apply filtering techniques to the recordsource query criteria, not the form filter, etc)
• applying appropriate indexing
• probably the most effective - once a connection to the BE is made, keep the connection open

[isladogs]

Create a persistent connection by opening a hidden form at startup which is linked to a small linked table.
The table should have few records, ideally one, so it loads quickly.
It can be dummy data if you want.
Keep the form open permanently in the background

[CJ_London]

The table should have few records, ideally one, so it loads quickly.

or just have a form recordsource something like

SELECT * FROM myTable WHERE False

which won't return any records

Keep the form open permanently in the background

to clarify, open the form hidden

[isladogs]

Hi. I did say to open it hidden.
Your suggestion having no records is even better than one record in this case