First the set up: On Windows 2000, we are running Filemaker Server 5.5 and Filemaker Pro 5.0 as the web client (separate machines).

In recent days, the Filemaker Pro client has been maximizing CPU usage and refusing any additional work. Twice I had to restart the client machine with the hardware switch. I could get Task Manager up and see the CPU usage, but could not end the FM task using Task Manager and could not get the PC to restart from the start menu.

We moved the client to a newer machine and the CPU problem recurred, but I could at least kill the task and restart FM.

Does anyone have any advice about how to track down the source of the problem? Could this be a run-away query? The primary database being accessed has about 22,000 fairly large records.

Any help would be appreciated.

Kay

Kay->

Assuming that no programming in the databases occured that could cause a change in response time,and assuming that the user isn't doing a new kind of search, I see two main suspects: a corrupt database file on the server or a network issue.

I'd recommend shutting the server down cleanly, copying the files to a client machine, and then 1) recover each file to see if you get any errors, 2) manually open the dbs and perform what the client was doing when they crashed.

Thanks, but I found the guilty party and it was me.

I had changed a web page that, through a Lasso connection, was retrieving summarized data. While it had been pulling one summary field, the new page needed four summary fields. Apparently, that was too much for the client.

I changed the page to do the summaries instead of FM and things are much better.

Do you know why this should have been such a problem?

Kay

Kay->

I haven't used Lasso, so I'm not familiar with its foibles. :)