Custom Query (26 matches)
Results (16 - 18 of 26)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#12 | fixed | Description of software (first form Patient) | ||
Description |
This form is the first step of all other forms because in this form the patient is saving with all information and if the user won’t to search the patient information it can be searched from this part, this form has search button, refresh button and addPatient button. The search button is used for searching the patient, refresh button is used if the new information that is add doesn’t appear in grid table, and add Patient is used for adding new patient, if administrator click in addPatinet In this form the user has to write the patientID, name, surname, age and all there information about the new patient to have them in electronic way not in hard copy. This form I think is more important than the other form because it gives to administrator easy work, till now they have the patient information saved in hard copy but with this application they will have all patient in electronic way and this will help them to find the patient information easily. If the administrator leaves any textbox empty the message ex:"pleas enter first name " will appear and the leaved textboxes will automatically change their color The other control that has been used is the one that doesn’t permit to put text at the textboxes that should contain numbers. In this case the following message "Invalid value entered for patientID ,it must be number" |
|||
#11 | fixed | Description of software (login part) | ||
Description |
Login part of the software
In the moment that any member of the staff will try to log in the system there will appear the following form.
If the users live empty any of the textboxes or they put a wrong username or password the following message will appear "Please enter username" In the other hand if the member of the staff put correct data and log in then will be send to the next form "The user is valid!"
|
|||
#10 | fixed | Entity Relationship Diagram and Relational model | ||
Description |
Entity Relationship Diagram
The transformation of E-R diagram into relational model is an important step, because this model defines the tables that should be implemented in Access. This transformation is also very important because there can be seen in details which attributes are used as primary keys and which are foreign keys, this scheme also provides a better distinction between identifiers and descriptors which were mentioned above. The organization of data into relational tables is also known as the logical view of the database. That is the form in which a relational database presents data to the user and the programmer. |