Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

'Sealing' a record.

Discussion in 'Information Technology' started by ChrisLarge, Nov 16, 2005.

  1. ChrisLarge

    ChrisLarge
    Expand Collapse
    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?
     
  2. Loading...


  3. Arvin Meyer [MVP]

    Arvin Meyer [MVP]
    Expand Collapse
    Guest

    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

    "ChrisLarge" <ChrisLarge@discussions.microsoft.com> wrote in message
    news:B889A7E6-EFD5-43E4-866C-883A7795FCAA@microsoft.com...
    > 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?
     
  4. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    ChrisLarge wrote:
    > 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?

    --
    Joseph Meehan

    Dia duit
     
  5. ChrisLarge

    ChrisLarge
    Expand Collapse
    Guest

    Hi Joseph,

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

    from Chris

    "Joseph Meehan" wrote:

    > ChrisLarge wrote:
    > > 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?
    >
    > --
    > Joseph Meehan
    >
    > Dia duit
    >
    >
    >
     
  6. ChrisLarge

    ChrisLarge
    Expand Collapse
    Guest

    Thanks Arvin.

    "Arvin Meyer [MVP]" wrote:

    > 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
    >
    > "ChrisLarge" <ChrisLarge@discussions.microsoft.com> wrote in message
    > news:B889A7E6-EFD5-43E4-866C-883A7795FCAA@microsoft.com...
    > > 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?

    >
    >
    >
     
  7. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    ChrisLarge wrote:
    > 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.

    >
    > "Joseph Meehan" wrote:
    >
    >> ChrisLarge wrote:
    >> > 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?
    >>
    >> --
    >> Joseph Meehan
    >>
    >> Dia duit


    --
    Joseph Meehan

    Dia duit
     

Share This Page