hidden database window needs to remain hidden

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a way to permanently hide the database window except for certain
users? Also, I need to develop a security scheme that is unique for each
user and specific to each table. Can the security wizard handle that? If
so, how should I go about setting it up?
 
Is there a way to permanently hide the database window except for certain
users? Also, I need to develop a security scheme that is unique for each
user and specific to each table. Can the security wizard handle that? If
so, how should I go about setting it up?
Click to expand...

I recommend that you do not use the security wizard, but instead secure
the database manually. The wizard in most versions will miss an important
step or two and will thus leave a hole in your security scheme unless you
plug it. The most important reason I believe to secure it manually is that
the wizard takes the "knowledge" away from you. While the wizard will
make the process *easier*, you completely miss out on *understanding*
what it is doing behind the scenes. Many, many people have made the
mistake of just jumping into Access security by letting the wizard run the
show. Then when everything begins to stop working, all your users demand
their money back because of a poor show. Trust me on this, read some of
the past posts in this group. Learn the process and you will save yourself
a lot of headaches down the road.

Here is some past information by me which should help you tackle
this issue.The only way to do this is to implement full blown Access User Level
Security (ULS). You would then deny all permissions on the tables
themselves and create RWOP queries for the users to access the table
information. Assigning appropriate permissions to various database objects
would also be needed.

You could also distribute MDE files (a good idea anyway) which would
prevent tampering with your code and prevent importing of forms, macros,
reports, and modules.

In addition you should create custom menu bars and toolbars to limit
what the users can do. Check under Tools | Startup and set limited
startup properties for your users. Hide the Database Window, select
a startup form, uncheck Allow Special Keys, etc. You may also want
to disable the Shift key bypass for those users who like to mess with things.
Details on that technique can be found here:

http://www.mvps.org/access/modules/mdl0011.htm

http://www.mvps.org/access/general/gen0040.htm

If you have never used ULS before, be prepared for a lot of work ahead
of you. ULS is not a trivial undertaking at all so I would recommend
ALL of the following reading material before beginning. Also, practice
on dummy databases until you are really comfortable with it.

http://www.ltcomputerdesigns.com/JCReferences.html#SecurityGood luck,
 
Thanks,

I have been practicing on a copy of my database... I also put the following
post for the group. I don't really want to get into ULS, I'd rather handle
it be using logical business groups for each type of job an employee can do,
but the owners wanted me to look at user level security thinking it would be
easier for them to manage. We'll be going with using groups for various
activities, however, I'm still having some issues.

I am hiding the database window on startup, but I didn't disable the Shift
key bypass or uncheck Allow Special Keys. I'll check these out.


Thanks.
 
Thanks,

I have been practicing on a copy of my database... I also put the following
post for the group. I don't really want to get into ULS, I'd rather handle
it be using logical business groups for each type of job an employee can do,
but the owners wanted me to look at user level security thinking it would be
easier for them to manage. We'll be going with using groups for various
activities, however, I'm still having some issues.
Click to expand...

Your owners are wise people, trust me.
Taking the time to learn ULS and implementing it *properly* will provide
you with more increased database security and less accidental "screw-ups."
There is no reason you cannot mesh ULS with your logical business groups.
For example, you could create a Group for each type of job an employee
can do and just make the employees members of whatever groups they
need to belong to.

If you are still somewhat of a beginner on the subject, you may seem a
bit overwhelmed at the moment by all the information. Keep studying,
read posts in this newsgroup, and the concepts will be begin to sink in.
Once you really understand the process, ULS becomes a very valuable
tool in your arsenal. With that knowledge you can then take control
and make it sing and dance for you.

Best advice I can give to you at this moment is to politely tell your
owners that you are studying up on the subject, but to be patient
as you learn everything. This will not come overnight, and they
need to give you a little time to set up everything correctly.
I am hiding the database window on startup, but I didn't disable the Shift
key bypass or uncheck Allow Special Keys. I'll check these out.
Click to expand...

Your requirements will be dictated by your users. If you have users who
have a lot of Access knowledge and like to mess with things, then
you need to lock things down tight.

Keep studying and do not hesitate to post back with questions if
you have problems. We're here to help.

Good luck,
 
That's exactly what my plan is... thanks.

Jeff Conrad said:
Your owners are wise people, trust me.
Taking the time to learn ULS and implementing it *properly* will provide
you with more increased database security and less accidental "screw-ups."
There is no reason you cannot mesh ULS with your logical business groups.
For example, you could create a Group for each type of job an employee
can do and just make the employees members of whatever groups they
need to belong to.

If you are still somewhat of a beginner on the subject, you may seem a
bit overwhelmed at the moment by all the information. Keep studying,
read posts in this newsgroup, and the concepts will be begin to sink in.
Once you really understand the process, ULS becomes a very valuable
tool in your arsenal. With that knowledge you can then take control
and make it sing and dance for you.

Best advice I can give to you at this moment is to politely tell your
owners that you are studying up on the subject, but to be patient
as you learn everything. This will not come overnight, and they
need to give you a little time to set up everything correctly.


Your requirements will be dictated by your users. If you have users who
have a lot of Access knowledge and like to mess with things, then
you need to lock things down tight.

Keep studying and do not hesitate to post back with questions if
you have problems. We're here to help.

Good luck,
Click to expand...
 
Back
Top