Somebody please help me. I want to password protect the Edit and Delete buttons on a FM4 web/database.

When I set up the FM Web Security DB I put in a Username and Password and set the rights to everything, they can do all. If I do this everybody that hits the site is prompted for a Username and Password. If I put in "All Users" in the Web Security DB then nobody gets prompted for a Username and Password, but the Edit and Delete buttons are gone.

How do you password protect just the ability to edit or delete a record and allow every body else the ability to browse and search?

I don't use web security, I use the db security. Make a "no passord" in the databasr that allows only browse and export. Make the other passwords with browse, export, delete. edit etc.

No password will be requested *until* somebody clicks on a link or form button with the -edit or -delete or -new action tag.

jbreslow said:

How do you password protect just the ability to edit or delete a record and allow every body else the ability to browse and search?

Hi there!

I have the exakt same problem, just one big difference.

I use IWP and not CDML.

I use db-security, not web security.

I want all users to be able to browse and search(=<no password>) and some users to be able to edit/delete (=password)

If I have a <no password> privelege in the db there is no promtp for pw. And there is no way to click a link with edit or delete privileges. They are hidden!

How do I let the users with pw-privilege get to the edit/delete forms?

I this not possible with IWP?

IWP generates format files on the fly based on its limited capabilities and your extensive abilities as a FileMaker developer.

You must have an inherent understanding of the intricacies of the way IWP generates format files and design your db files to force the generation of the format files that you desire. I infer that gaining the "inherent understanding" is a trial and error process.

Bon chance.

Unable said:

IWP generates format files on the fly based on its limited capabilities and your extensive abilities as a FileMaker developer.

Well, my capabilities maybe limited, but thats why I ask questions here.

Unable said:

You must have an inherent understanding of the intricacies of the way IWP generates format files and design your db files to force the generation of the format files that you desire. I infer that gaining the "inherent understanding" is a trial and error process.

Bon chance.

OK, so trial and error it is.....

"I haven

Even though the FMI security pop-up is such an ugly interface, it can work, so you might try this.

On your index.htm you advise your clients that they must enter the password "snaketoes" when prompted. When they do they get the limited access you have set for that password.

An administrator would know her unique password and would ignore the "public prompt" and enter the password which allows her to edit/delete/ whatever.