I am going to flash my TyTnII.
All my data is synced Except my SMSes Grrrrrrr.
I am going to flash my TyTnII.
All my data is synced Except my SMSes Grrrrrrr.
All unhandled errors (aka crashes) will take your email…
And inform you when a hot fix/service pack resolves that issue
(I choose Outlook as the first application to implement this, as that is what I get the most crashes)
If I get more than one contacts with the same email address when checking the names, I’d like to know which is in my Local Contacts and which in the Exchange User List. So please add a column to identify this.
For instance, if I know the one in my Local Contacts is the latest and the first one is identified as Local Contacts, I can select it easily without checking details of these two.
It’s more efficient to have a ‘Find’ option in the right click menu of the ‘Contacts’ folder. With it we can look for certain contacts easily.
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.
Currently, Microsoft makes this decision based on what was the last copy of Access opened. This is a mistake.
A .MDB should open in the version it was designed for.
Note: A bootstapper application is needed (this is what the Visual Studio Team did).
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.
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.
There should be a column in the Form designer that tells you the size of each object.
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.
When you have an Access 2003 Runtime installed (only) + using Office 2007, Windows Updates recommends (aka gives end users grief) patching Word 2003 etc (which they don’t even have).
PS: Times like this I wish Access was not tied in with Office.