preventing user to access/see/import/linking tables

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • thread
    #1

    preventing user to access/see/import/linking tables

    hi all,

    i'm searching the most secure way to prevent users from able to
    approach tables in a mdb file
    any ideas?
    Tags: None
    • Tom van Stiphout
      #2
      Re: preventing user to access/see/import/linking tables

      On Tue, 12 Feb 2008 03:13:10 -0800 (PST), thread <yaniv.dg@gmail .com>
      wrote:

      The most secure, albeit not perfectly secure, way is to use Workgroup
      Security. Phased out in A2007, so that should tell you something.
      If you want real security, SQL Server can provide it, including the
      free Express edition.

      -Tom.

      >hi all,
      >
      >i'm searching the most secure way to prevent users from able to
      >approach tables in a mdb file
      >any ideas?

        Comment

        • Fred Zuckerman
          #3
          Re: preventing user to access/see/import/linking tables

          "Tom van Stiphout" <no.spam.tom774 4@cox.netwrote in message
          news:fjr4r3dcr5 a1nesmifpghflmq eq0muuq52@4ax.c om...
          On Tue, 12 Feb 2008 03:13:10 -0800 (PST), thread <yaniv.dg@gmail .com>
          wrote:
          >
          The most secure, albeit not perfectly secure, way is to use Workgroup
          Security. Phased out in A2007, so that should tell you something.
          If you want real security, SQL Server can provide it, including the
          free Express edition.
          >
          -Tom.
          >
          ..mdw is phased out in A2007???
          Is there an alternative?
          Is it backwards compatible with A2k?
          tks,
          Fred Zuckerman


            Comment

            • Tom van Stiphout
              #4
              Re: preventing user to access/see/import/linking tables

              On Tue, 12 Feb 2008 20:29:27 -0800, "Fred Zuckerman"
              <ZuckermanF@sbc global.netwrote :

              Yes. You can still run it, but not create it.

              I am writing code to check with Active Directory as to who is a member
              of what group.

              Define "it".

              -Tom.

              >"Tom van Stiphout" <no.spam.tom774 4@cox.netwrote in message
              >news:fjr4r3dcr 5a1nesmifpghflm qeq0muuq52@4ax. com...
              >On Tue, 12 Feb 2008 03:13:10 -0800 (PST), thread <yaniv.dg@gmail .com>
              >wrote:
              >>
              >The most secure, albeit not perfectly secure, way is to use Workgroup
              >Security. Phased out in A2007, so that should tell you something.
              >If you want real security, SQL Server can provide it, including the
              >free Express edition.
              >>
              >-Tom.
              >>
              >
              >.mdw is phased out in A2007???
              >Is there an alternative?
              >Is it backwards compatible with A2k?
              >tks,
              >Fred Zuckerman
              >

                Comment

                • Larry Linson
                  #5
                  Re: preventing user to access/see/import/linking tables

                  As far as I know, Access security is still available for MDB files created
                  in Access 2007, but not for the new ACCDB file format. You are supposed to
                  use the security provided by SharePoint or by the server database you are
                  using as a back-end. If you are using ACCDB as a back-end, no security is
                  supported.

                  In the past, I've worked on Access client applications, to which we applied
                  Access security, with server DB back ends, in which we applied the server
                  DB's security. Now, it seems, only the server's security can be used.

                  Larry Linson
                  Microsoft Office Access MVP


                  "Fred Zuckerman" <ZuckermanF@sbc global.netwrote in message
                  news:Pjusj.145$ Mw.58@nlpi068.n bdc.sbc.com...
                  "Tom van Stiphout" <no.spam.tom774 4@cox.netwrote in message
                  news:fjr4r3dcr5 a1nesmifpghflmq eq0muuq52@4ax.c om...
                  >On Tue, 12 Feb 2008 03:13:10 -0800 (PST), thread <yaniv.dg@gmail .com>
                  >wrote:
                  >>
                  >The most secure, albeit not perfectly secure, way is to use Workgroup
                  >Security. Phased out in A2007, so that should tell you something.
                  >If you want real security, SQL Server can provide it, including the
                  >free Express edition.
                  >>
                  >-Tom.
                  >>
                  >
                  .mdw is phased out in A2007???
                  Is there an alternative?
                  Is it backwards compatible with A2k?
                  tks,
                  Fred Zuckerman
                  >
                  >

                    Comment

                    • thread
                      #6
                      Re: preventing user to access/see/import/linking tables

                      On 13 פברואר, 08:01, "Larry Linson" <boun...@localh ost.notwrote:
                      As far as I know, Access security is still available for MDB files created
                      in Access 2007, but not for the new ACCDB file format. You are supposed to
                      use the security provided by SharePoint or by the server database you are
                      using as a back-end.  If you are using ACCDB as a back-end, no security is
                      supported.
                      >
                      In the past, I've worked on Access client applications, to which we applied
                      Access security, with server DB back ends, in which we applied the server
                      DB's security.  Now, it seems, only the server's security can be used..
                      >
                       Larry Linson
                       Microsoft Office Access MVP
                      >
                      "Fred Zuckerman" <Zuckerm...@sbc global.netwrote in message
                      >
                      news:Pjusj.145$ Mw.58@nlpi068.n bdc.sbc.com...
                      >
                      >
                      >
                      "Tom van Stiphout" <no.spam.tom7.. .@cox.netwrote in message
                      news:fjr4r3dcr5 a1nesmifpghflmq eq0muuq52@4ax.c om...
                      On Tue, 12 Feb 2008 03:13:10 -0800 (PST), thread <yaniv...@gmail .com>
                      wrote:
                      >
                      The most secure, albeit not perfectly secure, way is to use Workgroup
                      Security. Phased out in A2007, so that should tell you something.
                      If you want real security, SQL Server can provide it, including the
                      free Express edition.
                      >
                      -Tom.
                      >
                      .mdw is phased out in A2007???
                      Is there an alternative?
                      Is it backwards compatible with A2k?
                      tks,
                      Fred Zuckerman-הסתר טקסט מצוטט-
                      >
                      -הראה טקסט מצוטט-
                      so if i understand correctly,there is no option to secure ACCESS
                      within its functionalities but only by outsource softwares

                        Comment

                        Previous template Next
                        Working...