Total shots in the dark here...take as such:
1. Does it happen on any other app? Are you sure it's FMP? Could it be:
- Clock speed
- Streaming clasical music and video content for the stock ticker at the same time.
2. Log off the other users (end of day or before hours) and see if it is sharing based or computer based.
You probably already tried these...but just in case you didn't. ;)
Enjoy the day!
Issue comes and goes so Hardware specs wouldn't seem to be the key issue.
I only had FMP and Explorer open when I last saw this on my machine, My boss only has the same plus either MS Money or MS Word.
I suspect that either something is bogging down the host machine or FMP 10 is nearing it's max capabilities under times when nearly max users are all interacting with the DB's at the same time.
Open TaskManager and watch the CPU/Memory and watch what's happening when it gets slow.
I would suggest CCleaner
Run the cleaning and registry repair
Defraggler for defragmentation
Process Explorer instead of Task Manager to run down memory hogs
Have you tried various Filemaker Cache Memory settings to see if this has any effect.
Ive not experienced this myself, so its another shot in the dark...
Hmm, I'm doubling the cache settings on my machine now just to see what happens.
I've had 2-4 LAN hosted files open all day with two local test DB's open just on my machine. In the local DB file I've been noticing a brief lag in echoing keyboard input in both text fields and FMP dialogs. With the Task Manager up, I see very brief spikes of CPU usage that never seem to exceed about 30%. No other apps except Internet Explorer 7 is open. None of the files are Filmaker Pro hosted, all are Filemaker Server hosted.
I would guess you have recoverd the files, noted any errors and tested with the recovered files.
and noted any anomoulus fonts being used.
And verified any custom functions and or plugins are up to date and compatible.
Good thought on recovering the files, the problem here is that several of these are large files getting fairly heavy use. Swapping recovered files in and out (without losing any data or edits) to see if they affect performance would not be a simple task. I'll have to think about that one. I can at least swap some of the lesser files in and out.
All files are "plain vanilla"--no plug ins, no custom functions.
Thank you for your posts, and I apologize for the late reply.
There have been a couple of reports of slow performance in a text file when there are a lot of characters (15,000+). One person on the forum reported the problem with several thousand characters without any spaces. From your posts, it doesn't sound like this applies, but wanted to bring that to your attention just in case.
Other than that, I don't have anything else to offer except what others have suggested.
If you have found a possible solution over the last week, please let us know.
Yeah, that's one I've already added to the Known Bug List. It doesn't apply in this case as no record has a field storing more than a few lines of text. Plus, the issue comes and goes on different days.
I did discover that my boss (who has seen the most extreme examples on his machine), had never updated his copy of filmaker from 10v1 to 10v3. He hasn't complained about this since he finally ran the updater, but that was just a day or two ago so the jury is still out on this one.
I just noticed extreme slow downs on one file. I could type entire words before the first letter of the word would echo to the text field. I just checked the Work Station acting as a Filemaker Pro host and found an update software dialog from Apple up and open on the machine again. I dismissed the dialog and returned to my machine and found I could now type in text as fast my fingers could go with no lag.
I seems odd that such a simple thing might affect database behavior and may be simply a coincidence, but if it is a coincidence, it's now happened twice.
Plain text field, right? No autocompletion from any value lists?
Yep, just a plain vanilla text field for recording short memo style messages. Spell check is enabled, but that's it.