ASP.NET application to store and display user-editable rich text

I need an ASP.NET application to display and allow editing of user-entered rich text, which will be stored in a SQL Server 2005 database. The application will also require authentication to access the editing interface (plain-text username/password values stored in the database, no Active Directory or Windows Authentication needed). ## Deliverables **_About the Data_** I have attached a Create script for a database with sample data, but please feel free to make whatever changes you need to the structure. The script assumes you have a database named [EditableText]. Once you run the script, you'll see that the database has four tables: Markets, TextEntries, Articles, and Users. Markets and Articles simply have Id and Name columns. TextEntries are organized by Market and then by Article. This means that "Market 1, Article 4" or "Market 3, Article 2" would each refer to a unique text entry. Note that there is a constraint on the table to prevent multiple text entries from having the same Article and Market. (NOTE: The text entries must be stored and displayed as rich text, including font sizes, bolding, underline, and italics. They may also be in multiple languages including Russian, Mandarin Chinese, and Greek, so please ensure that the database encoding can handle this.) The Users table contains authentication information for users authorized to edit the text entries. Each user will have a Username, a Password, and a MarketId. The MarketId tells the application which Market's text entries that user has permissions to edit - for example, a user with a MarketId of 5 can edit any text entry that also has a MarketId of 5. (NOTE: Market Id -1 is the MASTER Market, with permission to edit all Markets.) _**Application Functionality**_ The purpose of the application is to display the correct text entry for the user by Market and Article, and allow them to edit that text entry if they are authorized. All users can view all text entries without logging in, but must authenticate in order to edit. The application will be accessed using a hyperlink containing a query string that specifies the ArticleId number (for example, [login to view URL]). If no Market cookie is detected (see next paragraph), the user will select their Market from a dropdown menu consisting of the Name values from the Markets table (except for the MASTER market, which should not appear as a choice). Once the user selects their Market, they should receive a cookie that stores this information. The application should check for this cookie every time it is launched - if the cookie is present, use that Market value, and if it is absent, display the dropdown and attempt to store the cookie. When the market has been determined, the proper text entry for that Market and Article should display. At the bottom of the window, there should be an Edit button. Pressing this button will prompt the user for a username and password, which will be checked against the values stored in the database. Additionally, it should check the MarketId for that user to make sure they have permission to edit text entries for the current market. The login should succeed if the user's MarketId matches the MarketId of the text entry they are trying to edit, OR if the user's MarketId is -1 (the MASTER Market). If the login is successful, the user will be taken to the editing interface. This should be a standard WYSIWYG rich-text editing window, similar to the one that appears on vWorker when using IE8/9. The bottom of the editing window should have a Save button to allow the user to commit their changes to the database, and a Cancel button to allow them to exit the editing interface without saving. NOTE: When saving to the database, please take appropriate care to prevent SQL injection in text entries. After saving or cancelling, the user should be taken back to the text display. Authentication information does not need to be stored - they can log in every time they want to edit. That's all there is to it. Please let me know if you have any questions or need further information. Thanks for bidding!