Hiding Query's

[mswhiteside]

Hello All,

I have an Access Database, that i would like to hide all of the query's, and preventing them from being imported by another database. I tried to use the QueryDef's in the same way that you use the TableDef's
( ie. CurrentDb.Table Defs("TableName ").Attributes=d bHiddenObject)
However, it won't allow me to hide the query's.

Anybody have any ideas?

[Curben]

Hello All,

I have an Access Database, that i would like to hide all of the query's, and preventing them from being imported by another database. I tried to use the QueryDef's in the same way that you use the TableDef's
( ie. CurrentDb.Table Defs("TableName ").Attributes=d bHiddenObject)
However, it won't allow me to hide the query's.

Anybody have any ideas?

There are a few options. By selecting the properties of the query you can change them to hidden, however certain actions have been known to unhide queries and tables, also if the users has "view Hidden Controls" selected it will be useless.

Second option is two fold. Use the switchboard, which is found in a few different sections based on what version of access you have. 2000 and later should be located in Tools > Database Utilities > Switchboard Manager
This will make a control panel of sorts that you can have load on startup Tools > Startup

As for creating the security of the switchboard, you have two options, either edit the form template to not display the close buttons, and have the form maximize. Follow up on this by creating a small transparent close button. Otherwise you can deselct a few options in startup as well. If you deselect "Display Database Window" along with the switchboard, most users will only have access to what you put in the switchboard. Once this is done you will need to know a few Overrides to get in yourself.
F11 = Display the Database Window
Hold shift during bootup = will completely bypass all startup options

Combine these with a secure DB and you have almost Total control over who has what access (and thus who can break) to your DB

[FishVal]

Hi, there.

What about simple locking db with password?

[mswhiteside]

Thanks for the quick response guys. The problem i have run into is that there are a bunch of people that need to get into the database, and most of them know that you can hold the shift key down to bypass all startup commands. Also i have discovered that people will just create a new database, and import everything, which more or less gives them full access. I got around this by hiding the tables through the code i showed earlier. This makes it where you can't see the table, or import the table from another database, however when i tried to do the same with the query, it wouldn't let me do it. I was hoping there was a way to hide the query's in the same way i hid the tables. I haven't put a database password on it because i didn't want to log in everytime i wanted to make an update to the database. Recently i've had to make updates to it daily

[Curben]

Thanks for the quick response guys. The problem i have run into is that there are a bunch of people that need to get into the database, and most of them know that you can hold the shift key down to bypass all startup commands. Also i have discovered that people will just create a new database, and import everything, which more or less gives them full access. I got around this by hiding the tables through the code i showed earlier. This makes it where you can't see the table, or import the table from another database, however when i tried to do the same with the query, it wouldn't let me do it. I was hoping there was a way to hide the query's in the same way i hid the tables. I haven't put a database password on it because i didn't want to log in everytime i wanted to make an update to the database. Recently i've had to make updates to it daily

Most of this could be resolved with the appropriate security settings. While shift may get past startup, it isnt as easy to bypass access security. If you setup security the right way it is able to deny a few of the things your users are doing. Also, with security, if you wish you can create a shortcut that includes your username and password to log you in directly (assuming you are not using a shared workstation)

Use this as the example target in your shortcut

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "\\127.0.0.1\CompanyServer\Project\Project.mdb" /wrkgrp "\\127.0.0.1\CompanyServer\Poject\ProjectFiles\Security\Project_SEC.mdw" /User "Itsme" /Pwd "Letmein"

If you need clarification let me know

[missinglinq]

This sounds like more of a policies thing than security!

First, why in the world do the people that "need access" to this database feel the need to import everything into thier own database rather than use the etstablished db? Are they having trouble gaining access? Do you need to split it into a front/end backend app so that multiple users can use it at the same time? Is it running unusually slow?

Secondly, a corporate database is a corporate asset; people doing unauthorized things to it, including importing objects into their "own" database, are misusing those assets! It's no different than taking a company vehicle for an unauthorized spin to Vegas for the weekend, and should be dealt with in the same way!

Ultimately, if your users have the talent, little you can do will keep them from messing around in your database. What man can devise man can hack! The answer lies, I think, in resolving the issues that underline the problem and/or letting it be known that unauthorized use is against company policy and will be dealt with accordingly.

Welcome to TheScripts!

Linq :0)>