Record locking table w/ view

Try to reformulate your question, it's not very clear.

I have a member table where a user can change his own profile. There are different administrators for different members in this table subdivided by ID. The admin can change any member profile under his ID. A view was created called admin_member for the purpose of setting the security permissions to allow the admin to edit the members. The only time where locking would be required is when a member and the admin are making changes at the same time. The locking does not work for a table and it's view because they do have different names although they are the same table. Hopefully this is more clear.

This behaviour is by design, locking is implement on project level, tables and views are treated as different objects.

I kind of figured that it was by design. That makes sense. I don't fully understand what you mean that it is implemented on a project level. So there is no way to implement this for my case?

What you looking for is 'locking on database level' where physical tables can be locked. PHPRunner is only able to lock 'project objects' like tables and views defined in PHPRunner.
If you need to lock records - you have to handle it using single table or view.

I understand now. Thanks