During the process of completing this database project in Microsoft Access I learned a lot. Creating tables was probably the activity I was most acclimated to since I have experience in programs like Excel. Figuring out how to correctly import the data, however, was a bit of a trial-and-error type of experience. I ended up getting it right the third time around. I learned how to create a query from that imported data which was, in my opinion, the most useful of activities. I then learned how to create forms and reports which included a lot of specific property editing, but that taught me how to effectively organize and present information. Overall, I learned that I would never choose to use this confusing database and I hope that this was my first and only time having to.
(geekpedia.com)
I struggled with this database even though I watched the lectures, read the textbook chapter, watched outside tutorials and used the searchable help tool. Microsoft Access would benefit from creating a more intuitive application. Even through using the help tool I felt like I was really on my own trying to figure out the next step. It could streamline tasks by making items less separated-I was very confused and thought I had to somehow "merge" the tables, queries, forms and reports into one database, like I would with different PDF files. By using the same verbiage, this database would seem less complicated. For example, when I was trying to make the MemberID field not editable in the form, I could only find the "allow edit" option for forms in their entirety, instead of for just the MemberID field. I had to do multiple searches and trials until I realized that "disabling" that field would make it read-only. There is no reason why this field shouldn't have the same options as the form, at least for the exact same tasks. Microsoft Access should learn more about its users and predict what they might like to do next.
No comments:
Post a Comment