Tables and record in use errors

[mborgens]

On a served FM 6 and below file if one person is in a field all others are locked out of that record. As I convert to 7 and create multiple tables within a file, are people locked out of individual tables or is it still record level lockouts?

Mark

[The Shadow]

Neither, FM7 has improved its locking.

A record is not locked until someone starts making a change to one of the fields - others can still click in and read, but they will not recieve a dialog unless they attempt to make a change. When the dialog *does* come up, the user has the option to send a message (within FileMaker) to the person who is clicked in with changes.

[mborgens]

On a current served FM6 solution I'll have 3 people trying to access a record to make changes, all with the same deadlines. Plus, many individuals will start to modify and walk away. I know that we can adjust FM server's timeout limits, but 30 minutes can be an eternity. I have been adding files to reduce this conflict. I was hoping that by creating tables within a file that access would be "table level" instead of record level. As people reduces files and create tables within a single file, access conflicts will increase.

Another question. On FM6, if you have FM administrative rights and send a message to a user the message only rises to the level that FM is running, i.e., if FM is running behind a program, the user does not see the message and the message only stays on screen for 15 seconds. Is the messaging system on FM7 different.