How do I compile(run) an access program ?

[Guest]

that is my first program in access. I want to be admin of this program, and
users only fill in the blank of form question and see the result of their
search from report. (In my program's form part have some buttons when the
user click one of them they can see the reports in word doc.) When i need to
change the design or database of program, only i can do it ?
can you help me?

 

[Billy]

You will have to be more specific. You can protect forms and reports
against modification, deny permission to open forms and so on. First
you have to change Login password for Admin in "Tools|Security|User and
Group Accounts|Change Logon Password". You can also create MDE file.
That way you prevent anyone to modify forms or reports, including you.
HTH
Billy

 

[Lynn Trapp]

against modification, deny permission to open forms and so on. First

you have to change Login password for Admin in "Tools|Security|User and
Group Accounts|Change Logon Password".

Billy,
That is actually the third thing that needs to be done to properly secure
Access. Please check the following webpage:

http://www.ltcomputerdesigns.com/The10Steps.htm

 

[Billy]

I agree with you Lynn, but in my opinion for the beginner in Access
this is maybe easier task and then explore further. And as I said he
need to describe more specific what kind of protection he need.
For just usual protection will be already enough to set psw for Admin,
add new user, set permissions for that user. If that new "user" doesn't
program in Access and hack PC's that will be more then enough.

 

[Rick Brandt]

I agree with you Lynn, but in my opinion for the beginner in Access
this is maybe easier task and then explore further. And as I said he
need to describe more specific what kind of protection he need.
For just usual protection will be already enough to set psw for Admin,
add new user, set permissions for that user. If that new "user"
doesn't program in Access and hack PC's that will be more then enough.

No, all he will have to do is use a different MDW file and he will get right in.
This would even be a likely thing to happen by accident on the users part.

There is no way to do Access security except the correct way. Anthing else and
you're wasting your time.

 

[Lynn Trapp]

Following your approach he would do one of 2 things -- (1) Not have any
security at all or (2) completely lock everybody, including God, out of his
database. Access security needs to be done right or not done at all.

 

[Lynn Trapp]

Amen!

 

[Billy]

What about if you protect your project with password for viewing and
save it as MDE file? Is then your code and forms safe against
modification and looking inside? Here I mean that I still didn't change
workgroup file or modify any persmission for users.

 

[Lynn Trapp]

The MDE file is a good idea and something you should always, or nearly
always, do when you distribute an application to a client. However, a
database password is worthless and I would drop the idea if I were you. It
can be hacked into in almost no time.

 

[Billy]

I don't know if we talk about the same password. I mean password in VBA
editor under Tools|prjName Properties...|Protection. Password on db is
worthless because you can revail it with code you have on your
homepage.

If previous is correct thinking can we say then that using psw in VBA
and save front-end file as MDE will be enough to protect your app. Or
is still any risk there?

If that is enough protected why then we still need separate MDW file if
we assume that all users have access to all data in the db?

 

[Rick Brandt]

I don't know if we talk about the same password. I mean password in
VBA editor under Tools|prjName Properties...|Protection. Password on
db is worthless because you can revail it with code you have on your
homepage.

If previous is correct thinking can we say then that using psw in VBA
and save front-end file as MDE will be enough to protect your app. Or
is still any risk there?

If that is enough protected why then we still need separate MDW file
if we assume that all users have access to all data in the db?

If you allow all users access to all data then there _is_ little need to
implement Access Security. That has always been mostly about protecting the
*data*.

Also if you distribute an MDE then putting password on the VBA project is
redundent since it is already impossible to look at or change the code in an MDE
file.

 

[Tom Wickerath]

Lynn,

I think Cheryl Fischer would have God back into the database in no time....


Tom
__________________________________


Following your approach he would do one of 2 things -- (1) Not have any
security at all or (2) completely lock everybody, including God, out of his
database. Access security needs to be done right or not done at all.

 

[Lynn Trapp]

Ah, Tom, now I believe you are quite right there.