Record locking results in slow FM

[CARDrico]

Hello,

Does anyone have experience with record locking through FM server hosted files ?? I created a file where i put record acces through a calculation field. Why ??: because i can edit this calculation without having to close the file on the server. I only have to disconnect all the users on that file. In this calculation i put some references to an other file (i use a separate file with all my usernames and put into some fields what they may do or do not.) This was working verry well without the record locking but i had to put calculations on every field. With FM 5.5 i can use record locking so i'm now replacing all the old program codes with this, so now i'm really sure they cannot access any field in the record. This is working great, exept for 1 thing: The system is terrably slow, at first i thought that it was because i started out with a new clone and imported all the data (about 48000 records) and all fields where not indexed yet. But now i see that one way or the other filemaker has to create a new index everytime the user wants to use this file.

Does anyone has experience with this and find a solution for this ??

Richard

[LiveOak]

Just a guess, the usual rules for calculation with related fields apply. If you base access to a record on a complex calculation which uses related field, evaluation may be slow as this unstored calculation is run every time every user changes records. If this calculation operates across multipe files and especially multipe records in multiple files, it could be slow. Might be time to rethink the approach or optimize the calculation for speed.

-bd