Outlook Appointments – Make the Reminders Visible and changeable as when you receive them

When you get an appointment in your inbox, they often have a Reminders in them, you can’t see them, but they are there. The main issue is that I don’t want the reminder going off later.

  • Can you make the reminder visible
  • Can you add a button “Accept without reminder”
  • Can you add a button “Accept and edit the reminder”
Figure: The Appointment's reminder information, needs to be visible and changable

Figure: The Appointment’s reminder information, needs to be visible and changable

Access 2003 Runtime – Error messages after running Access 2003 Runtime for the first time (when not an Adminstrator)

You install the Access 2003 runtime as an administrator, then:

Running the Access 2003 runtime (for the first time and thereafter) as an Administrator is fine.
Running the Access 2003 runtime as a Non-Administrator gives 3 error messages (only for the first time). Subsequent times are fine. This is a terrible first impression.

Figures: Error message #1

Figures: Error message #1

Figures: Error message #2

Figures: Error message #2

Figures: Error message #3. Unacceptable warning message after installing Access 2003 runtime as a non administrator

Figures: Error message #3. Unacceptable warning message after installing Access 2003 runtime as a non administrator

Note: This is a little harsh. Unfortunately, the world of security requirements has dramatically changed since Access 97. You don’t get these prompts if the file is digitally signed. That is how you work around this for Access 2003. Digitally sign a file or macro project You are now leaving SSW

Note: In Access 2007 this has been fixed (as it now uses Trusted Folders)… however the above bug with the runtime should be fixed.

The ‘Configuring’ message is unacceptable (it should be a one time event – not every time you open a different Access version)

When you have Access 2003 and 2007 you get a very long ‘Configuring’ message when you open them alternatively.

This is not good, but I can live with it as a developer.

It really impacts our customers, when we give them a runtime in 2003, and they use Access 2007. Those customers are getting this message all day long.

Figure: This long message is caused only because they launched the Microsoft Access 2003 runtime prior

Figure: This long message is caused only because they launched the Microsoft Access 2003 runtime prior

Figure: If they exit Access 2007, then they open the Access 2003 runtime app, the penalty is the long message again

Figure: If they exit Access 2007, then they open the Access 2003 runtime app, the penalty is the long message again