This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
What do I need to do in order to insure that only one person is accessing the database at a time if multiple people will have the application that interacts with it. Or is this even something I should concern myself with.
It may, or may not be a concern. That depends on your application. Here's a scenario to consider: 2 people read the same data from the database. Person #1 updates the data. Person #2 has no way to know that the data has been updated. Now person #2 submits their update. This wipes out person #1's changes. If it's highly unlikely that a situation like this can occur it may not be worth worrying about. Depending on the type of application you are writing, it may or may not be an issue.
Yeah, you probably want to watch out for the lost update scenario. You also have to very careful as to which DBMS you are using. Different vendors implement locking and concurrency control different (especially Oracle) so you must be very aware of implementation to use the database efficiently.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com