Fixing normalization and adding features to Law Management Web App
Added on -2019-09-20
This project involves fixing the normalization of database tables in a Law Management Web App designed in Visual Studio and MS SQL Server 2008 using C#. The project also includes adding new features such as user session, file upload, reports, and more. The main issues to be fixed are with the dbo.User and dbo.ClientDetails tables, which have repeating groups that need to be normalized. The project also involves creating a user session for each user that logs in, updating only the relevant row when updating client details, adding a print button to generate a word document with client details, adding a reports webform, and adding file upload and prefix label and dropdownlist to various webforms.
| 3 pages
| 963 words
| 110 views
Trusted by 2+ million users, 1000+ happy students everyday
Hello,I have designed a Law Management Web App in Visual Studio and MS SQL Server 2008 using C#, thatwill run on the extranet of a small Law Firm. A Secretary/Solictor/Barriter can add client details to the system, update the details, delete or edit, and also email fee to the client while also being able to email the case details to the solicitor/barrister. Also the UpdateClient.aspx.cs webfrom we search for a client by putting there name in the text box labelled name and if the name is correct the textboxes are populated with the details etc.As you look at the webapp you will see there are a few issuesMy queries and what I would like you to fix are below... I want the same layout kept as close to what it is as possible. The only real changes I want are listed below.1)The most important issue is with normalization of the database.dbo.User has repeating groups Secretary, Solicitor and Barrister. I would like the table to be normalized to include another table of UserType consisting of Secretary, Solicitor and Barrister using foreign keys to link back to the dbo.User table. The main issue for me is allowing for this in the project code wise in Login.aspx.cs, SignUp.aspx.cs and Forget.aspx.csThe dbo.ClientDetails table I created should also be normalized as it consists of a number of repeating groups. Department is a repeating group and should have its own table, CasePlan should have its own table and also CaseStatus is a repeating group and should have its own table. These three extra tables should use foreign keys etc to link back to the main table dbo.ClientDetails. Once again my issue is that I cannot code this correctly or design it in the project code wise in NewClient.aspx.cs, UpdateClient.aspx.cs, EmailClientFee.aspx.cs and EmailSolBarCase.aspx.cs.I hope I explained that correctly? Can you confirm?I would like the Database/Tables and Webform code normalized correctly so I can update, delete, email etc correctly which updates, deletes or alters the database correctly in a normalised way.My current attempt works, but it is not normalized correctly so in effect it is useless for my project.2)I would like a user session to be created for each user that logs in. So each secretary/solicitor or barrister who have access to the system will have their name show up on a small label in the Home.aspx.cs page. If they log out their user session goes. This is so I could potentlaly have two users logging in at the same time.
Found this document preview useful?
You are reading a preview Upload your documents to download or Become a Desklib member to get accesss