what options do i have to protect my work?

[fdelval]

Hello,
I have a server-client access databases setup.

SERVER.mdb has 3 tables and 3 reports with custom code.

client1.mdb
client2.mdb
client3.mdb
clients link that 3 tables and uses forms and querys.


I have never worked with extra security but, now i must use it.

1)
How can i secure my clients?
I only know to "hide" the database window, so users only interact with the forms, but they learned to open it with the SHIFT key pressed.

2)
How can i secure the server?
If the server is shared, users can browse to its folder.
If the delete the Write permissions for it, so nobody can delete it, users cant write...


So, what options can i use?

thanks in advance

 

[boblarson]

1. You can disable the Shift key bypass by using code here:
http://www.access-programmers.co.uk/forums/showthread.php?t=51479

1a. Also uncheck the USE ACCESS SPECIAL KEYS in the startup options so that F11 can't bring up the database window/navigation pane.


2. You will not be able to keep users from deleting the backend. That is why backups are important and your IT folks should be backing the server up every night.

3. If you absolutely need better security, then you should move to SQL Server Express.

 

[fdelval]

1. You can disable the Shift key bypass by using code here:


1a. Also uncheck the USE ACCESS SPECIAL KEYS in the startup options so that F11 can't bring up the database window/navigation pane.


2. You will not be able to keep users from deleting the backend. That is why backups are important and your IT folks should be backing the server up every night.

3. If you absolutely need better security, then you should move to SQL Server Express.

Hello Bob,
Fast and usefull answer, i appreciate it.
Well, im really working to move to mysql, and work with linked tables, but nowdays i cant.
Just to make it clear, "You will not be able to keep users from deleting the backend" with backend you mean what i called the SERVER.mdb file , right?

I will give the shift fix a try, but, if i disable the shift key, is there any other workaround to bring the db window up? i dont want to be locked with no control over the db window.

Maybe i should investigate on USERS ACCOUNTS too..

thank you sir.

 

[boblarson]

Just to make it clear, "You will not be able to keep users from deleting the backend" with backend you mean what i called the SERVER.mdb file , right?

Yes, that's what I mean.

I will give the shift fix a try, but, if i disable the shift key, is there any other workaround to bring the db window up? i dont want to be locked with no control over the db window.

You can connect to your database through another one and then Enable Bypass Key. Do a Google search on Enable Bypass Key.

Maybe i should investigate on USERS ACCOUNTS too..

I wouldn't as those go away in the newer Access 2007 format.

 

[fdelval]

Yes, that's what I mean.

You can connect to your database through another one and then Enable Bypass Key. Do a Google search on Enable Bypass Key.


I wouldn't as those go away in the newer Access 2007 format.

Copy that,
I ended up with the app to remotely enable/disable the SHIFT key.
But, going further, i thought that any user could google the SHIFT key and find a solution; download the remote app and enable the key.

So, i used this one:

databasedev.co.uk/disable_shift_bypass.html
(i cant post links, so i deleted the www . )

Now, you must know the password to enter in design mode.
Unless you have got it, you are done.

I can see more benefits using this way, what do you think?

 

[boblarson]

I can see more benefits using this way, what do you think?

I think that's a great idea.