Visual Basic Assignment Introduction You are required to develop a small system in Visual Basic to demonstrate the programming skills you have mastered in studying this module. You are also required to document it accordingly. You are free to specify your own requirements for this project ??" it might be concerned with a hobby, or another area of your studies, or simply be the product of a vivid imagination. However, in order to gain credit it must utilise in an appropriate way a range of facilities provided by Visual Basic, according to the criteria below. I woudl like this project based on a CD collection
Criteria for an Acceptable Project Criterion 1: Basic controls ??" your program should use labels, text boxes and command buttons. Criterion 2: Selection controls ??" your program should use at least one of the following controls: option button, check box, list box, combo box. Criterion 3: Variables ??" your program should declare and use variables. Criterion 4: Selection constructs ??"your program should use an If and/or a Select Case statement. Criterion 5: Multiple forms ??" you should have at least two forms in your program. Criterion 6: File handling ??" your program should store/retrieve information on disk. You may use either sequential text or random-access file formats but you must NOT use the Data control to interface to Microsoft Access tables in this assignment. Criterion 7: Other constructs: your program should use at least one of the following constructs: loop, array, control array, general function/procedure (i.e. a function or procedure, not an event procedure, which you have created yourself) including at least one parameter, timer. Of course, if you wish you may use a greater range of facilities ??" even those which have not been directly covered in the module syllabus ??" so long as you meet the above requirements. The documentation you are required to hand in is as follows: (a) An outline, in 70??"100 words, of the purpose of your program. This should describe what it is for, not the step by step details of how it works nor the use of Visual Basic features in implementing it. (b) A ‘screenshot’ of each form in your project, annotated to show the name property of each control and of the form itself. (c) For each form, a table showing which property values have been modified for each object. NB it is not acceptable to simply provide a list of all properties and values ??" the list must only include those which have been modified from their default setting. (d) For each form, a listing of all code attached to the form and its objects. The code should demonstrate a suitable approach to naming, layout and commenting. (e) A list or table explaining concisely where each of the required criteria are met in your project. Where there are several instances of a facility or construct you need only give one example. For items (b), (c) and (d) you are strongly advised to take as a model the “How it Works?? documentation 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) 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).