Is there a way to control how many client stations can have access a record at one time?

What I am trying to constrain is the ability of one client station to attempt to modify a record while another station is currently modifying a field.

If this cannot be done, is it possible to somehow signal the the other stations that the active record is currently being modified?

My network consists of FM Server 7 and FM 8 Advanced and FM8.

Any suggestions?

Jarvis

It sounds like what you're describing is record-locking behavior that is built-in to a multi-user system using filemaker networking. You don't have to do anything to stop the second user from modifying an active record... it won't be allowed and the user will be notified which user is currently locking the record. the user will also have an opportunity to send a message to the other user, asking them to exit the record.

... unless he doesnt have auto committ set... or doesnt that make a difference ?

~genx

Reed,

I think I stated my problem 180º wrong.

You are right. I can't have a problem keeping a second user from modifying the record because Filemaker won't allow that.

The option to send a message to the other user doesn't fix my problem because the other user is usually AWOL by the time a conflict is apparent.(This is a cabinetshop: My guys don't linger around the monitor long enough to receive an error message.They walk up, make an entry then go back to a work station)

What I am looking for is some way to automatically commit every entry so that error cannot happen. I am hoping this can happen in a way that still allows radio button or drop down lists.

Do I need to restrict these guys entries to some kind of dialog box that automatically posts a result?

Any more suggestions?

Thanks,

Jarvis

One way you could do this is to have a set of global fields used as entry fields, and then make them run a script to create, edit, and delete records without locking the records.

Another thing you can do is set FM Server to automatically disconnect idle clients after some short time period. This won't fix the problem of validation errors (if they occur) not allowing their record to be committed...

Thanks Reed,

I think I will look into the scripted global fields.

Jarvis