Welcome to SPN

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

Sign Up Now!
  1. Monthly (Recurring) Target: $300 :: Achieved: $95
      Become a Supporter    ::   Make a Contribution   

password to prevent editing of forms

Discussion in 'Information Technology' started by trace, Nov 11, 2005.

  1. trace

    trace
    Expand Collapse
    Guest

    I have a database that many people will be using, I don't need to protect the
    database as a whole with a password. But I want to prevent users from
    editing forms by creating a password. How do I password protect a from for
    editing functions? Thanks in advance.
     
  2. Loading...

    Similar Threads Forum Date
    I became victim by Password hacker Hard Talk May 27, 2012
    Legal Sharing Passwords with Spouse is Risky Breaking News Oct 14, 2011
    Password for Sikhs: "WAHEGURU" ! Spiritual Articles Apr 4, 2006
    How to prevent sikh erosion? Blogs Oct 21, 2015
    Leisure Stomach Protection / Prevention for travelling to India?? Business, Lifestyle & Leisure Oct 18, 2013

  3. Ofer

    Ofer
    Expand Collapse
    Guest

    Let the users use MDE file instead of MDB, that way they wont have the
    ability to change forms, reports, and modules

    Check this link

    http://www.microsoft.com/technet/prodtechnol/office/office2000/proddocs/opg/part4/ch18.mspx

    --
    The next line is only relevant to Microsoft''s web-based interface users.
    If I answered your question, please mark it as an answer. It''s useful to
    know that my answer was helpful
    HTH, good luck


    "trace" wrote:

    > I have a database that many people will be using, I don't need to protect the
    > database as a whole with a password. But I want to prevent users from
    > editing forms by creating a password. How do I password protect a from for
    > editing functions? Thanks in advance.
    >
     
  4. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    trace wrote:
    >I have a database that many people will be using, I don't need to
    > protect the database as a whole with a password. But I want to
    > prevent users from editing forms by creating a password. How do I
    > password protect a from for editing functions? Thanks in advance.


    MDE is likely the best way as Ofer suggested.

    My question is are you using the application over a LAN? If so have you
    split the database. If not you should split the database and give the users
    MDE version (or if you don't care if they mess with their own forms use an
    MDB.

    MDE's are not editable. (The data is, just not the structure)

    Split databases have one front end database for each user on their
    machine that is linked to the data in a back end database on the server. It
    speeds things up and causes far less problems.




    --
    Joseph Meehan

    Dia duit
     
  5. trace

    trace
    Expand Collapse
    Guest

    Thanks. I'm not able to create a .mde because apparently we are using 2000
    here. I tried to convert to 2002/2003 but that didn't work, either. I
    suppose I'll just proceed with front/back end. Thanks again.


    "Joseph Meehan" wrote:

    > trace wrote:
    > >I have a database that many people will be using, I don't need to
    > > protect the database as a whole with a password. But I want to
    > > prevent users from editing forms by creating a password. How do I
    > > password protect a from for editing functions? Thanks in advance.

    >
    > MDE is likely the best way as Ofer suggested.
    >
    > My question is are you using the application over a LAN? If so have you
    > split the database. If not you should split the database and give the users
    > MDE version (or if you don't care if they mess with their own forms use an
    > MDB.
    >
    > MDE's are not editable. (The data is, just not the structure)
    >
    > Split databases have one front end database for each user on their
    > machine that is linked to the data in a back end database on the server. It
    > speeds things up and causes far less problems.
    >
    >
    >
    >
    > --
    > Joseph Meehan
    >
    > Dia duit
    >
    >
    >
     
  6. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    trace wrote:
    > Thanks. I'm not able to create a .mde because apparently we are
    > using 2000 here. I tried to convert to 2002/2003 but that didn't
    > work, either. I suppose I'll just proceed with front/back end.
    > Thanks again.


    If you like, you can start a new topic about the MDE problem and maybe
    someone will have an answer for you on that one.

    In any case I do suggest you use the split database. Access has a
    wizard to help you do the splitting. As always make a copy first.

    >
    >
    > "Joseph Meehan" wrote:
    >
    >> trace wrote:
    >> >I have a database that many people will be using, I don't need to
    >> > protect the database as a whole with a password. But I want to
    >> > prevent users from editing forms by creating a password. How do I
    >> > password protect a from for editing functions? Thanks in advance.

    >>
    >> MDE is likely the best way as Ofer suggested.
    >>
    >> My question is are you using the application over a LAN? If so
    >> have you split the database. If not you should split the database
    >> and give the users MDE version (or if you don't care if they mess
    >> with their own forms use an MDB.
    >>
    >> MDE's are not editable. (The data is, just not the structure)
    >>
    >> Split databases have one front end database for each user on
    >> their machine that is linked to the data in a back end database on
    >> the server. It speeds things up and causes far less problems.
    >>
    >>
    >>
    >>
    >> --
    >> Joseph Meehan
    >>
    >> Dia duit


    --
    Joseph Meehan

    Dia duit
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page