'Sealing' a record.

[Guest]

We are creating a database for telesales. When the operators have finished
entering the details on a record we want to 'seal' the record so it cannot be
edited again. Does anyone know a way of doing this?

 

[Arvin Meyer [MVP]]

Aircode:

Sub Form_Current()
If Me.NewRecord = False Then
Me.AllowEdits = False
Else
Me.AllowEdits = True
End
End Sub

This will lock the form, but not the underlying tables. To do that, you must
implement User-Level security and create and MDE. That will keep out all but
the most determined users. If you have a user who even tries to break into
the database, fire them as they are untrustworthy. Have a look at the
Security FAQ for more details:

http://download.microsoft.com/download/access97/faq1/1/win98/en-us/secfaq.ex
e
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Joseph Meehan]

We are creating a database for telesales. When the operators have
finished entering the details on a record we want to 'seal' the
record so it cannot be edited again. Does anyone know a way of doing
this?

Do you need to protect the record from accidental edits or from
intentional edits?

 

[Guest]

Hi Joseph,

Thanks for your response. It is to protect from accidental edits.

from Chris

 

[Guest]

Thanks Arvin.

Aircode:

Sub Form_Current()
If Me.NewRecord = False Then
Me.AllowEdits = False
Else
Me.AllowEdits = True
End
End Sub

This will lock the form, but not the underlying tables. To do that, you must
implement User-Level security and create and MDE. That will keep out all but
the most determined users. If you have a user who even tries to break into
the database, fire them as they are untrustworthy. Have a look at the
Security FAQ for more details:

http://download.microsoft.com/download/access97/faq1/1/win98/en-us/secfaq.ex
e
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Joseph Meehan]

Hi Joseph,

Thanks for your response. It is to protect from accidental edits.

from Chris

Good, then you have a good solution provided by Arvin.