These different forms of procedures will produce different performance results depending on what you are trying to achieve. The database procedure will be invoked on the server side and will perform all of the processing there. This may help reduce network traffic, but may overload the server if many clients are doing this.
Local form and library procedures are quite similar in that they are both stored and run on the client with any SQL statements being passed to the server.
The local procedures are typically faster on execution because they are actually part of the .fmx file, but may use more memory and have a longer startup time when the .fmx file is initially invoked.
Library procedures may be better in terms of overall memory as procedures are only loaded into memory in 4K chunks when they are required. However, once loaded they are read from memory.
They have the additional advantage that the library can be attached to a number of forms and the code within the library is then available to the forms.
If the code within the library procedures is altered, the form does not require re-generation. That can be a *big* advantage.
No comments:
Post a Comment