I don't think that gives us enough information... especially the screen effects. Can you describe a bit more?
If the PSoS script does things on records that are also in the user's found set then FM's internal notification scheme can make the client do work to keep what is shown on the screen updated and in-sync. Very likely that is where the 'finding records' comes from. That would largely be a solution design thing.
You mention "optimized server"; what does that mean? Do you have the FMS stats log toggled on? If not then do so, together with the top call stats log. If the machine is running into any of the traditional bottlenecks then that will us which one are getting constrained.
If you really are running a PSOS on server you will not get any thing involved in what the PSOS are doing on your screen. That script that is running on the server will do all the action.
Do you have "Wait for completion" Enabled?
Johan Hedman wrote:
If you really are running a PSOS on server you will not get any thing involved in what the PSOS are doing on your screen.
Yes you will, if you are looking at the same records... FMS will send you all the notifications for your client to refresh things on screen. Including new records, changed data, etc.
It can even run triggers, which is what this technique is based on: ClickWorks | Trigger a script on another client
Not Find Dialog
Yes, even that one. Depending on the design of the solution if the client needs to refresh something because FMS notifies it, it may very well show a "find in progress" dialog if the refresh takes a while. In that case FM is not actually performing a find like if a user was changing the found set, but usually it is resolving some dependency, say from something related. And for FM that is the functional equivalent of doing a find and it will use the same dialog.
We're working through a situation like this for a client right now...
Thanks! Good to know. I have never seen that problem
I have seen this in FMP 10 without any PSOS or server Schedule involved. Client A had a layout in the background that referenced data other clients were very actively editing--creating and updating lots of records in a POS type work flow. It kept updating and the little dialogs kept popping up and the cursor kept changing to an hour glass every few seconds.
Identifying and closing that window (since it was in the background anyway), resolved the issue.