Locking Access in Access?

AC5FF

Registered User.
Local time
Today, 12:52
Joined
Apr 6, 2004
Messages
552
Sorry, couldn't resist the pun...

I spent half my morning chasing down problems in my DB this morning. What appears to have happened is some key data from one of the tables was deleted. Only 5 rows out of 200 or so, and only one field, but that field is a highly linked to field to keep everything linked together.

I have no way of knowing who/when/how this was done. I guess it 'could' have been a network error?? Frankly I'm not ready to spend the hours it would take to find the culprit.

Is there a way to password protect who can access/see the Navigation Pane? Or a better way to restrict access?

I've tried to 'split' my DB several times now without luck. It never seems to work. I am still working on that aspect, but frankly again I don't have the time to dig. I would love to post a copy of the DB here, but it's 65meg after a compact/repair; plus management said I 'can't ' send it out due to data it contains... :(

Ideas?
 
Couple options:
1. Put in a folder where authorized users can access
2. Create a table within the Access DB and make it a system table (MsysUser) so that the table doesn't display. In the table, you can authorized users and check against their login (Windows Current User) to see if the person has property permission or not. If not, exit the database.
3. Create security for your database
4. You can hide all of the ms access menu bars, tool bars, etc... and create a special tool bar for your application.
5. Sounds like you are way to busy (sort of like me) to take care of the data. Give it to someone that has a little bit more time so that it's off your shoulder.
 
With Microsoft Access Security features you can restrict Users from adding, editing or deleting records. Field level security is possible on Forms by checking the current User's Workgroups and locking important fields from his reach. Removing Built-in Menus, Toolbars and replacing with Custom Toolbars with only selected options also will be necessary.

But to do these things you must learn Microsoft Access Security implementation. This may take some time to master it.

If you have the time, take a look at the following link as a starting point:

http://www.msaccesstips.com/2006/11/microsoft-access-security.shtml
 
Thanks for the tips all... This is something that DEFINATLY needs to be done. But.... :p

After I wrote this post I walked down the hall to inform my boss what I had discovered. About half way there it clicked... Yesterday afternoon I was writing a new query, trying to bump an excel sheet against our database. Everything worked there, so I decided to write another one, to update the excel sheet (imported as a table) with common names we use for each part. I 'thought' I wrote the update query right, but nothing updated in the table like I wanted... It turns out the 5 rows were the data was gone was the 5 matches from the excel database! It was all MY fault!!! LOLOL
Maybe I need to 'protect' the DB against myself?!? :p
 
Thanks for the tips all... This is something that DEFINATLY needs to be done. But.... :p

After I wrote this post I walked down the hall to inform my boss what I had discovered. About half way there it clicked... Yesterday afternoon I was writing a new query, trying to bump an excel sheet against our database. Everything worked there, so I decided to write another one, to update the excel sheet (imported as a table) with common names we use for each part. I 'thought' I wrote the update query right, but nothing updated in the table like I wanted... It turns out the 5 rows were the data was gone was the 5 matches from the excel database! It was all MY fault!!! LOLOL
Maybe I need to 'protect' the DB against myself?!? :p

It is called BACKUPS and proper testing!

You should do a back up befor you start. You should also be testing and developing on a COPY of the back end.

I am not sure why you are having so much trouble splitting your database. I will only work on a split database. I start all my split and keep then that way.

I am splitting databases regularly for clients and I usually have it done in less than 15 minutes (I do not normally use the splitter wizard).
 
HiTechCoach

Just curious; how much do you normally charge to 'split' a DB?
 
Create two empty db, Import the tables into one (backend) , import everything else into the other (Frontend). Then LINK the tables from the Backend to the Frontend. Less 5 mins work.
 
seriously its a five minute job, but you need an understanding of what you are trying to achieve

basically just copy your database

in one, delete all the tables

in the same dbs then do file/external data/link

navigate to the other copy, and select all the tables

done!

the dbs with the actual tables should be on a server (backend)
every user should have their own copy of the linked database (frontend)

there are a number of utilities around to manage relinking and distribution of the front ends, but the above is all they do
 

Users who are viewing this thread

Back
Top Bottom