I am trying to give some 70 or so users access to their own record in a database. My method is:

Give a single password to all 70 users.

That password has the "Browse records" and "Edit records" Privileges set to "Limited..." with a calculation that matches a field in their record with a global that they enter on opening (e.g., "userEntryCode=entryCodeGlobal").

This method works as far as allowing them to browse only the matching record. But when they go to edit any field, they get the message: "This field is not modifiable." even though the field is modifiable and they are in their own record.

What is the problem here?

Obviously something is wrong with your scheme or implementation.

What is the purpose of this database? How are userEntryCode & entryCodeGlobal populated?

Thank you, Kurt, for your quick reply.

On further experimenting, it seems to be a problem with individual layouts and not the calculation. These layouts work fine if I leave "Access the entire file" checked (which checks all options) but if I turn off even one option--any option--I can no longer edit in those layouts.

I can only assume that this is a bug or corruption in my file.

If I duplicate the layout, the problem persists, but if I create a new layout and copy and paste the entire contents of the problem-layout to it, everything works properly.

Fixing this will be boring, but at least there seems to be a fix.

I suspect you may have certain layouts set to 'read only' access in the Access Privileges overview. That would account for the fact that it is only with a master password that you are able to make changes whilst on those layouts.

If that is the case, editing the access privileges to make all layouts fully accessible will enable you to control record level access in the way you wish. And it will be much quicker than re-creating the layouts!

Nope, that's not it. All the layouts (including even the pointless ones like "-" spacers) are fully accessible. I really do think this is some kind of corruption in the affected layouts--which are all duplicated from a single parent. Other layouts in the same file work fine.

Unfortunately, using "recover..." and "Save a copy as..." Clone, doesn't seem to fix the problem.

I'll try this: make new empty layouts and paste all the required fields & portals into them; that's no big deal. Then I'll adjust my navigation scripts & buttons accordingly; that will be a pain. Then I'll trash the original layouts and rename the new ones to the old names for consistency. Then I'll let you know if that does the trick.

If it's really a corrupted database, consider rebuilding the whole file again from scratch.

Well, my solution did the trick. I'll have to work back to see where the trouble originated, because this is based on a template that I use extensively. If the template has some sort of problem, I could have my work cut out for me.

Thanks, all, for your help.

Need help with creating an above stated type of database - need to give about 100 users access to their own record.

Need a "how-to" - from the beginning.

Anyone know where I can get a good reference? Or offer any help?

Thanks - FMP newbie

MCGC Webmaster

www.mcgc.net