Whenever I am working on a Quick Fields Session, it takes forever to save the session. This causes some delay in my ability to proceed with my work. I was wondering why it appears that Quick Fields sets the session save file to 0 KB when i hit save and then slowly gets larger until it reaches its final filesize. It is like getting Quick Fields to regenerate the entire save file each time one hits save.
This is not just a nuisance, but a problem with clients who are using the sessions I create. We have had clients accidentally close Quick Fields in the middle of saving the session and it causes the session file to be corrupted.
My question(s) are as follows:
- Is there any best practices I can use to reduce this? Maybe I should change this to a feature request for Quick Fields to save sessions by only adding into the existing file the changes that were made since the last save occurred.
- Why does Quick Fields use this type of save method?