Z
Zlatko Matiæ
How to be 100 % sure that no user can see content of database window
(tables, queries, modules) ? Especially in .mde...
(tables, queries, modules) ? Especially in .mde...
R
Rick Brandt
Zlatko Matiæ said:
For 100% you would have to not give them the file at all. : )
You would have to secure the file with Access User Level Security, set the
option in startup to hide the db window, set the option in startup to disable
"special" keys, And then run some code (one time) to disable the use of the
shift key while opening the file.
The last option is where security comes in. If ULS is in place you can execute
that code in a manner such that only a user with admin permissions would be able
to execute a similar line of code to restore the shift key ability. Without ULS
anyone who knows how would be able to change that setting.
Of course Access security is breakable by anyone who knows how to use Google and
is willing to spend a few bucks which is why you cannot achieve the 100% you are
asking for.
Bottom line... if you want to protect data from "users" then it doesn't belong
in an MDB file.
Z
Zlatko Matiæ
Hi, Rick!
Thanky you for answer.Just to say, I have Access 2003 .mde, and I set
startup options to disable special keys, also I disabled database window in
startup options.
Nevertheless, database window sometimes appears just prior closing. I didn't
have enough time to explore what is the reason, but obviously there is a
problem with security of my application.
As there is back-end in PostgreSQL (ODBC linked tables and pass-through
queries) with it's own security, I would like to avoid using Access
security, because the there will be two different security systems then,
which I don't know how to synchronize...Is that what I need to do ?
Greetings,
Zlatko
Thanky you for answer.Just to say, I have Access 2003 .mde, and I set
startup options to disable special keys, also I disabled database window in
startup options.
Nevertheless, database window sometimes appears just prior closing. I didn't
have enough time to explore what is the reason, but obviously there is a
problem with security of my application.
As there is back-end in PostgreSQL (ODBC linked tables and pass-through
queries) with it's own security, I would like to avoid using Access
security, because the there will be two different security systems then,
which I don't know how to synchronize...Is that what I need to do ?
Greetings,
Zlatko
A
Albert D.Kallal
You can quite well lock up the ms-access interface, and you don't have to
use security to do this.
Try downloading and running the 3rd example here:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm
(the ms-access interface hidden example). Note how all of ms-access is
hidden, and NO code and NO security was needed. (just the tools->startup
settings).
The only steps to lock up the above would be to convert it to a mde, and
then disable the shift key by-pass. I have a sample utility for shift key
here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html
use security to do this.
Try downloading and running the 3rd example here:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm
(the ms-access interface hidden example). Note how all of ms-access is
hidden, and NO code and NO security was needed. (just the tools->startup
settings).
The only steps to lock up the above would be to convert it to a mde, and
then disable the shift key by-pass. I have a sample utility for shift key
here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html
Z
Zlatko Matiæ
Thank you for your help.
I have made .mde, included some code to prevent database window opening and
disabled bypass-key (shift).
I read that someone can't import module, form or report from a .mde file,
but can import tables and queries, so
I have to solve how to disable importing tables and queries from my database
to some other database. Do you have any solution for that ?
Thanks.
I have made .mde, included some code to prevent database window opening and
disabled bypass-key (shift).
I read that someone can't import module, form or report from a .mde file,
but can import tables and queries, so
I have to solve how to disable importing tables and queries from my database
to some other database. Do you have any solution for that ?
Thanks.
A
Albert D.Kallal
I have to solve how to disable importing tables and queries from my
Hum, no, not really. You could setup security, but at the end of the day, it
is should not be a big deal that someone can import the quires and table
defs.
At the end of the day, if you need the data to be secure, then move the data
to true database server, and require rights and logons to that database. The
fact that some users can import the queries and table defs form your mde
file is really moot. This in no way gives away your application, or allows
them to modify the forms and the valuable code logic that you write.
You certainly could setup a logon prompt and then use this logon stuff to
setup the links in tables so they connect to sql server. I mean, if you
give a password and logon to your sql server, then what stops the uses from
grabbing that data with Excel?
If you need to hide your code and forms, then use a mde. If you need to
secure the data, then put the data on sql server, or the server of your
choice. However, it is going to be up to you how much rights you give each
user to that server. In most cases, if your uses edit that data on the
server, then the users can copy it.
It is not clear if you are trying to protect the data on the server, or your
appliation?
Hum, no, not really. You could setup security, but at the end of the day, it
is should not be a big deal that someone can import the quires and table
defs.
At the end of the day, if you need the data to be secure, then move the data
to true database server, and require rights and logons to that database. The
fact that some users can import the queries and table defs form your mde
file is really moot. This in no way gives away your application, or allows
them to modify the forms and the valuable code logic that you write.
You certainly could setup a logon prompt and then use this logon stuff to
setup the links in tables so they connect to sql server. I mean, if you
give a password and logon to your sql server, then what stops the uses from
grabbing that data with Excel?
If you need to hide your code and forms, then use a mde. If you need to
secure the data, then put the data on sql server, or the server of your
choice. However, it is going to be up to you how much rights you give each
user to that server. In most cases, if your uses edit that data on the
server, then the users can copy it.
It is not clear if you are trying to protect the data on the server, or your
appliation?
Z
Zlatko Matiæ
Right, because I want to do both
)
Anyway, thank you for help.
)Anyway, thank you for help.