Setting permissions

[skip]

HELP

I need to know how to allow users to edit fields in an existing record that has no information in it and only allow permissions for certain fields to be updated. I've set permissions to allow users to add new information but once they get out of the record they can't edit anything since they are only allowed to add and that won't work

Also, how can I tell Access to open up in a new record so that information in an existing record will not get accidentally deleted or typed over

Thank you.

 

[Tim Ferguson]

I need to know how to allow users to edit fields in an existing record
that has no information in it and only allow permissions for certain
fields to be updated.

Ummm: it can't be an existing record if there is no information. At least
there must be a PK value (if there is no PK, then it's not a table and
therefore it's not a record).

I've set permissions to allow users to add new
information but once they get out of the record they can't edit
anything since they are only allowed to add and that won't work.

I assume you mean that you have set the form to DataEntry and nothing else.
There are alternative methods that may suit you better:

Add all new records to a temporary table, which the user can edit, and
append them to the real table at the end of the session.

Add a boolean field Committed. Base the form on a query with a criterion
WHERE Committed = FALSE, and make sure the user can't set it to true by
accident. Make it an admin job to validate the record and set the flag to
TRUE.

Put some code in the OnCurrent event that checks if a record is a new one
or not; if not, then show the user a message asking if they are sure that
they want to edit an old one rather than create a new one.

(My favourite) Analyse your users processes very carefully and find out
what mistakes they are making and why and discuss methods with them of
avoiding them or picking them up sooner, perhaps even before they have
moved off the control. Use AutoCorrect, combo boxes, push buttons and
option groups as much as possible. Make different forms for different
processes -- one will need a search function for going back over previous
records; one will need lots of validation and help for entering new data;
one might be a private form for the admin to flag up errors; and so on.

Also, how can I tell Access to open up in a new record so that
information in an existing record will not get accidentally deleted or
typed over?

Set Data Entry = True?


HTH


Tim F