Does FMServer eliminate Record Lockout?

[ViciousTruth]

This might be a silly question, but I could not find a definitive answer for it on the product website....

Does running Filemaker Server eliminate the problem of a user locking a record out from another user?

What advantages does running Server have over just sharing a database to multiple users from a single PC?

[Sara Severson]

Never a silly question...

Running Server doesn't eliminate record-locking. If one user is actively modifying a record, and another user tries to do the same, the second user will get a message noting that User A is modifying the record, and it cannot be modified right now.

However, there are many benefits to hosting a file on Server versus FileMaker client:

- Access to more users. I believe only 9 users may connect to a file hosted by FileMaker client, whereas FM Server allows for 250-999 connections (depending on whether you're using Server or Server Advanced).

- Server allows for Custom Web Publishing and ESS connections, which may not matter to you, but the next one should...

- SECURITY. Server has a rich security set-up, including an easy back-up scheduler. If the file is on one user's machine, there's no guarantee that the user won't inadvertently mess with the file. Also, it's irritating if another user wants to log on and the "host" doesn't have their machine up and running.

In short, if you're depending on your solution at all (versus just playing with a file or experimenting with something), it's a great idea to use FM Server so you can better secure the file.

[Steven H. Blackwell]

eliminate the problem of a user locking a record out from another user?

Record locking is an imperative for protection of data and structure. That's why FileMaker employs it.

Steven

[ViciousTruth]

Record locking is an imperative for protection of data and structure. That's why FileMaker employs it.

Steven

Steven, do you employ the separation model in your solutions and keep the user on a single layout, in a single record?

[Wim Decorte]

Steven, do you employ the separation model in your solutions and keep the user on a single layout, in a single record?

Why a single layout and a single record?

Seems like an unnecesary limitation that you're imposing on yourself.