access security
- Thread starter ariansman
- Start date
well, difficult is not enough. i need it totally blocked and accessible only by the owner or admin. I have already made my file and now i see how insecure is MS Access. is there a way that i change my file into another DB program, such as "oracle" or " file maker"? i dont know much DB programs. any suggestion is appreciated.
thank your
thank your
Frothingslosh
Premier Pale Stale Ale
- Local time
- Today, 09:38
- Joined
- Oct 17, 2012
- Messages
- 3,276
Anything can be hacked.
If you split your database, use a SQL Server back end rather than an Access back end, convert the front end to an MDE/ACCDE file, use AutoKeys to disable F11, use a custom toolbar/ribbon to restrict the commands available to the user, hide the database window, disable special keys, and disable the SHIFT bypass, then your front end will be secure from anyone save Access experts explicitly trying to hack your program, and if you have someone trying to hack your system, you've got bigger problems.
If you need better security than that, or you absolutely 100% need to prevent someone from pulling your empty forms to see how they're built, then you're going to need to switch platforms entirely.
If you split your database, use a SQL Server back end rather than an Access back end, convert the front end to an MDE/ACCDE file, use AutoKeys to disable F11, use a custom toolbar/ribbon to restrict the commands available to the user, hide the database window, disable special keys, and disable the SHIFT bypass, then your front end will be secure from anyone save Access experts explicitly trying to hack your program, and if you have someone trying to hack your system, you've got bigger problems.
If you need better security than that, or you absolutely 100% need to prevent someone from pulling your empty forms to see how they're built, then you're going to need to switch platforms entirely.
- Local time
- Today, 14:38
- Joined
- Sep 12, 2006
- Messages
- 16,048
Actually - queries, yes, you can hide, because you can store the query SQL so that users cannot see it.
tables - sort of - you can put them in a password protected backend database, and make your front end use the password secretly. That may help prevent non-authorised users seeing the data tables.
With regard to tables - why is it a problem for users to see their data, anyway? Most commercial systems expose their data via ODBC Drivers and the like, to facilitate their use. I struggle to see why users need protecting from their own data, to be honest.
I have occasionally worked for companies who wanted to extract data from a proprietary system, and Access is a fair old tool to do that - but you need to be able to link to the tables to do so.
tables - sort of - you can put them in a password protected backend database, and make your front end use the password secretly. That may help prevent non-authorised users seeing the data tables.
With regard to tables - why is it a problem for users to see their data, anyway? Most commercial systems expose their data via ODBC Drivers and the like, to facilitate their use. I struggle to see why users need protecting from their own data, to be honest.
I have occasionally worked for companies who wanted to extract data from a proprietary system, and Access is a fair old tool to do that - but you need to be able to link to the tables to do so.
if they see tables they can simply change data.
Is there a way that we make the “option” to be out of reach of the user or make it password protected? I want the user to be restricted to work through forms and buttons.
Similar threads
