How to make program or any permission so once data saved into ms-acces database "user" cannot modify the records.
If any1 have the idea please share.
thanks
8 Replies - 166 Views - Last Post: 15 January 2013 - 11:37 AM
#1
Once data inserted into ms-access database it should not updateable
Posted 14 January 2013 - 11:52 PM
Replies To: Once data inserted into ms-access database it should not updateable
#2
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 07:50 AM
Modify it through your app or modify it through MSAccess's interface?
#3
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 08:48 AM
#4
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 09:11 AM
Well.. only allow inserts and not update/deletes!
#5
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 09:51 AM
Let me tell you my problem, see there is one data entry operator 1st he will enter all the data after that, his boss will verify the entered data then he will update the data along with his name "Verify by name must be enter". So, once boss verify the data after that it should not be change even that boss also.
#6
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 09:55 AM
Well then have a numeric column for each stage of this approval process.. and increment as the data moves down the pipe.. and when the data loads - depending on the numeric value allow and disallow certain user types to edit the data.
0 = just entered (user cannot enter/edit)
1 = boss reviewed it (user cannot enter/edit - boss can edit)
2 = boss verified it (boss and user cannot edit)
It's all about setting up roles and permissions.
0 = just entered (user cannot enter/edit)
1 = boss reviewed it (user cannot enter/edit - boss can edit)
2 = boss verified it (boss and user cannot edit)
It's all about setting up roles and permissions.
#7
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 09:55 AM
modi123_1, on 15 January 2013 - 07:50 AM, said:
Modify it through your app or modify it through MSAccess's interface?
Through app only.
Let me tell you my problem, see there is one data entry operator 1st he will enter all the data after that, his boss will verify the entered data then he will update the data along with his name "Verify by name must be enter". So, once boss verify the data after that it should not be change even that boss also.
#8
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 10:07 AM
modi123_1, on 15 January 2013 - 09:55 AM, said:
Well then have a numeric column for each stage of this approval process.. and increment as the data moves down the pipe.. and when the data loads - depending on the numeric value allow and disallow certain user types to edit the data.
0 = just entered (user cannot enter/edit)
1 = boss reviewed it (user cannot enter/edit - boss can edit)
2 = boss verified it (boss and user cannot edit)
It's all about setting up roles and permissions.
0 = just entered (user cannot enter/edit)
1 = boss reviewed it (user cannot enter/edit - boss can edit)
2 = boss verified it (boss and user cannot edit)
It's all about setting up roles and permissions.
thanks for d idea
tell me one thing if i create some roles lyk "Developer, Admin, User, Boss" and during log in time if the user select any role among them then they can get some different permissions? is it possible, how to write the SQL syntax "Select * from xyz where username & password & role = '" & UsernameTextBox.Text & "'&'" & PasswordTextBox.Text & "' & '" & Roletextbox.Text & "'""
#9
Re: Once data inserted into ms-access database it should not updateable
Posted 15 January 2013 - 11:37 AM
There are many possibilities in trying to accomplish what (I think) you're asking. Instead of each person having a single role, they can have more than one? Is that what you mean?
I did something similar by assigning bitwise values
Developer = 1
Admin = 2
User = 4
Boss = 8
So if a user is an admin and a boss their value is 10 and by ANDing the value with the value you're comparing, you can determine if that user fits that criteria.
This way a user has a single userid and a column that holds their role(s)
EDIT: Listed wrong bitwise operator
I did something similar by assigning bitwise values
Developer = 1
Admin = 2
User = 4
Boss = 8
So if a user is an admin and a boss their value is 10 and by ANDing the value with the value you're comparing, you can determine if that user fits that criteria.
This way a user has a single userid and a column that holds their role(s)
EDIT: Listed wrong bitwise operator
This post has been edited by CharlieMay: 15 January 2013 - 11:48 AM
Page 1 of 1
|
|

New Topic/Question
Reply



MultiQuote







|