Hey all,

I'm trying to create a fool-proof editing ability in my database by setting all user's privileges to [read-only] then run a script which using the re-login script step relogins as a user with [data-entry] priveleges.

Then the user edits the page.

But then when they are done editing I want them to return to their own user account (so they lose editing priveleges again); I can retrieve the login but not the password.

The front end of my database is just the normal login page for web publishing. I was thinking if I store the passwords myself I could retrieve them; is there any way to write my own login page?

Thanks.

Why do that: you are hard-coding account names and passwords into scripts which is a security risk.

Instead, configure the layouts themselves to deny record modification *except* for the edit layout. Then restrict access to the edit layout via scripted navigation.

So the edit layout is an exact copy of of the layout which denies editing.

Then the editing button takes to the edit layout, and the submit button enters data into "real" layout and takes user back to said "real" layout?

How do I set a layout such that you can't edit anything? Fields I understand, but what about portals?