Limiting Users to deleting records

[gowrann]

Hi All,

Can somebody tell me how to restrict users to be only able to delete one record at a time, I have gone into the "Passwords" privileges selected the user and gone to the Limited delete records option, but don't know what to put in the calculations field.

Is this the right area to do this and if so what is the formula.

Many Thanks

[Ugo DI LUCA]

Well not(Status(CurrentFoundCount))>1 would limit the user of using the Delete All records step (if more than one) is in the foundset...

It will also limit the user to using the Delete Record step when more than one record is in the foundset.

So any delete step should rather be scripted with for instance

Omit

ShowOmitted

Delete

Show AllRecords

or GTRR (SJonID)

Delete

Show All Records

or Capture Found Set in global field

GTRR (SJonID)

DefineField(g_IDHolder, Substitute(g_IDsHolder,ID,""))

Delete

GTRR (g_IDsHolder:ID)

Now sure this could be an interresting feature to be created (or does it already exist ?)

[Steven H. Blackwell]

Script the delete and look at the options under the menu control to gray out the Delete menu.

Steven

[LaRetta]

Hi gowrann,

To explain further ...

From Access Privileges, uncheck 'Delete Records' and then down on Menu, select 'Editing Only.' In this way, Users can't delete one record (or a found set) using shortcut keys or menu options, but your scripted delete buttons will still allow deletes.

I never allow Users access to Delete or Create Records because Create Records also gives them access to duplicating records (which can be bad). You will still be allowed to delete multiple records via script whenever needed, but Users having access to your Delete buttons will be nixed. Both those options should be restricted, in my opinion.

If you restrict Users in this way (and assign a generic Password), it's also good to unclick the 'Change Password' feature. And then in Edit > Preferences > Document, enter that same password in 'Try Default Password.' In this way, Users won't be required to type a password in the db - it'll just open for them. Keep in mind that you'll need to provide any Add/Delete buttons throughout your solution.

LaRetta

[Steven H. Blackwell]

I would never assign a default password of any type to a file accessed on a LAN or on a local mchine drive if yiou are concerned about the security, data integrity, or data confidentilaity of the file. You bypass the ability to challenge access to the file.

Steven

[ktstem]

I like the default password option you just described for some of my databases, but I have a question about that. If the database just opens without asking for a password and I have it set to very basic privledges....then how do I get into the database with a "Master" password and all privledges? Is that a stupid question???

[LaRetta]

Hi ktganss!

Not a stupid question at all. Hold down the [shift] key while opening the database. This will bring up the password box for you to enter your Master password.

LaRetta

[Steven H. Blackwell]

Not a stupid question, but auto enter default passwords is not a good idea if you have any security concerns--AT ALL.

Steven

[ktstem]

I understand, I probably won't use it due to security concerns. I just thought I would ask for just in case! It would just be so much easier for users to not have to remember a password. You know how that is!!

Kate

[Vaughan]

" It would just be so much easier for users to not have to remember a password."

Agreed, but it also makes access easier for people who should not have access to the database.

Be careful. Here in Australia we have privacy laws. I'm sure other countries have too. Allowing password-free access to a database that contains private personal information (like home address and phone numbers) could be a breach of the applicable laws.

[ktstem]

Well, the database I was considering using it for, first opens to an empty "navigational" database. From that Main File, you click on the button that takes you to the proper "section" which are all separate databases with their own passwords. That is why I was curious about the default password option. Just curious though, I already have user groups and an opening script that takes the user to the proper navigational layout based on their group. Thanks for all the warning though, I will be sure to NEVER use it!