Date entered/changed by keyboard (for time, expenses, bills, etc.) doesn't save

When entering or changing the date on an item (such as a time entry, expense entry, or bill) using the keyboard, the date that you've entered is not saved.

This behavior ONLY happens if all of the following are true:

  1. You change part of the date using the keyboard (not the mouse)
  2. Your change involves typing in just ONE digit - for example, changing the month from "9" to "7", but not from "9" to "10".
  3. You do not move to any other part of the window (either by using the mouse or the keyboard)
  4. After making the change, you immediately click on the Save & Close or Save & New button, without clicking anywhere else.

If you make the same change using the mouse, or if you click anywhere else on the window or move to another part of the date or to a different part of the window using the keyboard, the problem will not occur and the date will be saved properly.

Note: this problem has been fixed in version 1.12 (and later) of TurboLaw Time and Billing.

This behavior is due to a bug in the Windows (.NET Framework) date drop-down box control. The control does not consider your edit "final" until you have moved to another control or pressed more keyboard keys.

There are several ways to work around this problem when entering or editing a date. You can use any one of these options:

  • Use the mouse to enter the date rather than the keyboard
  • Click on another part of the window before saving
  • Press the TAB key on your keyboard after entering the date to move to the next field before saving
  • Use the up/down arrow keys to change the date
  • Use the left/right arrow keys to move to a different part of the date before saving

Any one of these options will prevent the problem from occurring. You do not need to use all of these options - just one of them will prevent the problem.

If this problem is fixed in a future Microsoft Windows (or .NET Framework) Update, we will update this article with the new information.

Was this article helpful?
0 out of 0 found this helpful


Article is closed for comments.
Powered by Zendesk