30
We have an MS Access database that we are using at my work. Currently, everything is done through forms in Access, but this makes making any updates to the forms difficult, as there is always somebody in the file so we can never save any changes. The plan is to make the forms web based. We're currently looking at a few different options - the first is to use Infopath, which a coworker is learning right now, while the other is to use ASP.Net.
I'm really not a fan of Infopath at all, as it has always felt a little too restrictive to me, so I'd prefer to use ASP.Net. My main concerns with that have to do with maintaining data integrity. Basically, we will have a page that, when the user selects a service name, will display all the hiring actions for that service. We would face the basic problem of two people having the same service open and making changes to it, thus having one of them over-writing the other person's changes. Nobody on the team is all that intimately familiar with ASP, so I'm worried that the workaround for this is going to take a lot more knowledge of the language than we currently have or could learn in a short amount of time.
I guess the real question I have is how does record locking work in ASP.Net? If I run a query for, say, all the hiring actions where service = fiscal, does it only lock down the Fiscal records, or does it lock the whole table?
