Any time you view information in Streamtime, FileMaker Pro downloads all of that data from the server to the client machine. This means that in order to increase speeds, we need to minimise the data transferred between the server and client machine where possible. Here's how:
1. Update to the latest version of Streamtime.
2. Keep your database current and tidy.
- Work towards accurate 'Active' lists for Quotes, Orders, and Jobs.
The shorter your Active lists are, the faster they will load. And, keeping your lists tidy means that you will have an accurate idea of what stages your jobs are at.
Process Tip: Once you set a Quote Status to "Accepted," lock the quote by clicking on the padlock. The quote will remain reportable, but will be removed from your Active list.
- Complete tasks and lock jobs once they have finished.
The Progress Bars in your Job and Task lists are calculated on the fly every time you view them. This means that the more open tasks you have, the longer it will take to calculate and display your list. Where possible, the total number of hours logged to a job should be kept to a minimum. Internal jobs, for instance, should be closed on a yearly or 6 monthly basis.
Tasks will also disappear from your My Tasks view the day after you have completed them, giving you an accurate To Do list.
Process Tip: After sending a final invoice for a Job, navigate to the Job and 1) change the status of the Job to an inactive status, and; 2) lock the Job by clicking on the padlock. Not only will locking a Job remove it from the active jobs list, it will also tell you if there are any uncompleted tasks and allow you to automatically complete them.
- Adjust the task calendar settings accordingly depending on how many tasks/staff are in the organisation.
Reduce 'Max staff tasks' and 'max days to display' figures if slow.
- Add ONLY the staff in their team to the task calendar
The more staff members you add to your task calendar, the longer it will take to load.
3. Keep Job Attachments to a minimum.
The more Job Attachments you have, and the larger they are in size, the more likely they are to slow down your database.