I am experiencing a problem where I am not able to create a new record in the database via the web. The error message I get is:

"Access Restriction: You do not have access to perform the action: new"

The database is for work requests that our users can enter via a form on our corporate intranet. The form's action contains the username and password for an entry in the Web Security database, along with the hostname (i.e. <form action="username:[email protected]/FMPro">). This username and password combination is only allowed to: Create, Edit and run Scripts. The corresponding database password for this user has permissions set to the following (File > Access Privileges > Passwords): Browse records, Edit records and Create records. So with this setup, I cannot create new work requests in the database. However, if I check the "Access the entire file" checkbox in the passwords window for the database file, I am able to create a new record. I have tried numerous combinations of checked checkboxes for this database password but I've not seen any success.

Million dollar question: What am I doing wrong?

Thanks, Jason

Version: v6.x

Platform: Mac OS X Panther

You will need to set, in the "Application/Plug-ins/WebCompanion" preferences, which security system you are using. If this is set to "Web Security Database" you will need to have "Create" rights for that user.

Good Luck.

Garry

p.s. Sometimes you may find that a database is "locked" if it has been copied from CD or from another computer.

I have checked the "Web Security Database" option in the Web Companion Configuration setup window (FileMaker Pro > Preferences > Application > Plug-Ins > Web Companion). In the web security database, I have Create, Edit and Scripts checked as allowable permissions for this username and password combination.

The only way I seem to be able to create a new record via the web is to allow this user complete and total access to the FileMaker file. That seems wrong to me to have to do that.

I have just been testing and I can emulate your problem if I open the database with a "password" other than one which gives "Create Records" permission. Try opening the database with a password which has "Create Record" permission.

Good Luck.

Garry

Thanks for your reply, Garry.

If I understand you right, when you say,

"Try opening the database with a password which has 'Create Record' permission,"

you are telling me to use a web username and password combination within the Web Security database that is mapped to a password in my work request database file which has the 'Create Record' option checked in File > Access Privileges > Passwords... window. The current database password is set to allow entire access to the database file as this is the only way I seem to be able to get work orders in from the web. When I uncheck every option but the 'Create Record' checkbox, I am not allowed to enter a work request (over the web). I am simply informed that I am not allowed to perform the action: new.

Am I missing something else?

You can have any "Password" for the standard access privileges, as long as it has "Create Record" checked and it is used to "Open" the database. You may also need to have "Export" checked as a minimum (I have not fully tested this).

Good Luck.

Garry

Yes, Export needs to be allowed for Wen Companion to operate.

Ha, Ha! It worked!

The piece that I was missing was: I had to open the service request database file in FileMaker Pro WITH THE DB FILE PASSWORD SET UP FOR A WEB USER!

Gee, that's Dumb (with a capital 'D')! Why should it matter which password is used to open my service requests db file so long as the web page sending the 'new' request uses the appropriate username and password combination from the web security db file? Someone please explain the logic behind this to me!

THANKS FOR YOUR HELP!!!

Jason

side note:

Print is considered to be a form of "export" to a printerport/file/PDF and can prevent or interfear if the "Print right" is taken away....

"Why should it matter which password is used to open my service requests db"

Because on the machine Web Companion is acting as a user based on the instructions given through the web browser. Sit and watch the machine while it's being used: you'll notice it changing into Find and Browse modes, entering criteria etc just as though somebody was using it. That somebody is WC. And WC is limited to whatever privileges the database has been opened with, not what username and password is enabled in the url.