-
Application Design - locking
If we're developing a new application using SQL Server 6.5 as the
database, do I need to write some code into my application to take care
of locking the records etc so that 2 or more users aren't in the same
record making changes? I was under the impression that the database
itself would take care of that, but I think I may have been wrong in my
thinking.
What do you think? Any advice?
Thank you!
Toni Eibner
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|