<div>
Are you asking how to do this in Access (with an Access database), or asking how to do this in SQL Server?<br />
<br />
For the record, you cannot lock individual columns/rows in an Access database on the table level. You can build forms which mimic your tables, and you can use code to Enable/Lock the controls, but that won't stop someone from changing data in the tables directly.
</div>


<div>
What about SQL Server?<br />
How can I do that?<br />
And what if I enable specific users to be able to unlock those fields?
</div>


<div>
You cannot lock columns/rows in MS Access, however, you can keep the user from modifying the tables, queries, views, reports in MS Access by calling &quot;DoCmd.LockNavigationPane True&quot;, or by following instructions in: <a href="http://office.microsoft.com/en-us/access/HA102357171033.aspx" rel="ugc">http://office.microsoft.com/en-us/access/HA102357171033.aspx</a>. &nbsp;You would need to build forms to provide read-only access to your tables or queries.<br />
<br />
You cannot lock rows or columns in SQL Server. You may grant permissions at the table level. Be aware that the priviledges of the caller take precedence, so if a user account executes a stored procedure which updates data, the permissions for that stored procedure take precedence, even if that user has been denied access to update the table. &nbsp;You can implement triggers to prevent updates to your tables which meet a criterion/criteria to filter out exactly which row/column you wish to deny modifications (lock specific rows), though I would recommend implementing &quot;edit&quot; logic in a BLL or even the Persistence or Data Layer (or a VBA module, if the application is written in VBA) and to stay away from triggers unless there is no other choice. &nbsp;You may also implement rules in your SQL stored procedures to prevent updates for rows/columns for specific criteria. You may also implement SQL Server views to provide a read-only conduit for your SQL Server tables.
</div>


<div>
Thanks for the comprehensive answer...<br />
For controlling using VBA modules, I prefer staying away from that because I think that the best security can be achieved using server-side security, not client side<br />
I want some explanation regarding this sentence: &quot;I would recommend implementing &quot;edit&quot; logic in a BLL or even the Persistence or Data Layer&quot;
</div>


<div>
Could you explain why you don't really prefer triggers?
</div>


<div>
Sure;<br />
<br />
Triggers are usually hard to debug/trace and they are performance overheads to systems, since every time data in a table has changed, a trigger is fired.<br />
<br />
Normally, I would only use triggers when I need to implement a &quot;quick and dirty&quot; table auditing facility to track changes in a table when it is required to do so. I always try to avoid them whenever possible and use stored procedures instead. There are times where I have used triggers due to time contraints in developing a more elegant solution; however, I always inform the business partner(s) of the pros and cons of triggers, if it is presented as an option in a solution due to limited time contraints. I would also suggest to replace triggers with stored procedures in a future project, if they are implemented.
</div>


<div>
<div class="content wysiwyg-content">
Hi everybody...<br />
<br />
How can I lock specific fields from being edited?<br />
I'm using MS Access 2007 for making the back-end, and I can use the same software of MS SQL Server 2005 as a back-end depending on whether I need it or not...<br />
<br />
As I know, I can look a specific column in SQL Server by modifying the permissions on that column, and I can lock rows by using simple views<br />
But, how can I lock specific rows only?
</div>
</div>


Hi everybody...

How can I lock specific fields from being edited?
I'm using MS Access 2007 for making the back-end, and I can use the same software of MS SQL Server 2005 as a back-end depending on whether I need it or not...

As I know, I can look a specific column in SQL Server by modifying the permissions on that column, and I can lock rows by using simple views
But, how can I lock specific rows only?

Locking specific columns in specific rows using MS Access 2007

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.

Visual Basic Classic

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.