Hi all,
I have an SQL Express db accessible by many users. The db contains records that only one user should be able to view at a time to avoid duplicate work (users view a customer's record and then print out a report based on that record).
As a newbie I've done a bit of research and I think I should add an extra table column called 'locked' (which could contain the user's name). My VB.net app will find the next available record where the 'locked' column is null.
Is this good practice or am I missing something more obvious?
Thanks,
Matt
I have an SQL Express db accessible by many users. The db contains records that only one user should be able to view at a time to avoid duplicate work (users view a customer's record and then print out a report based on that record).
As a newbie I've done a bit of research and I think I should add an extra table column called 'locked' (which could contain the user's name). My VB.net app will find the next available record where the 'locked' column is null.
Is this good practice or am I missing something more obvious?
Thanks,
Matt
