I have Filemaker Pro 4.0v3 running of a NT 4.0 Server. The users access the database over a network. However, the Filemaker has started closing unexpectedly on the server, and seems to be doing this fairly often. What could be the cause of this?

One of the databases does have quite a lot of records, but the physical file size is about 50 Mb. I'm thinking the server could be running low on resources, but not sure. Any help would be greatly appreciated. Thanks in advance.

Do you can be more specific ?

• is the server dedicated (hopefully) or not?

• is FMP server installed (it seems not,ahi ...)

• which way the db is administered (who takes care to open db before guests log in and close it after the relative logs out) ?

• is FMP cache properly set on server ?

• what kind of platform on clients (W95-W98-Nt or other) ?

• the databases have the 'shared' attribute correctly set in FMP ?

Waiting for answers, regards.

[ May 28, 2001: Message edited by: JPaul ]

quote:

---

Originally posted by JPaul:

Do you can be more specific ?

is the server dedicated (hopefully) or not?

is FMP server installed (it seems not,ahi ...)

which way the db is administered (who takes care to open db before guests log in and close it after the relative logs out) ?

is FMP cache properly set on server ?

what kind of platform on clients (W95-W98-Nt or other) ?

the databases have the 'shared' attribute correctly set in FMP ?

Waiting for answers, regards.

[ May 28, 2001: Message edited by: JPaul ]

---

JPaul,

The server is not dedicated.

No, just FMP 4.0v3 installed, not server.

The database is kept open, it isn't closed (unless it closes itself).

Hmmm...I think the cache is set correctly, but will have to check that.

Clients use Windows 98.

Yes shared attribute set correctly.

The filemaker was running well until a couple weeks ago. Don't know why it just started doing that. Hope ya'll can advise me. Thanks in advance again.

Hi Proton,

if your checks are right it could be a NT server problem: i made me fool, in the past, with a similar situation under SQL server 7.0; situation in which the server was often hang up.

After about 2 weeks of investigations on server, clients, etc. i discovered it was essentially a problem of server's resources during particularly heavy queries !!

Tending to avoid to you these troubles i suggest to immediatly investigate on this way using res. monitor on server (i used both - NT res. mon. & SQL Enterprise mon. before understand and isolate the problem !!)

Do you apply regularly in your scripts the 'flush cache' statement ?

Notice me about and greetings.

[ May 29, 2001: Message edited by: JPaul ]

[ May 29, 2001: Message edited by: JPaul ]