Today is the day before the project is due. Mr. Calomeni also came back today, and we were given one final day to finish our project. Because our project was separated into several different programs, we put everything together today. We also added new buttons and made sure everything worked the way it was supposed to.
Yes, we are finally done after about 5 months. It's a refreshing feeling. We are happy :)
Bishop Allen Innovations - Tim Hortons
January 23, 2012
Finishing The Project
This weekend we focused on polishing the project. We added small components to the programs, changed its visuals, and updated and changed our blog to better organize our journal. We also encountered problems when we added the temperature tracker to the dropbox, as it did not debug for some people. However, we discovered it had to do something with transferring the file onto the folder, and it was fixed. Other than that, we were happy with the results.
Proofing, Naming, Design
We started to proofread the coding and the design form to make sure there were no mistakes. We added comments to the program, as well as incorporate proper naming to the objects of each form. A slight change to the temperature tracker and the missing item form was made, as we included a help button to create a more user-friendly environment. The work periods we had were basically used to finish up the project.
January 13, 2012
Local Database
Discovered we could use a local database instead of an online one after talking to the manager. Hence, we had a better idea on how to finish the Schedule form, but we still encountered issues with it. For example, one day we would be struggling on how to add variable data into the data grid while other days the program kept on constantly crashing because of a line within the code that involved the AddItemsScreen. But we pulled through in the end, and we finished the schedule form.
January 4, 2012
Over The Christmas Break
During the break, we needed to figure out how
to:
- Set up an online database; meaning, we needed to
have a method to access values from one computer, change them, and notice the
changes in those values using another computer.
- Efficiently manage the schedule for the trucks – this would also need to be online.
- Efficiently manage the schedule for the trucks – this would also need to be online.
·
The temperature tracker and the missing items
forms were finished and added to the program. However, we used the SQL server
once again to try setting up an online database but obtained bad results.
·
Worked on the schedule form. The purpose of the
program was that when the user entered the time, the values on the database
changed, and when stock orders were completed, the database would reset to its
original default value.
We
discovered that we could not connect a remote SQL database using the “Add new
data source” in Visual Basic Express 2008. In other words, we could not “drag
and drop” the information for the database.
December 21, 2011
Schedule Coding
Our class was relocated to the library and so
for a while we were readjusting to the new environment. We started to work on
the schedule form. We had to figure out a way to change the time the truck was
expected to come to the store based on how late in schedule it was. We first
needed to determine what variable to use in order to declare the time. We first
thought we could use Integer or Decimal instead of Date or Time, and we were
stuck at that point. However, we got a general idea from it on how to add
certain minutes to the original schedule for the trucks in order to keep the
arrival times accurate.
December 14, 2011
Online Database
We used a site to attempt connecting Visual
Basic Express 2008 to an online website using an SQL server. However, we
discovered this particular method wasn't going to work and we needed to think
of something else.
Subscribe to:
Posts (Atom)