AllowByPassKey No Use Security

[FuzMic]

Hi forum mates

I just learnt that one can easily overcome the AllowByPassKey via one product in the market. This totally defeat the purpose of this property. I was relying on this to protect a table in the .mde but it is now so transparent. Is there a way to block this?? I

 

[Poppa Smurf]

Right click on the table then select table properties then tick Hidden in the Attributes

 

[FuzMic]

Sorry Pop this will not really work as user can get to the option menu, then select 'show all hidden objects', from that point, one can unhide the table. Hence still

 

[JANR]

Keeping users out of tables in access isen't easy. This discussion from UtterAccess: http://www.utteraccess.com/forum/Access-2007-security-t1242310.html gives you some idea on a possible solution. It is a lenghty thread.

95 % of user don't really care about how things works behind the scenes only that it works, the rest of the curious users, educate them NOT to snoop around or they will be fired!!!

If securety is that important then SQLServer is probably your best option.

JR

 

[Poppa Smurf]

In your database options set your options not to display the full menu and objects. In 2007 you do not display the navigation pane and do not display the menus (ribbons). Set your startup form as required. Then convert to mde or accde. In 2003 from memory I think it is Tools then Options.

 

[John.Woody]

You could install a runtime version of access on you're users PCs. This would stop users getting to tables and queries. You would need to address other issues using custom menus and toolbars and get on top of error reporting.

 

[FuzMic]

John & Pop: Understand what u suggest but i really looking for some more fail proof stops to protect password tables without using SQL Server.
JanR's link to utteraccess is some of the paths i would consider interesting.

Behind my annoyance of the openly available reversal of the AllowBypassKey is the uncontrolled use of Option that eventually leads to exposing all your password tables that one "dreams" of protecting.

 

[Poppa Smurf]

John & Pop: Understand what u suggest but i really looking for some more fail proof stops to protect password tables without using SQL Server

Have you looked at setting the Input Mask of the relevant text fields to PASSWORD?

 

[DCrake]

Setting the input mask to Password only works if you are using Access to vie the records. If you analyse a table in Excel that has fields with input masks as Password Excel does not carry over the encryption it simply displays the contents, so not a good option.

 

[FuzMic]

Thanks Pop & DCrake

What i am really trying is do is to hide 'totally unsecured' Connection string in the system tables.

By the way how do one use VB to ensure that system objects are default to being hidden. The following link shows all the currentdb.properties(???) but there is none on hiding system objects.

http://blog.vishalon.net/index.php/...rties-available-through-currentdb-properties/

Guru help!!

 

[FuzMic]

Just to follow up

I just found the way to ensure the system objects are always hidden. It is by way of Application.SetOption "Show System Objects", False.

Meanwhile still hoping that reversal of AllowBypassKey can be permanently secured. Is there a way to tinker the bits in the .mde?

 

[Poppa Smurf]

Have a look in the Help file for AllowBypassKey Property. This will give you an example how to set the property to FALSE.

I have a database that I use to set various properties of a database in 2003. The bypass key setting works in 2007. If you want to tinker with this database reply to my email address below and I will send you a copy.

 

[ghudson]

Have a look in the Help file for AllowBypassKey Property. This will give you an example how to set the property to FALSE.

I have a database that I use to set various properties of a database in 2003. The bypass key setting works in 2007. If you want to tinker with this database reply to my email address below and I will send you a copy.

As the original poster has questioned, you can externally turn the AllowBypassKey property on or off. As this sample will do >>> ByPass Shift Key Utility for Access
You have to be a member of UtterAccess to open/download the ByPass Shift Key Utility for Access file.

 

[FuzMic]

Thanks to all the new advices. I feel i might have mislead some of you of my concern. At the start of this thread I wrote

"I just learnt that one can easily overcome the AllowByPassKey via one product in the market."

From the start I was able to Set AllowByPassKey and once it becomes a .mde, i was hoping that users cannot reverse this setting, hence this thread.

Let me rephrase my question

How can one permanently keep the AllowByPassKey setting in a .mde and disallow user from reversing it?