Good instructions on how to use ElementTree to parse XML by Eli Bendersky.
Very good article by Fast Company based on a presentation giving at Google I/O by Tomer Sharon, Google Search User Experience Researcher. The link below has the full video of the presentation and the article has a great summary of the information. Super high level summary:
- Does the app solve a real problem? If not, then adoption will probably be low.
- If you get feedback from friends instead of actual users, that feedback may be very biased. Seek out feedback from potential users.
- Observe actual user behavior instead of surveying. Users may not actually understand their own actions or behaviors. Watch what users do instead.
- “Riskiest Assumption” – This concept is not explained very well in the article and I did not watch the video. I may not even understand very well, but the basic idea is, “Is every part of the concept understandable? Is there a fundamental flaw in the whole process that would result in failure?”
- “Bob the Builder” – the act of building an app quickly as a test case to see if people adopt it and change the app purpose if necessary. The problem is that you have done your research and are actually trying to solve a problem, then you should be focused on a complete solution to the problem.
- You need to understand the need and the problem and build an app to address that.
Here is a way to be able to show status messages when running a macro in MS Access.
1. Create a form and name it something useful. In my example, the form is called “Status”
2. On this form, create a text box. When you create the box, you will have the text box itself as well as a label. The label is optional. Select the text box and look at the property sheet. In the Other tab, either make note of the name, or rename the element to something memorable. In my example, the element is called “Text1”.
3. In your macro, add an “OpenForm” event to open the form you’ve just created. Window Mode should be “Normal.” I thought it would be cool, if it was a pop up windows, but the macro will not continue to run as long as the window is open.
4. In your macro, add “SetValue” at locations where you want to update the status message. The Item value for my example is “[Forms]![Status]![Text1]”. You can use the magic want to search for the element. The value for Expression is the message you want to display in quotes.
Every SetValue step will change the message in the form.