This probably isn't a problem with FMServer itself but since it involves multiple users in a client-server relationship I thought I'd post it here...

I have found that FMPro 10 clients have a buggy behavior if multiple users run the client on the same machine.

The typical scenario is that user is accessing the Server but is not finished and leaves the client running. A second user comes along to the shared machine and, not wanting to disturb the first person's work, utilizes the 'fast user switching' feature of Mac OS X to login without logging out the first user. The second user can access the same database but all error messages appear as blank dialogue boxes. Even the text on the button is missing.

This behavior did not exist if both users use an FMP 8 and it also is not a problem if one user launches FMP 10 and the other uses FMP 8.

I've tried reinstalling the software but that doesn't help, nor does it seem to be limited to one machine. We are running strictly Tiger (OS 10.4.11) Has anyone else encounted this behavior?

Edited April 24, 200916 yr by Guest

I have found that FMPro 10 clients have a buggy behavior if multiple users run the client on the same machine.

Probably not a good idea to do this.

Steven

Yep, that goes without saying. Sadly having multiple users on the same machine was not a problem in the past. It shouldn't really create database problems either since, obviously, both users can't be making edits at the same time.

The problem comes if someone else is logged in and the second user cant' get to their login space to quit FMPro. If they don't have admin privileges the only option is reboot the computer.

It shouldn't really create database problems either since, obviously, both users can't be making edits at the same time.

Actually they can do so, and in any regard, it's not a good diea to be running this type typology.

Steven

Indeed it is possible that one user may have entered a field without having committed the record so a perhaps a conflict may arise in that field. Filemaker has facilities for handling that if users are at separate locations. Other network apps have no problems keeping users separate who are logged in to the same device - consider the example of the web browser.

Furthermore the problem that I'm alluding to is not data integrity. FMS seems to be doing just fine with that. The problem is quirky behavior of the error dialogue boxes. They pop up at appropriate times, just the text is missing.

The ability to function in a multiuser environment - where shared computers are required - would be a feature. Generating blank error messages is a bug.

Entering a field does [color:red]not lock a record. Beginning to edit that field does lock the record. And it remains locked until the user commits the record or until the user is kicked out by FileMaker Server Admin Console or the idel time out function.

Steven

...beginning to edit that field does lock the record and it remains locked until the user commits the record or until the user is kicked out by FileMaker Server Admin Console or the idel time out function.

That's a nice pearl.