accdb security setup

Hello ALL,

I want to upgrade a 2010 .mdb to .Accdb.
i see it doesnt support the .mdw for security setup.
how is it done in the accdb.
Please let me know.
Thanks
LVL 1
frimyAsked:
Who is Participating?
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"how is it done in the accdb."
it's not :-(
You would have to roll your own.
You can ... use an MDB format in >= A2007 ... and ULS is still supported, but not in the ACCDB format.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Peters Software has a product named LASsie (Light Application Security):

http://www.peterssoftware.com/las.htm

It's not a true "security" mechanism (read the page for the details), but it can help with navigation and such. Or, as joe said, you can roll your own.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Highly recommend Peter's app as well !
0
Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

 
John TsioumprisSoftware & Systems EngineerCommented:
Instead of trying to use a deprecated feature is preferred to use your own security settings...just a table that stores credentials and simple login form....you want to make it harder...obfusctate letters/numbers/symbols...want to make it impossible ...just put the encryption method in a compiled Access..  .accde
0
 
frimyAuthor Commented:
thanks for responding

is there a way to use a mdb format in Access 2013 - 2016?
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
A2013-A2016 will open the A2010 MDB format.
And I believe the ULS WorkGroup tool will be on one of the Ribbons.
0
 
mbizupCommented:
As Joe said, your mdb files will open in Access 2013-2016.  However, you will not be able to take advantage of newer capabilities in Access that are only available in .accdb format (some of which are quite useful).
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
And just to be clear: There is no such thing as a "2010 MDB file". You may have used 2010 to create the MDB file, but that is a 2003 (at best) format file. There have been no advancements made in that format since Access 2003.

And realize that at some point Access will stop making newer versions of Access compatible with the .mdb format. You would do yourself a favor by determining why you need ULS, and consider steps to take to implement those needs with the .accdb format.
0
 
frimyAuthor Commented:
Scott,

the mdw work group was a very good feature to control all the objects very easy
what can be replaced in accdb instead to avoid users to open objects in design view?
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I agree that ULS was a good feature in it's day, if used correctly (and it rarely was).

There is no real comparison in the ACCDB format, but you can deploy the .accde format which protects your objects from design changes. That doesn't apply to Tables and Queries - even in a compiled file users can still modify those - but hiding the navigation pane, and taking other steps, can go a long way toward reducing the chances of users messing with your design.

If you want real control over these types of things, you might consider moving your data to a more robust data platform, like SQL Server. You can very tightly control what happens with sql server, so that would take care of the data side. The .accde compiled format would take care of the UI stuff.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"You may have used 2010 to create the MDB file, "
Well that is what I meant, just not stated clearly.
0
 
John TsioumprisSoftware & Systems EngineerCommented:
As mentioned before .ACCDE is near impossible to crack on Forms/Reports/Modules so not worries on design view on them...
If you are concerned about the Table/Queries you could encrypt the data by some simple encryption mechanism like XOR or string replacement (e.g A -->T,B -->Z...you just need a simple character mapping) for Tables and store the Queries SQL to an encrypted table and completely delete them...
0
All Courses

From novice to tech pro — start learning today.