Application Shell

After discussions with various coders on the website, I have tweaked my requirements below to provide a more comprehensive explanation of what I want to achieve. Please note that all going well I will be looking to further expand this application as my time to perform the coding is limited. I am in need of a Windows application shell written in Microsoft Visual Studio 2005 - preferably VB.NET 2005 I need the application to open to a security dialog, which will authenticate to an SQL Server 2005 backend. I also require the security backend written as detailed below. In the future I wish to gradually build modules into the application such as financial, clients, management, etc. Each module will have various forms, reports, etc. Admins are to have access to all modules. Users are to be restricted to running some application modules. I want the security subsystem to be able to allow me to specify what modules a group or specific user has access to. More details below. ## Deliverables 1)I am in need of a Windows application shell written in Microsoft Visual Studio 2005 - preferably VB. 2) a)The application is to open to a security dialog, which will authenticate to an SQL Server 2005 backend. b)The passwords stored in SQL should not be stored in clear-text. c) Once the user is authenticated they will be sent to the main screen of the application, displaying the login time and currently active user. d) Based on the rights assigned to the user some of the menu items will be enabled/disabled. For the moment, the basic users need a CLOSE menu item only, while admins need access to the "TOOLS - Security" menu item (see below) and CLOSE menu item only. 3) I require the security backend written to: a) have the ability to add, delete and rename users b) have the ability to add, delete, rename and populate groups c) initially there are to be at least one demo user account - admin d) initially there are to be at least two groups for proof of concept - Admins and Users. e) record / display the last login time for each user, computername and IP address f) Users are to be restricted to running some application modules (eg: finances, security). I want the security subsystem to be able to allow me to specify what modules a group or specific user has access to. g) In the future I wish to gradually build modules into the application such as financial, clients, management, etc. Each module will have various forms, reports, etc. I don't want to recode the application when each new module is added. A database table is to be created to list the module areas of the application that users can be granted access to. The table is to be called "tblModules". In the future we would merely need to add the new module to the table, along with the forms contained in that module. eg: the clients module might allow access to the forms frmClients, frmClientAddresses, and frmClientContacts h) "tblModules" is to be populated with two records initially to prove functionality of the security system. The modules are SECURITY and CLIENTS, with at least one Windows forms associated with each of these modules. i) Admins are to have access to all modules. j) Admins should be able to reset passwords for any user k) While not part of this immediate brief, once the application is up and running, I plan to extend the security to stop users seeing all clients. For example, if I get a contractor in I only want them seeing the clients I designate they are working on rather than the entire list. This will stop people stealing client lists. But as I said that's down the track. But you can see this would also require a more dynamic security list, much like I envisaged with the modules having a dynamic list created from the modules listed in a table. I sort of envisaged the the client security could be stored with the client info. For example, we have a clients table, and a clientspermissions subtable. Hence we have multiple entries in the clientpermissions subtable that would be dynamic. Entries in this table might be for example: id: 1 clientno: abcxyz employeeno: mark access: allowed id: 2 clientno: microsoft employeeno: mark access: allowed Maybe I am thinking of this all wrong but thats what I have in mind visually. Hence why I thought we could worry about that part later. 4) I want to ensure variables are used as much as possible in the coding of the application. For example: - the SQL server configuration will need to be a variable - ie: I don't want the server name hardcoded in the application. - the database name - the application name - the application version 5) The system coding must include full error handling to ensure the application gives users full information about the location of any crash, and exits the application to ensure unauthorised users cannot access data when in a crashed state. 6) When coding please bear in mind I plan to add a web interface for some modules, and would need to have the ability for users to authenticate using the same security backend. These web modules would be hosted on IIS, and interface with the SQL backend. For the moment nothing will be written re this however I ask that you bear this in mind when coding the security subsystem. 7) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 8) Deliverables must be in ready-to-run condition, as follows: a) SQL Server side executable and scripts to create tables automatically b) The client application itself is to have a software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request, with questions re the SQL server name, etc during the install procedure. 9) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Tuesday Jul 25, 2006 10:40:23 AM: Hi, I have clarified the bid requirements after speaking with coders bidding. Please review the specs and update your bids if required. Thanks Mark ## Platform Windows 2000/XP/2003 for the client application SQL Server 2005 for the SQL backend