Stop Users Deleting Records

S

Simon

I have a database with, lets say, two tables with a relationship of one
to many. (Basically, a database to record version history about
individual files)

And ive got a nice form for my dumbass users to enter data into every
time they make a change to one of these files. The form contains
several bits of info about each file which stays the same (recorded in
one table) And then a sub-part of the form contains the info about
updates. What you should do is, find the file you just made an update
to, and then select a new record within the sub-section of the form
(one2many) to record the new version history.

This then allows me, to scroll back through version history for each
file.

However, these idiots, instead of creating a new record within the
sub-form, are overwriting the previous version history and not creating
a new record.

My first thoughts on preventing them from doing this, would be to
perhaps not allow users to edit the record once its been created - not
quite sure how to actually put this into practise. I also don't want
to limit the users too much in case they make a mistake and need to go
back.

Has anyone else got any other ideas on how to stop this happening?

I should also point out that this is a multi-user database.

Thanks in advance.
 
S

Stefan Hoffmann

hi Simon,
However, these idiots, instead of creating a new record within the
sub-form, are overwriting the previous version history and not creating
a new record.
My first thoughts on preventing them from doing this, would be to
perhaps not allow users to edit the record once its been created - not
quite sure how to actually put this into practise. I also don't want
to limit the users too much in case they make a mistake and need to go
back.
Click to expand...
In such a case i normally use three forms:
- data entry
- overview (read only form)
- detail view (the read only controls have set Locked=True)


For the read only form or subforms in the detail view i set AllowEdit,
AllowDelete and AllowInsert to False.


mfG
--> stefan <--
 
B

BruceM

Perhaps the users sense your contempt for them and are deliberately messing
it up.

Maybe all you need to do is make the subform single view (rather than
continuous or datasheet) and open the subform to a new record. Users can
still navigate to an old record, but will see a new record by default.

By the way, there are off-the-shelf programs that automatically record the
kind of information you wish to track. They are not inexpensive, but
neither is the accumulated time spent manually recording change information.
 
A

Albert D. Kallal

Actually, this is a good question.

I often do one of several things:

1) I often don't allow editing in the sub-form, they have to click a button
to "view" that line of details.

2) I actually place a "button" to add a new record at the bottom of the
sub-form, and once again that means
they have to click on a bunion to add a record.

Doing both of the above really seems to help. Also, there is a term called
"social" engineering, and that is just a fancy term for making designs that
"encourage" people to do what you want first.

For example, I want to "encourage" people to SEARCH FIRST for a record, and
if they do not find that record, they THEN click on the add button.

So, take a quick look/read of how my search form works...what is nice is
that when the search form loads..your cursor is RIGHT into the search
box...and they can type a few chars and then hit enter (or tab) to search.
So, I make it EASY to search, I make the FIRST thing a search prompt!!

The screen shots are here:

http://www.members.shaw.ca/AlbertKallal/Search/index.html

This approach is FAR preferable to launching a form in add mode (since then
users will just start adding!!!). Often, developers don't even supply some
type of search, and users must move their cursor into a EXISTING data form
and hit ctrl-f to search. Not only is this extra pain and work that most
users don't want, but they also accidentally TYPE OVER existing data with
great easy. No one the "first" record in a form load is often messed up
beyond belief.

So, as a result I do NOT allow searching in my forms....

There is also some screen shots here of sub-forms again that don't have the
extra "Line", and simply have a button to add.
Further, users can't edit, and must click on he "glasses" button to launch
the details form

http://www.kallal.ca/ridestutorialp/busmanage.htm

And, here is some examples when I have less space, and place a "+" on where
the navigation buttons would normally go:


Note in the last few screens how a big "+" button was provided...

http://www.kallal.ca/ridestutorialp/setdriver.htm
 
A

Albert D. Kallal

BruceM said:
Click on a bunion??
Click to expand...

Yes, we need a albert fish babel translater.....

that should read "buttion".....

You have a great new year....ok....
 
D

David W. Fenton

2) I actually place a "button" to add a new record at the bottom
of the sub-form, and once again that means
they have to click on a bunion to add a record.
Click to expand...

Would that be placed in the form footer?
 
A

Albert D. Kallal

Would that be placed in the form footer?
Click to expand...

Yes, I used the form footer...
I placed the button in the sub-form footer (since, the sub-form might be
used in several places..I wanted it to "go along" with the sub-form).
I likely should have pointed this out....
 
D

David W. Fenton

Yes, I used the form footer...
I placed the button in the sub-form footer (since, the sub-form
might be used in several places..I wanted it to "go along" with
the sub-form). I likely should have pointed this out....
Click to expand...

I guess my bunion joke was far too subtle. ;)
 
Top